Dynatrace SaaS version 1.253+
Dynatrace automatically enriches business events with additional context to enhance analysis and facilitate drill-down navigation. Specifically, Dynatrace adds certain properties to your business events, for example, information on geolocation, operating system, application, and more. You can then use Dynatrace Query Language (DQL) to analyze your business events.
Fields defined in the table below can be used to enrich business events. Some fields are automatically added depending on their source (OneAgent or API).
| Key | Added via | Description | Example | Data type |
|---|---|---|---|---|
| OneAgent | Time when the event originated, typically when it was created by the source2 |
| timestamp |
| API | Time when the event originated, typically when it was created by the source2 |
| timestamp |
| OneAgent | Host where OneAgent captured the event |
| string |
| OneAgent | Process group instance where OneAgent captured the event |
| string |
| OneAgent API | Unique identifier of the event autogenerated by Dynatrace (for OneAgent) |
| string |
| OneAgent API | High-level kind of the event; the field is always set to |
| string |
| OneAgent API | Source of the event, for example, the name of the component or system that generated the event; the default value is |
| string |
| OneAgent API | Event type identifier; the default value is |
| string |
| OneAgent API | Event category; the default value is |
| string |
| OneAgent | ID of the request as known by the caller; autogenerated by Dynatrace |
| string |
| OneAgent | ID of the whole trace forest that is used to uniquely identify a distributed trace through a system; autogenerated by Dynatrace |
| string |
| OneAgent | Indicates if the caller has recorded the trace data; autogenerated by Dynatrace |
| bool |
| OneAgent | Field that identifies the incoming request in a tracing system; autogenerated by Dynatrace |
| string |
Not an enriched field per se, but required by the Dynatrace internal schema
If no original timestamp is available, it's populated at ingest time.
Set by OneAgent and required by CloudEvents specification, but not enforced by the Dynatrace internal schema
Business events reported via RUM are enriched with fields relevant to the device and user, such as geolocation, device, browser, and application. The following fields are added automatically, depending on the application type—web or mobile.
The top-level fields contain generally relevant information for all events and data points.
If no original timestamp is available, it's populated at ingest time.
Unix timestamp in nanoseconds
The event namespace contains common identification, categorization, and context on events in Dynatrace.
| Key | Description | Example | Data type | Override possible | Required or optional | Available for |
|---|---|---|---|---|---|---|
| Type identifier of the event |
| string | N/A | req |
|
| Unique identifier of the event |
| string | req |
| |
| High-level kind of the event |
| string | opt |
| |
| Source of the event, for example, the name of the component or system that generated the event2 |
| string | opt |
|
Not enriched automatically; you set it via API when you report a business event.
Full domain name for web, app bundle for mobile, and application ID for OpenKit
The dt.rum namespace contains Dynatrace RUM-specific fields.
| Key | Description | Example | Data type | Override possible | Required or optional | Available for |
|---|---|---|---|---|---|---|
| Version of the event |
| string | req |
| |
| ID of the Dynatrace RUM application |
| string | req |
| |
| ID of the RUM application instance1 |
| string | req2 |
| |
| ID of the user session |
| string | req2 |
|
Also known as the internal user ID or visitor ID
If available
The device namespace contains information on the device running an application.
| Key | Description | Example | Data type | Override possible | Required or optional | Available for |
|---|---|---|---|---|---|---|
| Name of the device manufacturer |
| string | opt |
| |
| Model identifier of the device |
| string | opt |
| |
| Indicates if a rooted device was detected. |
| bool | opt |
|
The os namespace contains information on the operating system running an application.
| Key | Description | Example | Data type | Override possible | Required or optional | Available for |
|---|---|---|---|---|---|---|
| Operating system name |
| string | opt |
| |
| Operating system version |
| string | opt |
|
The browser namespace contains information on the browser running an application.
| Key | Description | Example | Data type | Override possible | Required or optional | Available for |
|---|---|---|---|---|---|---|
| Browser name |
| string | opt |
| |
| Detected browser version |
| string | opt |
| |
| Type of browser1 |
| string | opt |
| |
| Full user agent string as provided by the browser |
| string | opt |
|
Possible values: desktop, mobile, tablet, robot, other
The client namespace contains information on the initiator of a network connection.
| Key | Description | Example | Data type | Override possible | Required or optional | Available for |
|---|---|---|---|---|---|---|
| IP address of the client (IPv4 or IPv6) |
| string | opt |
|
The app namespace contains information on the application sending the business event.
| Key | Description | Example | Data type | Override possible | Required or optional | Available for |
|---|---|---|---|---|---|---|
| Full machine-readable version of the application |
| string | opt |
| |
| Short human-readable version of the application |
| string | opt |
| |
| Name of the bundle or package |
| string | opt |
|
The geo namespace contains geolocation information.
| Key | Description | Example | Data type | Override possible | Required or optional | Available for |
|---|---|---|---|---|---|---|
| Full continent name |
| string | opt |
| |
| Full country name |
| string | opt |
| |
| Full region name |
| string | opt |
| |
| Full city name |
| string | opt |
|