Skip to content

[Feature]: Diagnostics tab for errors, info, and network failures #1155

Closed

Description

@deniial00

Before you start

  • I searched the existing issues and roadmap and did not find a duplicate request.

What problem does this solve?

Currently, the bottom status bar shows only the latest notice/error. A later message replaces it, making it difficult to review earlier failures or understand why a layer, service, or network request did not load.

RustGIS already has a Diagnostic Monitor, but it displays performance/session metrics rather than a history of application messages and network failures.

Proposed solution

Add a dedicated Diagnostics pane for troubleshooting application messages and network failures, inspired by [GeoLibre's diagnostics UI](https://github.com/opengeos/geolibre/blob/main/apps/geolibre-desktop/src/components/layout/DiagnosticsDialog.tsx).

Make it accessible from the View ribbon and status bar. The existing performance-oriented Diagnostic Monitor should remain unchanged.

  • Retain a bounded, session-local history of errors, warnings, informational messages, and failed network requests, including background tile and remote service failures.
  • Show timestamps, severity, source/category, readable messages, and expandable technical details.
  • Include request URL, HTTP method/status, and duration when available. Distinguish HTTP failures from connection failures/timeouts without inventing unavailable details.
  • Provide severity/network filters, Copy diagnostics, and Clear actions.
  • Capture messages even while the pane is closed.
  • Redact credentials, tokens, and signed URL secrets before retaining, displaying, or copying diagnostic details.
  • Keep the history in memory only, without persisting it in .rgis project files.

Relationship to Session Log (#797 / #947)

The Session Log introduced in #947 serves a related but distinct purpose:

  • Diagnostics: Application messages, warnings, errors, and network failures for troubleshooting.
  • Session Log: Executed commands, parameters, outcomes, and durations for reviewing session activity.

Both are session-local, in-memory histories with explicit export/copy capabilities.

As suggested in [#1155](#1155 (comment)), a shared pane with separate Diagnostics and Session Log tabs could provide a consistent interface without introducing two similar troubleshooting views.

However, the underlying data models should remain independent.

Proposed implementation approach:

  1. Implement Diagnostics independently in feat(ui): add session-local diagnostics history #1181.
  2. Implement the Session Log independently in Session log: every command run in a session, with its time, parameters and outcome (#797, part 1) #947.
  3. Integrate both into a shared pane in a follow-up, reusing UI components where appropriate.

This keeps the PRs independently reviewable and avoids introducing unnecessary dependencies between them.

Implementation

PR #1181 implements the Diagnostics history and pane.

The implementation should reuse existing notice/error paths, capture background network failures, and expose the pane through ui.pane.diagnosticLog.

No additional dependency is required.

Acceptance / verification

  • Multiple errors, warnings, and informational messages remain reviewable after subsequent messages and after closing/reopening the pane.
  • HTTP errors and connection failures from background requests appear with available request context.
  • Filtering, copying, clearing, bounded retention, and secret redaction work correctly.
  • Diagnostics work on both desktop and browser.
  • The existing performance-oriented Diagnostic Monitor remains accessible.
  • No diagnostic history is persisted in .rgis files.

Out of scope

Estimated scope

Medium: a broader feature that is feasible in a reasonable timeframe.

Activity

  1. elpidioassinaturas commented on Oct 31, 2026

    @elpidioassinaturas
    Contributor

    This overlaps with #797, so a note to keep the two from becoming two similar panes.

    #947 (#797 part 1, open) adds a session log of commands: one entry for each command that changes the project or reaches a file or a service, with its time, parameters (secrets taken out), outcome, error and duration. It is held in memory for the session only, bounded to 10,000 entries, and read with project.log.

    Part 2, ready locally and waiting on part 1, is the app's view of it. For now it's a switch at the top of the History pane: entries newest first, a filter by command, Failed only, Save Log As… (CSV or JSON Lines), Clear Log and Log Commands.

    That is much the same shape as the Diagnostics tab here: a bounded, session-local list with a time on each entry, filters, and Copy and Clear. The difference is what goes in: commands there, application messages and network failures here.

    Proposal: one pane holding both, with a Diagnostics tab and a Session Log tab sharing the list, the filter row and the Copy/Clear actions. A failed command would then sit next to the network failure that caused it. I'd move part 2 into that pane, wherever #1155 puts it, rather than into History, and keep #1155's design as it is. I'm not taking this issue, only lining part 2 up with it.

  2. deniial00 commented on Oct 31, 2026

    @deniial00
    MemberAuthor

    @elpidioassinaturas I like the idea of bringing Diagnostics and the Session Log together in one pane, with separate tabs for their respective purposes. It would also help avoid having multiple similar troubleshooting interfaces.

    One thing I'd like to emphasize, though, is keeping the Session Log separate from project persistence. I'm not particularly in favor of storing a complete command history in .rgis files by default.

    To me, a project file should primarily represent the current project state, rather than every action that led to it. A command log serves a different purpose, and saving it automatically could introduce unnecessary file growth and privacy concerns when sharing projects.

    The session-only approach in #947, with an explicit export option, seems like a good compromise.

    I'd also prefer keeping Diagnostics and Session Log as separate data models, even if they share a pane and some UI components.

    For #1181, I'd suggest keeping the current Diagnostics implementation independent and integrating the Session Log UI once #947 is ready, rather than making either PR depend on the other.

  3. self-assigned this
    on Oct 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions