Errors

Automatic error grouping, stack traces, AI auto-triage, explain, fix, and analyze.

Error Grouping

The Errors page automatically groups individual error log entries into error groups by fingerprint (a combination of error type, message, and stack trace location). If the same error occurs 500 times, you see it as one group with a count of 500.

Error List

Each error group shows:

  • Error type and message — e.g., TypeError: Cannot read properties of undefined
  • Badges — NEW (first seen recently), FATAL (fatal-level errors), service name, environment
  • Event count — How many times this error occurred, with active vs. resolved breakdown
  • Affected users — Number of unique users who hit this error
  • Trend — Whether the error is trending up, down, or flat
  • Release version — Which release introduced or last saw this error
  • First seen / Last seen — Time range
  • Status — Open, Resolved, or Ignored

Filtering Errors

Filter by search, level (Error/Fatal), status (Open/Resolved/Ignored), service, release, and time range.

Error Detail

Click an error group to open the detail page, which includes:

  • Header — Error type, message, service, environment, status dropdown, and metadata badges.
  • Stats — Event count, affected users, first seen, duration, and the release that introduced it.
  • Details tab — Full error information organized in sections.
  • Occurrences tab — Individual occurrences with timestamps and release versions.
  • Stack Trace tab — Full stack trace with source context, separated into application frames and vendor/library frames. Also shows request context and breadcrumbs.
  • AI tab — Three AI-powered tools: Explain (what this error means), Fix (code fix suggestions with diffs), and Analyze (deep pattern and root cause analysis).

AI Auto-Triage

When enabled, Lognitor automatically triages new errors with AI. A triage card shows severity (HIGH, MEDIUM, or LOW), root cause summary, suggested fix, and affected user count.

Changing Error Status

Use the status dropdown in the error detail header:

  • Open — Active, needs attention
  • Resolved — Fixed
  • Ignored — Known issue, not actionable
PreviousLive TailNext Sessions