8.12 peinit.job.created

  • Event type: peinit.job.created
  • Defined in: peinit.evman
  • Tier: verbose
  • Gating: none — every job peinit creates is recorded
  • Cardinality: one record per occurrence

A job exists: peinit has decided to run a process and recorded it, before the process exists. The gap to peinit.job.started is time spent queued, and peinit.job.ended repeats everything here, which is why this one is verbose.

Formerly job.created.

8.12.1 Fields #

FieldTypePresenceMeaning
object.job.guidbin.guidrequiredThe job the event is about.
object.job.typestr.enumrequiredWhat the job is for.
object.job.statestr.enumrequiredAlways created.
object.service.namestrwhen object.job.type != submittedThe name of the service the event is about, as its definition names it.
object.job.activation-generationuintwhen object.job.type != submittedThe activation generation of the service the job belongs to, at the time the job was created.
object.operation.guidbin.guidoptionalThe operation the job serves. Absent when none asked for it, as for a submitted job.
object.job.executablestr.pathrequiredThe path of the executable the job runs.
object.job.token.sidbin.sidoptionalA service's token is minted when its process is set up, after this record, so here it is the user the job is to run as when peinit knows that SID in advance — a well-known identity such as SYSTEM — and absent for an identity peinit has only by name. A submitted job's token exists from the start.
object.job.token.groupsbin.sid[]optionalPresent once peinit holds the job's token: a submitted job's at once, a service job's from peinit.job.started.
object.job.token.privilegesuint.flagsoptionalPresent exactly when object.job.token.groups is.
object.job.token.privileges-enableduint.flagsoptionalPresent exactly when object.job.token.groups is.

Every record also carries the header fields of the envelope, which no payload repeats.

Generated from peinit.evman by pkm/tools/gen-events-book.py. Edit the fragment, not this page.

Edit this page