Owlmetry
CLI

Issues

View and manage error issues from the Owlmetry CLI.

Issues are error events automatically grouped by fingerprint. Each issue has a status (new / in_progress / resolved / silenced / regressed / snoozed), a list of occurrences (affected sessions), comments, and version tracking for regression detection (semver-aware: 1.10.0 > 1.9.0).

The owlmetry issues command group lets you list, investigate, and manage them.

List Issues

owlmetry issues list --project-id <id> --format json

Lists issues for a project, ordered by most recently seen. The table output colours last_seen_app_version green when it matches the app's latest_app_version, amber when it's older. See Latest Version Detection.

Filters

FlagDescription
--status <status>Filter by status: new, in_progress, resolved, silenced, regressed, snoozed
--app-id <id>Filter to a specific app
--devShow dev issues only
--limit <n>Max entries to return
--cursor <cursor>Pagination cursor from previous response

View Issue Details

owlmetry issues view <issueId> --project-id <id> --format json

Shows full issue details including occurrences (affected sessions), comments, and fingerprints.

Resolve an Issue

owlmetry issues resolve <issueId> --project-id <id> --version 2.1.0

Marks an issue as resolved. --version is required — it powers regression detection: if the same error reappears in a later version, the scan job auto-flips the issue to regressed. If you don't have a fix version, use owlmetry issues silence (known issue, won't bother you again) or owlmetry issues snooze (suspected one-off — auto-reopens on next occurrence) instead.

Silence an Issue

owlmetry issues silence <issueId> --project-id <id>

Silences notifications for the issue. Occurrences are still tracked — useful for known issues that don't need alerts. The issue stays silenced even if it keeps happening; use owlmetry issues snooze instead when you want the issue to auto-reopen on recurrence.

Snooze an Issue

owlmetry issues snooze <issueId> --project-id <id>

Snoozes the issue — like silence, but the next occurrence auto-reverts the issue to new and re-fires the issue.new push. Use when you suspect a one-off and only want to be alerted if it actually recurs.

Reopen an Issue

owlmetry issues reopen <issueId> --project-id <id>

Reopens a resolved, silenced, or snoozed issue, setting its status back to new.

Claim an Issue

owlmetry issues claim <issueId> --project-id <id>

Sets the issue to in_progress. Use this when you or an agent starts investigating or working on a fix.

Merge Issues

owlmetry issues merge <targetIssueId> --project-id <id> --source <sourceIssueId>

Merges the source issue into the target. All occurrences, fingerprints, and comments move to the target. The source is deleted. Future events matching either fingerprint will route to the surviving issue.

Add a Comment

owlmetry issues comment <issueId> --project-id <id> --body "Root cause: null pointer in UserService.fetch()"

Adds an investigation note to the issue. Comments are visible to all team members and preserved across merges.

List Comments

owlmetry issues comments <issueId> --project-id <id> --format json

Lists all comments on an issue in chronological order.

Ready to get started?

Connect your agent via MCP or CLI and start tracking.