8.25 peinit.operation.merged

  • Event type: peinit.operation.merged
  • Defined in: peinit.evman
  • Tier: verbose
  • Gating: none — every merge is recorded
  • Cardinality: one record per occurrence

An operation was absorbed into another before it ran, and has no outcome of its own: follow object.operation.merged-into.guid to the operation whose peinit.operation.ended decides it.

Formerly operation.merged.

8.25.1 Fields #

FieldTypePresenceMeaning
object.operation.guidbin.guidrequiredThe peinit operation the event is about: a start, stop, restart, reload or reset of one service, from the moment it is requested to the moment it ends.
object.operation.typestr.enumrequiredWhat the operation does to its service.
object.operation.sourcestr.enumrequiredWho or what asked for the operation.
object.operation.statestr.enumrequiredAlways merged.
object.operation.merged-into.guidbin.guidrequiredThe operation that absorbed this one.
object.service.namestrrequiredThe name of the service the event is about, as its definition names it.
subject.token.sidbin.sidoptionalThe user SID of the effective token the operation ran under.
subject.token.groupsbin.sid[]optionalThe group SIDs carried by the effective token.
subject.token.privilegesuint.flagsoptionalThe privileges the effective token holds, as the flags of its 64-bit privilege word from uapi/pkm/token.h: bit n is the privilege whose LUID is n, so SeDebugPrivilege is bit 20.
subject.token.privileges-enableduint.flagsoptionalWhich of the privileges in subject.token.privileges are enabled, as flags in the same bit layout.

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