Incident

Something broke or degraded, and someone should look.

Pattern

incident.*

Written with

Intents

Levels

errorwarn

Intents

Something broke and someone should look: a request, a job, a dependency

It worked, but worse than it should: a fallback, a retry, a slow dependency

Recording one

Name what happened. The intent sets the level and whether it alerts.

TS
// Something broke and someone should look: a request, a job, a dependency
log('incident.failed', 'Feed refresh stopped', { source: 'npr', attempt: 3 });

// It worked, but worse than it should: a fallback, a retry, a slow dependency
log('incident.degraded', 'Search fell back to the cached index', { tookMs: 4200 });
Writes (incident.failed)
TS
{
"intent": "incident.failed",
"level": "error",
"alert": true,
"message": "Feed refresh stopped",
"data": {
"source": "npr",
"attempt": 3
},
"time": "2026-10-09T12:00:00.000Z"
}

Is it an incident entry?

Find the row that describes your case, and use the domain on the right.

  • If the problem is

    Use

  • Who did what, kept as a record: things created, changed, deleted, and changes to access.

    audit.*
  • Signals worth watching: failed sign-ins, bad tokens, rate limits, probing.

    security.*
  • Something broke or degraded, and someone should look.

    incident.* this page
  • Background work: syncs, backups, migrations, scheduled runs.

    job.*
  • Detail for working on the code, dropped in production.

    debug.*

For registry authors

Starter intents. These are the intents prongs add logs puts in your registry. Change levels through the level.* intents, and point log() at your logger.