UI Reference

Top-level views

The local UI has four main surfaces:

• Issues Default grouped issue feed.
• Detail Expanded view for one fingerprint and its occurrences.
• Traces Trace/performance feed and waterfall detail.
• Settings Persisted local defaults for LLM and triage behavior.

Issues view

Filters

The Issues view exposes:

• project
• time window: 1h, 24h, 7d, 30d, all
• severity: critical, error, warn
• status: new, investigating, resolved, regressed, suppressed
• free-text / query input

Query examples shown by the UI:

• service:worker level:error
• tag.task_name:sync_orders
• is:regressed
• exception:IntegrityError

Table

The table columns are:

• selection checkbox
• severity and status
• issue summary
• count
• seen range

Bulk selection and delete are available from the issue feed.

Bulk delete

Selecting multiple issues and clicking delete opens a confirmation dialog. To prevent accidental deletes, the dialog requires you to type DELETE into a text field before the delete button activates when you delete more than one issue or choose all matching issues. Deleting issues permanently removes the fingerprints and their related occurrences, triage reports, rollups, and status history.

The same typed-DELETE flow is used for multi-trace or all-matching bulk delete in the Traces view.

Issue detail view

The detail page includes:

• issue summary and metadata
• issue status actions
• Current Analysis (the latest stored triage report)
• Deep Analysis action (re-runs triage with full context)
• occurrence list
• triage reports
• status history
• event detail for the selected occurrence
• timeline panel

Status actions

Available actions:

• New
• Investigating
• Resolve
• Suppress

If the current status is resolved, suppressed, or regressed, the New action is shown as Reopen.

Current Analysis and Deep Analysis

The detail page surfaces triage in two places.

Current Analysis shows the most recent triage report stored for the issue. While a deep analysis is running, this panel switches to a loading card showing the model being used.

Deep Analysis is a button that re-triages the issue against the latest occurrence using the configured LLM and the context the issue has accumulated since it was first seen. While it runs, the Deep Analysis button reads Running... and is disabled.

Deep Analysis is unavailable when offline mode is enabled, when no LLM base URL/model is configured, or when the configured LLM/model cannot be reached.

Event detail content

The event detail panel can contain:

• tags
• frames and stack trace
• breadcrumbs
• Network & DB Spans
• parsed Context
• raw context with parse-error hints when decoding fails

Each section that has a useful payload exposes a Copy button:

• Copy stack copies the full stack trace
• Copy reproduction copies a small block with the issue summary, fingerprint, and most recent occurrence excerpt, useful for pasting into a bug tracker

The detail page also offers a permanent delete action for the whole issue and its occurrences.

Traces view

Filters

The Traces view exposes:

• project
• time window
• protocol: http, grpc, db, other
• service
• HTTP status class: 2xx, 3xx, 4xx, 5xx
• free-text search

Summary and feed

The traces summary bar reports:

• total traces
• total spans
• average duration
• error rate

The trace table includes:

• selection checkbox
• protocol
• service
• name/path
• status
• span count
• duration
• time

Clicking a trace row expands the waterfall/detail view. Bulk delete is supported for selected traces or all matching traces.

Settings view

Settings are persisted locally in SQLite. CLI flags still override saved values at runtime.

LLM fields

• Base URL
• Model
• API Key
• Clear stored API key on save

Triage fields

• Offline mode
• Redact secrets before storing logs
• Verbose
• Min Level
• Batch Window
• Dedupe Window
• Signal running Sentinel processes to reload settings immediately

Current behavior notes:

• Verbose is stored but currently unused
• Batch Window is stored but currently unused
• reload signaling depends on platform support

Database

The Database section in Settings includes an Optimize Local DB button. It runs the same maintenance routine that runs in the background while sentinel ui is open: rollup pruning and SQLite optimize / analyze. Safe during normal use, but can briefly use CPU and disk.

Live status

The footer shows a small live indicator with one of three states:

• live (green): the UI is connected to the local stream and getting events
• reconnecting (amber): the connection dropped and the UI is retrying
• offline (grey): the stream is closed; the UI falls back to polling

The stream is a Server-Sent Events feed at /api/v1/stream. When SSE is unavailable (older browsers, restrictive proxies), the UI continues to work via periodic polling, only updates take longer to appear.

Navigation and command palette

The header includes:

• Issues tab
• Traces tab
• keyboard shortcuts button
• Settings button
• theme toggle

The command palette supports:

• Go to Issues
• Go to Traces
• Go to Settings
• direct jump by typing a single issue ID

Keyboard shortcuts

Global

Issues and traces lists

Detail view

Global shortcuts are suppressed while typing in form fields or while modal dialogs are open.