Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.usenightowl.com/llms.txt

Use this file to discover all available pages before exploring further.

Issues are NightOwl’s triage surface. Every unhandled exception and every slow request gets grouped by fingerprint so you see one row per problem, not one row per occurrence. From there you assign, prioritize, discuss, and resolve — the same workflow regardless of whether the issue started as a stack trace or a p95 regression.

​
The two issue types

Exception issues

Grouped by stack-trace fingerprint. One issue covers every occurrence of the same bug across every request, job, or command that hit it.

Performance issues

Opened automatically when a route’s p95 duration crosses the threshold you configure in Settings → Thresholds. Closed automatically when it recovers.
Switch between tabs at the top of the Issues page. Filters, bulk actions, and status pills apply to the active tab.

​
Status model

An issue is always in one of three states:
StatusMeaning
openActive. Alerts fire and the issue appears in the default list.
resolvedFixed. Silent until the fingerprint recurs — at which point the agent auto-reopens it (regression detection) and fires issue.reopened.
ignoredNoise. Silenced indefinitely — never auto-reopens, regardless of how often the fingerprint recurs.
Use Resolve for bugs you’ve deployed a fix for. Use Ignore for issues you’ve deliberately decided not to chase (third-party noise, known false positives, deprecated endpoints).

​
Triage workflow

  1. Filter down — status pills (Open / Resolved / Ignored / All), environment dropdown, assignee dropdown, and free-text search stack across each other.
  2. Pick by priority — the priority column is sortable. Critical first, then high.
  3. Open the detail view — click a row. The right-hand Manage sidebar has status, priority, assignee, and description; the main pane shows the latest stack trace, occurrence sparkline, affected users, environments, and a combined comments + activity timeline.
  4. Resolve with context — post a comment and tick Resolve on comment in one action. The comment, the status flip, and the alert fan-out all happen together.

​
Bulk actions

Tick the checkbox on multiple rows to reveal the bulk toolbar. Available actions:
  • Resolve selected
  • Ignore selected
  • Reopen selected
Useful when you ship a fix that knocks out a cluster of related exceptions, or when you want to sweep stale issues before a release. Bulk assignment isn’t supported today — assign one issue at a time from the Assigned column or the detail sidebar.

​
Assignments and comments

  • Assignee — any team member on the app. Assigning an issue notifies the assignee through the configured alert channels (if they have email configured).
  • Comments — markdown supported. Use them to document the investigation, link to PRs, or record why something was ignored.
  • Activity timeline — every status change, priority bump, assignment, comment, and description edit appears in the timeline. Entries from the MCP server are visually distinct so AI-driven edits stay auditable.

​
Alerts

Alert channels fire on the four lifecycle events documented in Alert channels → What fires an alert: issue.new (brand-new fingerprint), issue.reopened (a resolved issue’s fingerprint recurs — the agent flips it back to open automatically), plus issue.resolved / issue.ignored / issue.reopened on user triage actions. Individual occurrences within an already-open or already-ignored issue never re-alert — they bump counters silently. That keeps Slack quiet during incident storms and keeps “ignored” meaningful. resolved is the exception: a recurrence is treated as a regression, so the agent auto-reopens the issue and fires issue.reopened. To suppress flapping, set NIGHTOWL_REOPEN_COOLDOWN_HOURS on the agent (see Configuration → Issue lifecycle). With a cooldown of 24, for example, an issue resolved less than 24 hours ago stays silent on recurrence; only after the cooldown elapses does the next recurrence trigger the auto-reopen.

​
Auto-resolve stale issues

In Settings → Issues you can set an auto-resolve window (default: disabled). Any open issue with no new occurrences for that many days is resolved automatically by the nightowl:auto-resolve-issues artisan command, scheduled via Laravel’s scheduler in each app. This keeps long-running projects from accumulating a graveyard of open-but-forgotten issues. The activity timeline still shows exactly when and why the auto-resolve happened.

​
API and automation

Every action in the UI — status change, priority edit, comment, bulk update — has a direct API equivalent under /data/{app}/issues. AI assistants can do the same through the MCP server, which wraps those endpoints with auditable tokens and a fixed tool surface.