Job

Background work: syncs, backups, migrations, scheduled runs.

Pattern

job.*

Written with

Intents

Levels

info

Intents

A background job or script began: a sync, a backup, a migration

A job ended, with what it did: counts, duration

Recording one

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

TS
// A background job or script began: a sync, a backup, a migration
log('job.started', 'Redirect sync started', { site: 'main' });

// A job ended, with what it did: counts, duration
log('job.finished', 'Redirects synced', { count: 40, tookMs: 1830 });
Writes (job.started)
TS
{
"intent": "job.started",
"level": "info",
"alert": false,
"message": "Redirect sync started",
"data": {
"site": "main"
},
"time": "2026-10-09T12:00:00.000Z"
}

Is it a job 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.*
  • Background work: syncs, backups, migrations, scheduled runs.

    job.* this page
  • 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.