Repository navigation
Description
Before you start
- I searched the existing issues and the roadmap and did not find a duplicate request.
What problem does this solve?
With #1155 / #1181 introducing application diagnostics and #797 / #947 introducing command execution logging, RustGIS will have two complementary session-local histories:
Diagnostics: Application errors, warnings, informational messages, and background network failures.
Session Log: Executed commands, parameters, outcomes, and execution durations.
Both provide timestamped, filterable histories with similar controls, but serve different purposes.
Maintaining separate panes would duplicate UI functionality and make troubleshooting less convenient, especially when a command failure and a related network error need to be investigated together.
Proposed solution
Consolidate both views into a single pane with two tabs:
Diagnostics
- Application errors, warnings, and informational messages.
- Background network failures, including HTTP errors and timeouts.
- Severity and network filters.
- Expandable technical details.
- Copy diagnostics and Clear actions.
Session Log
- Executed commands with timestamps, parameters, outcomes, and durations.
- Command filtering and a Failed only filter.
- Expandable command details.
- Export to CSV or JSONL.
- Clear Log and Log Commands controls.
Shared UI
- Use the existing Diagnostics pane introduced in feat(ui): add session-local diagnostics history #1181 as the entry point.
- Provide consistent timestamp formatting, list styling, filtering, and expandable details.
- Reuse common UI components where practical.
- Make copy/export and clear actions clearly scoped to the active tab.
- Preserve entries when switching tabs or closing the pane.
- Keep access through the View ribbon, status bar, and Command Search.
Architecture
The integration should remain a presentation-layer concern:
- Keep Diagnostics and Session Log as independent data models.
- Reuse the existing collection mechanisms rather than introducing a third logging system.
- Avoid duplicating command failures unnecessarily.
- Keep both histories session-local and in memory.
- Do not introduce automatic persistence into
.rgisproject files.
The existing geoprocessing History and performance-oriented Diagnostic Monitor should remain unaffected.
Future considerations
A combined chronological timeline could eventually help correlate commands with application and network failures.
This is not required for the initial integration. The first step should be a consistent interface with separate tabs, without introducing additional logging infrastructure.
Acceptance criteria
- Diagnostics and Session Log are accessible through separate tabs in one pane.
- Existing functionality from both features remains available.
- Shared UI components provide a consistent experience.
- Filtering, copying/exporting, and clearing operate on the intended history.
- Switching tabs or closing the pane does not discard entries.
- No diagnostic or command history is persisted in
.rgis. - Works on desktop and web.
- Existing History and Diagnostic Monitor functionality remains unchanged.
- Documentation reflects the consolidated interface.
Dependencies
- [Feature]: Diagnostics tab for errors, info, and network failures #1155 / feat(ui): add session-local diagnostics history #1181 — Diagnostics history and UI
- [Feature]: A project log: every command run on a project, with its time, parameters and outcome #797 / Session log: every command run in a session, with its time, parameters and outcome (#797, part 1) #947 — Session Log engine
This issue covers the UI integration after the underlying implementations are available.
Estimated scope
Medium: a broader feature that is feasible in a reasonable timeframe
Alternatives considered
- Have them separate (this might be actually be the better approach - I am unsure yet)
Activity
deniial00 commentedon Oct 31, 2026
@Mavrick-F Since you are already familiar with the topic: whats your take on this? I feel like diagnostics and a command log are separate things and do not share (from a user perspective) a common use case. Diagnostics is for answering "What went wrong and why?" while the Command log is for traceability and knowing what has happened.
Mavrick-F commentedon Oct 31, 2026
@deniial00 I agree, I'd keep them separate. Thanks @elpidioassinaturas for lining the two up, though: it made the question worth answering properly.
They answer different questions. Diagnostics is "what went wrong", and most of the time it should be empty. The session log is "what did I do", and it grows with every change. Its natural neighbour is History, which already answers that question for tool runs. That's also where #797 first put it.
A shared pane wouldn't add much on top of that:
Suggestion:
I've put a longer note on how all these records fit together on #797. If that works for you, I'd close this one as not planned.
deniial00 commentedon Oct 31, 2026
Agree completely. Closing now.
History pane: Tool runs and Session log views; the log filtered, save…