Site Reliability guardian event structure

  • Latest Dynatrace
  • Reference
  • 4-min read
  • Published Oct 24, 2025

Depending on the type of guardianLifecycle guardian or Business guardian – you use, the underlying event structure is different. The number of events written by the Site Reliability guardian is the same, no matter the type. For each validation, one started event, one finished event, and n objective event, one for each objective of the respective guardian, are written.

Lifecycle guardian (SDLC events)

To query Lifecycle guardian events with DQL, use the following query:

fetch events
| filter event.kind == "SDLC_EVENT"
| filter event.provider == "dynatrace.site.reliability.guardian"

There are two different types of events: validation and validation.objective. For validation event types, there are two additional subtypes based on the event status started and finished.

To query Lifecycle guardian validation started events, use the following DQL query:

fetch events
| filter event.kind == "SDLC_EVENT"
| filter event.provider == "dynatrace.site.reliability.guardian"
| filter event.type == "validation"
| filter event.status == "started"

The above lifecycle events share several common fields. Any data that is related to guardian internals is stored with a prefix of dt.srg.. The structure of the other event fields aligns with the Semantic Dictionary for Software Development Lifecycle Validation Events.

Lifecycle guardian event fields

When you want to integrate Lifecycle guardian validation results with a dashboard or other tooling that you have created, the event fields below is a good starting point for your queries.

Field name

Description

Event type / status

validation.result

A text indicating the result of the validation. Any value of pass, warning, fail, error, or info is possible.

validation, finished

dt.srg.id

The ID of the guardian. It could be used to filter for specific guardian events or as part of a backlink to the guardian.

all

dt.srg.tags

All the tags that have been defined for a guardian. It could be used to filter for specific guardian events.

all

task.id

The ID of the guardian validation. It could be used as part of a backlink to the analysis page of the guardian.

all

Business guardian (Business events)

To query business guardian events with DQL, use the following query:

fetch bizevents
| filter event.provider == "dynatrace.site.reliability.guardian"

You can see three different types of events: guardian.validation.started, guardian.validation.finished, and guardian.validation.objective.

To query Business guardian.validation.started events, use the following DQL query:

fetch bizevents
| filter event.provider == "dynatrace.site.reliability.guardian"
| filter event.type == "guardian.validation.started"

The above business events share several common fields.

Business guardian event fields

When you want to integrate business guardian validation results with a dashboard or other tooling that you have created, the event fields below is a good starting point for your queries.

Field name

Description

Event type / status

validation.status

A text indicating the status of the validation. Any value of pass, warning, fail, error, or info is possible.

guardian.validation.finished

guardian.id

The ID of the guardian. It could be used to filter for specific guardian events or as part of a backlink to the guardian.

all

guardian.tags

All the tags that have been defined for a guardian. It could be used to filter for specific guardian events.

all

validation.id

The ID of the guardian validation. It could be used as part of a backlink to the analysis page of the guardian.

all

Related tags
Software Delivery