Triage issues

Issues are grouped failures. LogBrew uses stable fingerprints so repeated occurrences of the same error become one issue with a count.

Status values

Status	Meaning
`unresolved`	Needs attention.
`resolved`	Fixed or no longer active.
`ignored`	Intentionally muted from active triage.

List unresolved issues

logbrew read issues --status unresolved --environment production --json

Read the issue detail

logbrew read issue <issue_id> --json

Follow related traces and logs

logbrew read trace <trace_id> --json
logbrew read logs --trace <trace_id> --json

Explain the failure

logbrew explain issue <issue_id> --json

Update status

logbrew set issue <issue_id> resolved --json
logbrew set issue <issue_id> ignored --json
logbrew set issue <issue_id> unresolved --json

Agents should not mark an issue resolved until they have read the issue, checked related telemetry, and verified the code or deployment fix.