Errors Help

Error tracking, one-click resolve, and grouped deduplication mode.

Back to Errors
Browse & Filter

Filter errors by service, status (open/resolved), date range, and sort order to find what matters.

Resolve or Group

Resolve individual errors with one click, or switch to Grouped mode to see deduplicated error families by count.

Drilldown

Expand an error accordion to see the full stack trace, attributes, and a link to related log lines.

Filter Controls
Control Description
Service Multi-select dropdown. Filter to one or more services or leave empty for all services.
Status Open (unresolved), Resolved, or All.
Sort by In individual mode: Timestamp or Service. In grouped mode: Count (default), Last Seen, or Service.
Order Ascending or descending sort direction.
From / To Date-time range filter. ISO date-time or relative shortcuts accepted.
Grouped / Deduplicated Mode

Click the Group button in the page header to enable best-effort deduplication. SOBS groups recent errors by a fingerprint of (service, error_type, message).

  • Each group header shows a count badge (for example ×12), plus first seen and last seen timestamps.
  • Sort groups by Count (most frequent first, default), Last Seen, or Service.
  • Expand a group accordion to browse the individual error stack traces within that group.
  • Click Grouped (active red state) to return to the individual-error view.
Grouping is best-effort — it operates on recent errors within the current filter window. Very old errors that were created before the current date range filter may not appear in groups.
Resolving Errors

Errors are tracked as open by default. To mark an error as resolved:

  1. Expand the error accordion to reveal the full details.
  2. Click the Resolve button in the error detail panel.
  3. The error will be marked resolved and hidden from the default Open filter view.

To view resolved errors, change the Status filter to Resolved or All.

Log Context Links

Each error detail panel includes a View Logs link that navigates to the Logs page pre-filtered to the same service and time window as the error event. This helps correlate application log output with the error stack trace.

Ingest & API
Endpoint Description
POST /v1/errors Direct error submission (JSON). Accepts stack trace, service, type, message.
POST /v1/traces OTLP trace spans with otel.status_code=ERROR are also surfaced on the Errors page.
POST /errors/<error_id>/resolve Mark a specific error as resolved (also available via the UI resolve button).