System events are used to store details about executed queries, auditing events, billing events and more. In order to query system events, you need the storage:system:read permission.
Query system events.
fetch dt.system.events
The custom alert status events are used for Anomaly Detection. They track errors and warnings during the execution of a custom alert. Examples:
Analyze custom alerts status events.
fetch dt.system.events| filter event.kind == "ANOMALY_DETECTOR_STATUS_EVENT"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableA Dynatrace app ID. |
|
| string | experimentalA string that identifies the Dynatrace service that triggered the query. |
|
| string | experimentalAdditional details about the custom alert status |
|
| string | experimentalSeverity of a custom alert status |
|
| string | experimentalThe object ID of a settings value. This corresponds to the 'objectId' field/parameter in the Settings API. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
Model describing a billing usage event of function invocations. Billing usage events are stored in the dt.system.events table.
Analyze billing usage events.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "AppEngine Functions - Small"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableNumber of billed invocations. Unit is 1/4 GiB * min |
|
| string | stableThe entity/app invoking the function or not set when not invoked by an app. |
|
| string | stableThe service invoking the function or not set when not invoked by a service. |
|
| string | resource stableThe unique application identifier. Dynatrace apps are prefixed with 'dynatrace.', custom apps are prefixed with 'my.'. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| long | stableDuration of the function call in seconds. Measures not the actual execution time but the duration in the function proxy including network roundtrip to the Runtime. If the duration is bigger than the maximum allowed duration (which may happen due to technical reasons) the reported value is set to the maximum allowed duration. |
|
| string | stableIf the execution of a resumable function last for more than 2 minutes, there will be multiple |
|
| string | stableThe unique identifier of a function containing the app id and function id in the form of {app.id}.{function.id}. Missing for adhoc executions. |
|
| long | stableRuntime memory in MiB. Some of the memory is not available to the javascript code, because it is needed by the runtime itself. |
|
| string | stableThe identifier defining the function type. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableEmail of the user. |
|
| string | stableUnique UUID of a human user. If the system itself has to be represented, the constant 'system' is used. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| AppEngine Functions - Small |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
function.type MUST be one of the following:
| Value | Description |
|---|---|
| Adhoc function execution |
| App function execution |
| App function execution, but function is defined as an Action in the app manifest |
For every API access, Dynatrace stores an audit event in the dt.system.events table.
Additionally the Audit Event allows to attach an arbitrary key/value map with string keys and string values to the event. Keys are prefixed with "details." during serialization.
Analyze audit events.
fetch dt.system.events| filter event.kind == "AUDIT_EVENT"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe OAuth2 client id if of type 'CLIENT_CREDENTIALS'. |
|
| string | experimentalThe grant type used during OAuth2 authentication. |
|
| string | experimentalThe public token identifier of authentication.type 'TOKEN'. |
|
| string | experimentalThe method of authentication. |
|
| string | resource experimentalName or path of the App-Function that was executed. |
|
| string | resource stableThe unique application identifier. Dynatrace apps are prefixed with 'dynatrace.', custom apps are prefixed with 'my.'. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: | |
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableDenotes whether the event represents a success or a failure from the perspective of the entity that produced the event (for example an HTTP response code). |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableDescribes why a certain event.outcome was set. Typically, this is some form of error description in the case of a failure. |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| string | experimentalSource IP address of the request associated with this event. Must be set if origin.type is 'REST', must not be set otherwise. |
|
| string | experimentalThe ID of the browser session (if present) associated with the event. |
|
| string | experimentalOrigin type of the request associated with this event. |
|
| string | experimentalThe verbatim value of the X-Forwarded-For HTTP request header (if present) of the request associated with the event. |
|
| string | stableIn case of a REST call audit event, this field contains the request source. |
|
| string | stableGeneric reference to a resource like a REST resource URL or a settings ID. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableUnique UUID of a human user. If the system itself has to be represented, the constant 'system' is used. |
|
| string | experimentalFull name of the user. If the system itself has to be represented, the constant 'System' is used. |
|
| string | experimentalOrganization the user belongs to. |
|
Model describing a billing usage event of automation workflows. Billing usage events are stored in the dt.system.events table.
Analyze billing usage events for AutomationEngine workflows.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Automation Workflow"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableThe event end timestamp in UTC (given in Grail preferred Linux timestamp nano precision format). |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe event start timestamp in UTC (given in Grail preferred Linux timestamp nano precision format). |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableThe entity executing the workflow as UUID. |
|
| timestamp | stableThe time when the workflow was created. |
|
| string | stableThe description of the workflow. |
|
| string | stableThe unique identifier of a workflow as UUID. |
|
| string | stableThe boolean identifier denoting the visibility of the workflow. |
|
| string | stableThe entity owning the workflow as UUID. |
|
| string | stableThe title of the workflow. |
|
| string | stableThe identifier that describes the trigger of the workflow. |
|
| string | stableThe entity updating the workflow last. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Automation Workflow |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing an AutomationEngine action execution event. Action execution events are stored in the dt.system.events table.
AutomationEngine action execution state change.
fetch dt.system.events| filter event.kind == "WORKFLOW_EVENT" and event.provider == "AUTOMATION_ENGINE" and event.type =="ACTION_EXECUTION"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe app id of the app containing the executed action. |
|
| string | experimentalName of the function implementing the action. |
|
| string | experimentalThe unique identifier of a action execution as UUID. |
|
| long | experimentalLoop index of the action execution. | |
| long | experimentalRetry count of the action execution. | |
| string | experimentalThe unique identifier of the root workflow. |
|
| string | experimentalThe unique identifier of the execution of the root workflow. |
|
| string | experimentalThe state of an execution. Values depend on type of execution (workflow-, task-, or action execution). |
|
| boolean | experimentalIndicates if |
|
| string | experimentalAdditional info about current state of execution. Typically holds error details. |
|
| string | experimentalThe identifier of a task within a workflow. |
|
| string | experimentalThe unique identifier of a workflow as UUID. |
|
| string | experimentalThe title of the workflow. |
|
| string | experimentalThe unique identifier of a workflow execution as UUID. |
|
| string[] | resource experimentalCollects the identifiers of all pipelines through which a record has passed during the ingestion process in OpenPipeline, providing a complete trace of its journey. |
|
| string | resource experimentalIdentifies the source (such as API endpoints or OneAgent) used for ingesting the record into OpenPipeline. |
|
| duration | stableThe difference between |
|
| timestamp | stableEnd time of a data point. Value is a UNIX Epoch time in nanoseconds and greater or equal to the |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| timestamp | stableStart time of a data point. Value is a UNIX Epoch time in nanoseconds and less or equal to the |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Event in context of a workflow |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| Event produced by AutomationEngine |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Task execution state change event |
dt.automation_engine.state MUST be one of the following:
| Value | Description |
|---|---|
| Action execution started. |
| Action execution finished successfully. |
| Action execution failed. |
Model describing an AutomationEngine task execution event. Task execution events are stored in the dt.system.events table.
AutomationEngine task execution state change.
fetch dt.system.events| filter event.kind == "WORKFLOW_EVENT" and event.provider == "AUTOMATION_ENGINE" and event.type =="TASK_EXECUTION"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe unique identifier of the root workflow. |
|
| string | experimentalThe unique identifier of the execution of the root workflow. |
|
| string | experimentalThe state of an execution. Values depend on type of execution (workflow-, task-, or action execution). |
|
| boolean | experimentalIndicates if |
|
| string | experimentalAdditional info about current state of execution. Typically holds error details. |
|
| string | experimentalThe identifier of a task within a workflow. |
|
| string | experimentalThe unique identifier of a workflow as UUID. |
|
| string | experimentalThe title of the workflow. |
|
| string | experimentalThe unique identifier of a workflow execution as UUID. |
|
| string[] | resource experimentalCollects the identifiers of all pipelines through which a record has passed during the ingestion process in OpenPipeline, providing a complete trace of its journey. |
|
| string | resource experimentalIdentifies the source (such as API endpoints or OneAgent) used for ingesting the record into OpenPipeline. |
|
| duration | stableThe difference between |
|
| timestamp | stableEnd time of a data point. Value is a UNIX Epoch time in nanoseconds and greater or equal to the |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| timestamp | stableStart time of a data point. Value is a UNIX Epoch time in nanoseconds and less or equal to the |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Event in context of a workflow |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| Event produced by AutomationEngine |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Task execution state change event |
dt.automation_engine.state MUST be one of the following:
| Value | Description |
|---|---|
| Task skipped due to task conditions evaluation or task is disabled. |
| Task discarded due to predecessor task conditions evaluation. |
| Task waiting due to e.g. task option configuration. |
| Task execution has running action execution. |
| Task execution finished successfully. |
| Task execution cancelled manually/by API request. |
| Task execution finished due to at least one failed action execution and no retries configured/left to process. |
Model describing an AutomationEngine workflow execution event. Workflow execution events are stored in the dt.system.events table.
AutomationEngine workflow execution state change.
fetch dt.system.events| filter event.kind == "WORKFLOW_EVENT" and event.provider == "AUTOMATION_ENGINE" and event.type =="WORKFLOW_EXECUTION"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe unique identifier of the root workflow. |
|
| string | experimentalThe unique identifier of the execution of the root workflow. |
|
| string | experimentalThe state of an execution. Values depend on type of execution (workflow-, task-, or action execution). |
|
| boolean | experimentalIndicates if |
|
| string | experimentalAdditional info about current state of execution. Typically holds error details. |
|
| string | experimentalThe unique identifier of a workflow as UUID. |
|
| boolean | experimentalIndicates if the workflow execution state has changed since the last execution, ignoring draft executions. Always false for draft executions. |
|
| string | experimentalThe title of the workflow. |
|
| string | experimentalWorkflow type, either SIMPLE or STANDARD, where SIMPLE comes with restrictions. |
|
| string | experimentalThe unique identifier of a workflow execution as UUID. |
|
| string | experimentalThe identifier that describes the trigger of the workflow. |
|
| string | experimentalThe unique identifier of the user who triggered the workflow execution manually/via API. |
|
| string | experimentalThe unique identifier of the workflow that triggered the workflow execution. |
|
| string[] | resource experimentalCollects the identifiers of all pipelines through which a record has passed during the ingestion process in OpenPipeline, providing a complete trace of its journey. |
|
| string | resource experimentalIdentifies the source (such as API endpoints or OneAgent) used for ingesting the record into OpenPipeline. |
|
| duration | stableThe difference between |
|
| timestamp | stableEnd time of a data point. Value is a UNIX Epoch time in nanoseconds and greater or equal to the |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| timestamp | stableStart time of a data point. Value is a UNIX Epoch time in nanoseconds and less or equal to the |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Event in context of a workflow |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| Event produced by AutomationEngine |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Workflow execution state change event |
dt.automation_engine.state MUST be one of the following:
| Value | Description |
|---|---|
| Workflow execution started. |
| Workflow execution finished successfully. |
| Workflow execution failed due to at least one branch with a failed task without an on error successor. |
| Workflow execution cancelled manually/by API request. |
Model describing an AutomationEngine workflow lifecycle event. Workflow lifecycle events are stored in the dt.system.events table.
AutomationEngine workflow lifecycle events.
fetch dt.system.events| filter event.kind == "WORKFLOW_EVENT" and event.provider == "AUTOMATION_ENGINE" and in(event.type, array("WORKFLOW_CREATED", "WORKFLOW_UPDATED", "WORKFLOW_DELETED"))
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalThe unique identifier of a workflow as UUID. |
|
| string | experimentalThe title of the workflow. |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableUnique UUID of a human user. If the system itself has to be represented, the constant 'system' is used. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Event in context of a workflow |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| Event produced by AutomationEngine |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Workflow created event |
| Workflow updated event |
| Workflow deleted event |
Model describing an AutomationEngine workflow throttle event. Workflow throttle events are stored in the dt.system.events table.
AutomationEngine workflow throttle events.
fetch dt.system.events| filter event.kind == "WORKFLOW_EVENT" and event.provider == "AUTOMATION_ENGINE" and event.type =="WORKFLOW_THROTTLE"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | experimentalThe workflow execution per hour limit that has been reached. |
|
| string | experimentalThe unique identifier of a workflow as UUID. |
|
| string | experimentalThe title of the workflow. |
|
| timestamp | stableEnd time of a data point. Value is a UNIX Epoch time in nanoseconds and greater or equal to the |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Event in context of a workflow |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| Event produced by AutomationEngine |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Workflow throttled event |
Dynatrace stores a data deletion event for each segment that got rewritten in the dt.system.events table.
Analyze data deletion events.
fetch dt.system.events| filter event.kind == "DATA_DELETION_EVENT"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalA Dynatrace Grail bucket name. |
|
| string | stableThe REST API version used by the client to perform the request. |
|
| long | experimentalEnd of a particular deletion. |
|
| string | experimentalInternal deletion request UUID. |
|
| long | experimentalStart of a particular deletion. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: | |
| string | experimentalA Dynatrace environment/tenant ID. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | experimentalAdditional information if query execution has 'FAILED'. |
|
| string | experimentalThe query string. |
|
| long | experimentalThe number of rewritten bytes in the context of record deletion. |
|
| string | experimentalThe outcome of the query. |
|
| string | experimentalDeletion task UUID returned by API. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableEmail of the user. |
|
| string | stableUnique UUID of a human user. If the system itself has to be represented, the constant 'system' is used. |
|
| string | resource deprecatedUsed in Extension Framework 2.0The SNMP version. |
|
Events that are generated by Dynatrace components with self-monitoring information (health, status, unexpected situations)
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalUnstructured content of the record. It should contain a human-readable message. Often it is the raw version of a record read from a source. |
|
| string | resource experimentalThe name of a group that the ActiveGate instance belongs to. |
|
| string | resource stableAn entity ID of an entity of type HOST.Tags: |
|
| string | experimentalPreregistered event key for self-monitoring events whitelisting. |
|
| string | resource experimentalExtension's monitoring configuration identifier. |
|
| string | resource experimentalName of the data source. |
|
| string | resource experimentalName of the extension. |
|
| string | resource experimentalThe status of the component reporting a self-monitoring event. |
|
| string | resource stableThe ID of the entity considered the source of the signal. The string represents an entity ID of an entity that is stored in the classic entity storage. 1Tags: |
|
| string | stableHuman-readable attribute that identifies a log stream. 2Tags: |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
The value of this field will be based on one of the dt.entity.<type> fields value. This means that both dt.source_entity and dt.entity.<type> fields will be set to the same ID.
Can contain, for example, a file path, standard output, or an URI etc., depending on the log stream type. The value should be stable for one logical source (for example, not affected by log file rotation digits).
Dynatrace stores an enrichment execution event for the enrichment of threat observables in the dt.system.events table.
Analyze enrichment execution events.
fetch dt.system.events| filter event.kind == "ENRICHMENT_EXECUTION_EVENT"
The number of successful enrichments.
fetch dt.system.events| filter event.kind == "ENRICHMENT_EXECUTION_EVENT"| filter event.outcome == "success"| summarize count()
The number of failed enrichments.
fetch dt.system.events| filter event.kind == "ENRICHMENT_EXECUTION_EVENT"| filter event.outcome == "failure"| summarize count()
The number of enrichments by integration app.
fetch dt.system.events| filter event.kind == "ENRICHMENT_EXECUTION_EVENT"| summarize count(), by: {dt.enrichment.integration.id}
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource stableThe unique application identifier of the app that triggered the enrichment. Dynatrace apps are prefixed with 'dynatrace.', custom apps are prefixed with 'my.'. |
|
| duration | experimentalThe duration of the enrichment execution in nanoseconds. |
|
| string | experimentalThe identifier of the connection settings object used to execute the enrichment. The connection settings object ID refers to the connection in the settings section of the integration app. |
|
| string | experimentalThe unique application identifier of the integration app that provided the enrichment functionality. Dynatrace apps are prefixed with 'dynatrace.', custom apps are prefixed with 'my.'. |
|
| string | experimentalThe integration method ID of the integration app used to execute the enrichment. |
|
| boolean | experimentalIndicates whether the enrichment execution result was retrieved from the cache. |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableDenotes whether the event represents a success or a failure from the perspective of the entity that produced the event (for example an HTTP response code). |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableDescribes why a certain event.outcome was set. Typically, this is some form of error description in the case of a failure. |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableUnique UUID of a human user. If the system itself has to be represented, the constant 'system' is used. |
|
Model describing a billing usage event of ingest for events. Billing usage events are stored in the dt.system.events table.
Analyze billing usage events for the "Events - Ingest & Process" capability.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Events - Ingest & Process"| dedup event.id
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableThe number of bytes that will be billed. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableDisplay name for usage details. |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableStart time of the usage timeframe (inclusive). |
|
| string | stableA Dynatrace Grail usage event bucket name. |
|
| timestamp | experimentalEnd time of the usage timeframe (exclusive). |
|
| string | **deprecatedwill be replaced by usage.bucket.**A Dynatrace Grail usage event bucket name. |
|
| timestamp | experimentalStart time of the usage timeframe (inclusive). |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Client Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Events - Ingest & Process |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing a billing usage event of a events query execution. Billing usage events are stored in the dt.system.events table.
Analyze billing usage events.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Events - Query"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableIndicates if the query was executed to fetch records or to delete them. |
|
| long | stableThe number of bytes that will be billed. |
|
| string | stableA Dynatrace app ID. |
|
| string | stableName of the function that executed the query. |
|
| string | stableDynatrace application that executed the query. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableDisplay name for usage details. |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| string | stableThe UUID identifying a particular query. |
|
| long | stableQuery start time. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableA Dynatrace Grail usage event bucket name. |
|
| string | stableEmail of the user. |
|
| string | stableUnique UUID of a human user. If the system itself has to be represented, the constant 'system' is used. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Events Query Execution |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing the billing usage event for retention of events per Grail bucket. Billing usage events are stored in the dt.system.events table.
Analyze billing usage events.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Events - Retain"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableThe number of bytes that will be billed. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableDisplay name for usage details. |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableA Dynatrace Grail usage event bucket name. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Events Retain |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing a billing usage event for the Foundation & Discovery DPS capability.
Billing usage events are stored in the dt.system.events table.
Analyze billing usage for Foundation & Discovery on 15-minute billing intervals.
Note that complete usage for events is displayed only for Dynatrace versions 1.312+. Earlier versions will display partial usage.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Foundation & Discovery"| dedup event.id
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableHow many host hours of the capability have been consumed by the host. |
|
| string | resource stableCan be used to assign usage to a Cost Center. |
|
| string | resource stableCan be used to assign usage to a Product or Application ID. |
|
| string | resource stableAn entity ID of an entity of type HOST.Tags: |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| timestamp | experimentalEnd time of the usage timeframe (exclusive). |
|
| timestamp | experimentalStart time of the usage timeframe (inclusive). |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Client Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Foundation & Discovery |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing a billing usage event for the Full-Stack Monitoring DPS capability.
Billing usage events are stored in the dt.system.events table.
Analyze billing usage for Full-Stack Monitoring on 15-minute billing intervals.
Note that complete usage for events is displayed only for Dynatrace versions 1.312+. Earlier versions will display partial usage.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Full-Stack Monitoring"| dedup event.id
| Attribute | Type | Description | Examples |
|---|---|---|---|
| double | stableHow many gibibyte hours of the capability has been consumed by the host |
|
| string | resource stableCan be used to assign usage to a Cost Center. |
|
| string | resource stableCan be used to assign usage to a Product or Application ID. |
|
| string | resource stableAn entity ID of an entity of type HOST.Tags: |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| timestamp | experimentalEnd time of the usage timeframe (exclusive). |
|
| timestamp | experimentalStart time of the usage timeframe (inclusive). |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Client Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Full-Stack Monitoring |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
GenAI events are emitted when a GenAI skill is invoked or feedback is provided. They provide tracking data for skill usage and user feedback. Examples:
Retrieve all GenAI events.
fetch dt.system.events| filter event.kind == "GENAI_EVENT"
Count of GenAI skill invocations.
fetch dt.system.events| filter event.kind == "GENAI_EVENT"| filter event.type == "GenAi Skill Invocation"| summarize count()
Count the GenAI invocations per skill.
fetch dt.system.events| filter event.kind == "GENAI_EVENT"| filter event.type == "GenAi Skill Invocation"| summarize invocations=count(), by: skill
Count of the GenAI feedback type per skill.
fetch dt.system.events| filter event.kind == "GENAI_EVENT"| filter event.type == "GenAi Feedback"| summarize count(), by: {feedback.type, skill}
Time series of the GenAI execution duration per skill.
fetch dt.system.events| filter event.kind == "GENAI_EVENT"| filter event.type == "GenAi Skill Invocation"| makeTimeseries avg(execution_duration_ms), by: {skill}
Count of MCP initializations.
fetch dt.system.events| filter event.kind == "GENAI_EVENT"| filter event.type == "MCP Init"| summarize count()
Count the MCP initializations per client.application_context.
fetch dt.system.events| filter event.kind == "GENAI_EVENT"| filter event.type == "MCP Init"| summarize invocations=count(), by: client.application_context
Count of MCP Tool Invocations.
fetch dt.system.events| filter event.kind == "GENAI_EVENT"| filter event.type == "MCP Tool Invocation"| summarize count()
Count the MCP Tool Invocations per tool.
fetch dt.system.events| filter event.kind == "GENAI_EVENT"| filter event.type == "MCP Tool Invocation"| summarize invocations=count(), by: tool
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableA Dynatrace app ID. |
|
| string | experimentalName of the originating application if the conversation started from another app. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| long | deprecatedThe duration of the query in milliseconds. |
|
| string | experimentalDetailed error message or justification for failure, intended for end users. |
|
| string | experimentalAdditional information if query execution has 'FAILED'. |
|
| string | experimentalCategory of feedback, selected by the user. |
|
| string | experimentalUnmasked free-text feedback provided by the user. |
|
| string | experimentalType of feedback provided by the user, such as positive or negative. |
|
| string | experimentalAn MCP Client name |
|
| string | experimentalAn MCP Client version |
|
| string | experimentalThe response was generated by the skill. |
|
| string | experimentalThe name of the MCP server that was invoked. |
|
| string | experimentalThe name of the skill that was executed. |
|
| string | experimentalThe outcome of the query. |
|
| string | experimentalAdditional context information was provided for the skill (chat only). |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | experimentalThe name of the MCP server tool that was invoked. |
|
| string | experimentalGeneral topic addressed by the user input (for chat events only). |
|
| string | stableEmail of the user. |
|
| string | stableUnique UUID of a human user. If the system itself has to be represented, the constant 'system' is used. |
|
| string | experimentalThe user input was provided for the skill. |
|
event.type MUST be one of the following:
| Value | Description |
|---|---|
| GenAI skill was invoked. |
| Feedback for a GenAI skill was provided. |
skill MAY be one of the following:
| Value | Description |
|---|---|
| Events associated with the conversations skill also used in the Davis CoPilot Chat App. |
| Events associated with the skill translating natural language into DQL queries. |
| Events associated with the skill explaining DQL queries in natural text. |
status MUST be one of the following:
| Value | Description |
|---|---|
| Skill invocation succeeded. |
| Skill invocation failed. |
failure_reason MAY be one of the following:
| Value | Description |
|---|---|
| There was a technical problem. |
| Content filter check failed. |
| Guardrail check failed. |
| Generated DQL was invalid. |
feedback.type MUST be one of the following:
| Value | Description |
|---|---|
| Positive feedback. |
| Negative feedback. |
feedback.category MAY be one of the following:
| Value | Description |
|---|---|
| The execution of the skill did not work. |
| The response was incomplete. |
| The response was incorrect. |
| The response misunderstood the question. |
| No provided feedback category fits. |
Model describing a billing usage event for the Infrastructure Monitoring DPS capability.
Billing usage events are stored in the dt.system.events table.
Analyze billing usage for Infrastructure Monitoring on 15-minute billing intervals.
Note that complete usage for events is displayed only for Dynatrace versions 1.312+. Earlier versions will display partial usage.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Infrastructure Monitoring"| dedup event.id
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableHow many host hours of the capability have been consumed by the host. |
|
| string | resource stableCan be used to assign usage to a Cost Center. |
|
| string | resource stableCan be used to assign usage to a Product or Application ID. |
|
| string | resource stableAn entity ID of an entity of type HOST.Tags: |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| timestamp | experimentalEnd time of the usage timeframe (exclusive). |
|
| timestamp | experimentalStart time of the usage timeframe (inclusive). |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Client Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Infrastructure Monitoring |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing a billing usage event of a logs query execution. Billing usage events are stored in the dt.system.events table.
Analyze billing usage events.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Log Management & Analytics - Query"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableIndicates if the query was executed to fetch records or to delete them. |
|
| long | stableThe number of bytes that will be billed. |
|
| string | stableA Dynatrace app ID. |
|
| string | stableName of the function that executed the query. |
|
| string | stableDynatrace application that executed the query. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| string | stableThe UUID identifying a particular query. |
|
| long | stableQuery start time. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableEmail of the user. |
|
| string | stableUnique UUID of a human user. If the system itself has to be represented, the constant 'system' is used. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Logs Query Execution |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing the billing usage event for retention of events per Grail bucket. Billing usage events are stored in the dt.system.events table.
Fetch Log Management & Analytics - Retain billing usage events.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Log Management & Analytics - Retain"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableThe number of bytes that will be billed. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableA Dynatrace Grail usage log bucket name. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Logs Retain |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing the billing usage event for retention of events per Grail bucket. Billing usage events are stored in the dt.system.events table.
Fetch Log Management & Analytics - Retain with Included Queries usage events.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Log Management & Analytics - Retain with Included Queries"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableThe number of bytes that will be billed. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableA Dynatrace Grail usage log bucket name. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Retain with Included Queries |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing a billing usage event of ingest & process for metrics. Billing usage events are stored in the dt.system.events table.
Analyze billing usage events.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Metrics - Ingest & Process"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableThe number of billable metrics data points. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| string | stableIdentifies the type of metric and therefore the timeseries rollup functions it supports. |
|
| string | stableMonitoring source that originally reported the data. See 'dt.system.monitoring_source'. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableA Dynatrace Grail usage metrics bucket name. |
|
| timestamp | experimentalEnd time of the usage timeframe (exclusive). |
|
| timestamp | experimentalStart time of the usage timeframe (inclusive). |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Metrics - Ingest & Process |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing the billing usage event for retention of metrics per Grail bucket. Billing usage events are stored in the dt.system.events table.
Fetch Metrics Retain billing usage events.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Metrics - Retain"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableThe number of bytes that will be billed. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableA Dynatrace Grail usage metric bucket name. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Metrics Retain |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Dynatrace stores a query execution event for each query that got executed in the dt.system.events table.
Analyze query execution events.
fetch dt.system.events| filter event.kind == "QUERY_EXECUTION_EVENT"
The amount of succeeded queries.
fetch dt.system.events| filter event.kind == "QUERY_EXECUTION_EVENT"| filter status == "SUCCEEDED"| summarize countDistinct(query_id)
The amount of failed queries.
fetch dt.system.events| filter event.kind == "QUERY_EXECUTION_EVENT"| summarize sum(failed_count)
| Attribute | Type | Description | Examples |
|---|---|---|---|
| timestamp | experimentalEnd time of query analysis timeframe. |
|
| timestamp | experimentalStart time of query analysis timeframe. |
|
| string | experimentalA Dynatrace Grail bucket name. |
|
| string | stableThe REST API version used by the client to perform the request. |
|
| string | stableA Dynatrace app ID. |
|
| string | stableName of the function that executed the query. |
|
| string | experimentalA string that identifies the Dynatrace service that triggered the query. |
|
| string | stableDynatrace application that executed the query. |
|
| long | experimentalThe number of records returned by the query. Might differ from actual number of records delivered to the client due to the additional response size limits (max result bytes, max result records, etc.). |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: | |
| string | experimentalA Dynatrace environment/tenant ID. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| long | deprecatedThe duration of the query in milliseconds. |
|
| long | experimentalNumber of failed queries represented by the record. |
|
| string | experimentalAdditional information if query execution has 'FAILED'. |
|
| long | stableQuery end time. For aggregated events the query end time may be zero and not reflect the exact end time. |
|
| string | stableThe UUID identifying a particular query. For aggregated events this field is null. |
|
| string | experimentalThe resource pool of the query. |
|
| long | deprecatedThe time query spent in queued state (in milliseconds). |
|
| long | stableQuery start time. For failed queries the start time may be aggregated and not reflect the exact start time but rather the aggregation time. |
|
| string | experimentalThe query string. For aggregated events this field is null. |
|
| long | experimentalThe sampling ratio of the executed query. |
|
| long | experimentalThe number of scanned bytes. |
|
| long | experimentalNumber of scanned data points for metric queries. |
|
| long | experimentalThe number of scanned records. |
|
| string | experimentalThe outcome of the query. |
|
| string | experimentalA Dynatrace Grail table name. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | experimentalThe user ID that triggered the query. For aggregated events this field is null. |
|
| string | stableThe user email that triggered the query. For aggregated events this field is null. |
|
| string | stableThe user UUID that triggered the query. For aggregated events this field is null. |
|
| string | resource deprecatedUsed in Extension Framework 2.0The record version |
|
failure_reason MUST be one of the following:
| Value | Description |
|---|---|
| Query timed out before execution due to resource or tenant quota limit. |
| Query was rejected due to too many queries waiting in the queue. Reported either as records with full details or as aggregated batches with limited metadata. |
| Query cannot be parsed due to a syntax error. |
| Query cannot be parsed because it exceeds the complexity limit of the parser. |
| Query cannot be parsed due to an internal error. |
| Execution of the submitted query failed because of internal an error. |
| Query cannot be executed because the requester doesn't have permissions to a queried table. |
| Query execution was canceled because it exceeded the allowed running time. |
| Query execution was canceled because memory usage limit is exceeded. |
| Query execution was canceled because of user-defined functions limit is exceeded. |
| Query execution was canceled because record size limit is exceeded. |
| Query execution was canceled because table size limit is exceeded. |
| Query execution was canceled because the condition of a failIf command was met. |
Model describing a billing usage event for the Runtime Application Protection DPS capability.
Billing usage events are stored in the dt.system.events table.
Analyze billing usage for Runtime Application Protection on 15-minute billing intervals.
Note that complete usage for events is displayed only for Dynatrace versions 1.312+. Earlier versions will display partial usage.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Runtime Application Protection"| dedup event.id
| Attribute | Type | Description | Examples |
|---|---|---|---|
| double | stableHow many gibibyte hours of the capability has been consumed by the host |
|
| string | resource stableCan be used to assign usage to a Cost Center. |
|
| string | resource stableCan be used to assign usage to a Product or Application ID. |
|
| string | resource stableAn entity ID of an entity of type HOST.Tags: |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| timestamp | experimentalEnd time of the usage timeframe (exclusive). |
|
| timestamp | experimentalStart time of the usage timeframe (inclusive). |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Client Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Runtime Application Protection |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing a billing usage event for the Runtime Vulnerability Analytics DPS capability.
Billing usage events are stored in the dt.system.events table.
Analyze billing usage for Runtime Vulnerability Analytics on 15-minute billing intervals.
Note that complete usage for events is displayed only for Dynatrace versions 1.312+. Earlier versions will display partial usage.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Runtime Vulnerability Analytics"| dedup event.id
| Attribute | Type | Description | Examples |
|---|---|---|---|
| double | stableHow many gibibyte hours of the capability has been consumed by the host |
|
| string | resource stableCan be used to assign usage to a Cost Center. |
|
| string | resource stableCan be used to assign usage to a Product or Application ID. |
|
| string | resource stableAn entity ID of an entity of type HOST.Tags: |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| timestamp | experimentalEnd time of the usage timeframe (exclusive). |
|
| timestamp | experimentalStart time of the usage timeframe (inclusive). |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Client Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Runtime Vulnerability Protection |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing a billing usage event for Security Posture Management. Billing usage events are stored in the dt.system.events table.
Analyze usage events for the "Security Posture Management" capability.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Security Posture Management"| dedup event.id
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource stableAn entity ID of an entity of type KUBERNETES_CLUSTER.Tags: |
|
| string | resource stableAn entity ID of an entity of type KUBERNETES_NODE.Tags: |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Security Posture Management |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing a billing usage event for ingest and process of traces. Billing usage events are stored in the dt.system.events table.
Analyze billing usage events for the "Traces - Ingest & Process" capability.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Traces - Ingest & Process"| dedup event.id
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| long | experimentalThe size in bytes of ingested spans. |
|
| long | experimentalThe number of ingested spans. |
|
| string | experimentalThe origin/type of the ingested spans. |
|
| timestamp | stableStart time of the usage timeframe (inclusive). |
|
| timestamp | experimentalEnd time of the usage timeframe (exclusive). |
|
| timestamp | experimentalStart time of the usage timeframe (inclusive). |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Client Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Traces - Ingest & Process |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
licensing_type MUST be one of the following:
| Value | Description |
|---|---|
| The |
| The |
| The |
| The |
Model describing a billing usage event of a traces query execution. Billing usage events are stored in the dt.system.events table.
Analyze billing usage events.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Traces - Query"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableIndicates if the query was executed to fetch records or to delete them. |
|
| long | stableThe number of bytes that will be billed. |
|
| string | stableA Dynatrace app ID. |
|
| string | stableName of the function that executed the query. |
|
| string | stableDynatrace application that executed the query. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| string | stableThe UUID identifying a particular query. |
|
| long | stableQuery start time. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableEmail of the user. |
|
| string | stableUnique UUID of a human user. If the system itself has to be represented, the constant 'system' is used. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Traces Query Execution |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
Model describing the billing usage event for retention of events per Grail bucket. Billing usage events are stored in the dt.system.events table.
Analyze billing usage events.
fetch dt.system.events| filter event.kind == "BILLING_USAGE_EVENT" and event.type == "Traces - Retain"
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableThe number of bytes that will be billed. |
|
| string | resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: |
|
| string | stableUnique identifier string of an event; is stable across multiple refreshes and updates. |
|
| string | stableGives high-level information about what kind of information the event contains without being specific about the contents of the event. It helps to determine the record type of a raw event.Tags: |
|
| string | stableSource of the event, for example, the name of the component or system that generated the event.Tags: |
|
| string | stableThe unique type identifier of a given event.Tags: |
|
| string | stableDescribes the version of the event. |
|
| timestamp | stableThe time (UNIX Epoch time in nanoseconds) when the event originated, typically when the source created it. If no original timestamp is available, it will be populated at ingest time and required for all events. In the case of a correlated event (for example, ITIL events), this time could be different from the event.start time, as this time represents the actual timestamp when the "update" for the event was created. |
|
| string | stableA Dynatrace Grail usage span bucket name. |
|
event.kind MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |
event.provider MUST be one of the following:
| Value | Description |
|---|---|
| LIMA Usage Stream Service |
event.type MUST be one of the following:
| Value | Description |
|---|---|
| Traces Retain |
dt.security_context MUST be one of the following:
| Value | Description |
|---|---|
| Billing usage event |