All lessons Leer en español

Security in depth · Unit 23 · Lesson 8 of 14

Log fields need defined meanings

Use an event dictionary before deciding that a queued job completed.

3 minreadyShort lesson

Helpful before thisDefenses and detection

See all lessons in this topic

After this lesson you can

  • Separate queue acceptance, authenticated service identity, and a completed business outcome.

A convincing field name can still answer the wrong question.

Read the producer’s dictionary

Event semantics are the documented meanings of an event and its fields. “Success” might mean a connection opened, a request was accepted, or a business operation completed. The interpretation depends on the emitting component and event type, not the analyst’s preferred reading.

Assume a fictional membership service queues renewal notifications. Its dictionary says actor identifies the authenticated submitting service; member identifies the person named in the job. Neither field automatically establishes who was operating a browser at that time.

Event producer → Field semantics → Reliable interpretationEvent producerField semanticsReliable interpretation
The producer defines field meaning. Reliable interpretation requires that dictionary and the collection context, not merely a familiar result label.

Supplied event packet

  • D1: For this queue, accepted means the job entered the queue. A separate completed event records successful processing.
  • D2: At 09:00, job J7 records actor=membership-service, member=Leo, result=accepted.
  • D3: Collection from the processing worker was unavailable from 09:00 to 09:10. No completed event for J7 is present in the supplied packet.

Avoid two unsupported jumps

D2 establishes queue acceptance from the authenticated service. It does not establish that Leo personally initiated the job or received a notification. D3 also prevents treating the absent completion event as proof of failure.

A useful next request is the worker’s retained job outcome or another authoritative completion record tied to J7. Keep event time separate from collection time when reconciling records. Do not add message contents or personal details that are unnecessary to resolve the state.

Model wording: J7 was accepted by the queue at 09:00 from membership-service. Completion is unknown because the supplied worker observations have a ten-minute gap.

Terms you met

Event semantics

Check yourself

No timer. No penalties. Read the explanation and try again whenever you like.

  1. What can be concluded about J7?

    Show the answer

    Correct answer: The queue accepted the job from the service; final completion remains unknown. The dictionary defines accepted as queued and actor as the authenticated service. The missing completion interval prevents a stronger outcome claim.

Try it

  • WriteWrite two sentences about J7: the directly established state and the completion evidence still needed. Name the authenticated service separately from the person listed in the job.
References