Global field reference

The following reference contains a list of global fields that have a well defined semantic meaning in Dynatrace and can be used across different monitoring types. The fields are organized in namespaces that are separated with dots.

Top level fields

The top level fields contain generally relevant information for all monitoring data

Attribute	Type	Description	Examples
`timestamp`	timestamp	stable The time (UNIX Epoch time in nanoseconds) when the event originated, typically when it was created by the source. If no original timestamp is available, it will be populated at ingest time. Required for all events. In case of a correlated event (e.g. 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.	`1649822520123123123`
`timeframe`	record[]	stable The timeframe represented by a timeseries record.
`start_time`	timestamp	stable Start time of a data point. Value is an UNIX Epoch time in nanoseconds and less or equal the `end_time`.	`1649822520123123123`
`end_time`	timestamp	stable End time of a data point. Value is an UNIX Epoch time in nanoseconds and greater or equal the `start_time`.	`1649822520123123165`
`duration`	duration	stable The difference of `start_time` and `end_time` in nanoseconds.	`42`
`interval`	string	stable Denotes the timeframe of represented by individual timeseries measurements returned by a timeseries record.	`1 min`

Adobe

Fields

Attribute	Type	Description	Examples
`adobe.em.env_type`	string	experimental Adobe Experience Manager (AEM) environment type.	`dev`; `stage`; `prod`
`adobe.em.program`	string	experimental Adobe Experience Manager (AEM) service. Contains the customer defined name of the AEM environment.
`adobe.em.service`	string	experimental Adobe Experience Manager (AEM) service. Contains the program and environment IDs the customer is exposed to.
`adobe.em.tier`	string	experimental Adobe Experience Manager (AEM) tier.	`author`; `publish`; `preview`

Aggregation

OneAgent might aggregate spans having the same parent span into a single one. The aggregated span contains attributes to indicated that aggregation happened and to allow to reconstruct details.

For aggregated spans the start_time holds the earliest start_time, end_time holds the latest end_time of all aggregated spans.

Fields

Attribute	Type	Description	Examples
`aggregation.count`	long	experimental The number of spans aggregated into the this span. This means this span represents multiple spans therefore value is >1.	`3`
`aggregation.exception_count`	long	experimental The number of aggregated spans which included an exception.	`0`; `6`
`aggregation.duration_sum`	duration	experimental The duration sum in nanoseconds for all aggregated spans.	`123`
`aggregation.duration_min`	duration	experimental The duration in nanoseconds for shortest aggregated span.	`42`
`aggregation.duration_max`	duration	experimental The duration in nanoseconds for longest aggregated span.	`482`
`aggregation.parallel_execution`	boolean	experimental `true` indicates that aggregated spans may have been executed in parallel. Therefore `start_time + duration_sum` may exceed `end_time`.
`aggregation.duration_samples`	duration[]	experimental Array of reservoir sampled span durations of the aggregated spans. The duration samples can be used to estimate a more accurate duration distribution of aggregated spans rather then using the average value.	`[42, 482, 301]`

Apache HTTP Server

Fields

Attribute	Type	Description	Examples
`apache.httpd.config.path`	string	experimental None

Apache Spark

Fields

Attribute	Type	Description	Examples
`apache.spark.master.ip`	string	experimental None

Apache Tomcat

Fields

Attribute	Type	Description	Examples
`apache.tomcat.base`	string	experimental The server's base directory. This is what usually is referred to as CATALINA_BASE.	`/usr/share/tomcat6`
`apache.tomcat.home`	string	experimental The server's home directory. This is what usually is referred to as CATALINA_HOME.	`/usr/share/tomcat6`

App

The app namespace contains information on the application sending the event.

Fields

Attribute	Type	Description	Examples
`app.bundle`	string	stable Name of the bundle or package.	`com.example.easytravel`
`app.version`	string	stable Full version of the application. This can include more verbose information, such as the build number.	`5.23.15789`
`app.short_version`	string	stable Human readable version of the application, usually major & minor version.	`5.23`
`app.id`	string	stable The unique application identifier. Dynatrace apps are prefixed with 'dynatrace.', custom apps are prefixed with 'my.'	`dynatrace.notebooks`; `my.awesome.app`

ASP.NET Core

Fields

Attribute	Type	Description	Examples
`aspnetcore.appl.path`	string	experimental None

Authentication

Authentication type and method used to login to a Dynatrace system.

Fields

Attribute	Type	Description	Examples
`authentication.type`	string	experimental The method of authentication.	`OAUTH2`
`authentication.grant.type`	string	experimental The grant type used during OAuth2 authentication.	`AUTHORIZATION_CODE`; `CLIENT_CREDENTIALS`
`authentication.client.id`	string	experimental The OAuth2 client id if of type 'CLIENT_CREDENTIALS'.	`dt0s02.UZCK6ENL.2YQ2A3DZUEISRJSUU5544J3SC3TMPXSEEMNA5HK7RW54SJ6XKLYGMWJNKL7B2DNH`
`authentication.token`	string	experimental The public token identifier of authentication.type 'TOKEN'.	`dt0c01.AM4SEYKIBROBEJ2N3HAXZ4IX`

authentication.type MUST be one of the following:

Value	Description
`DEVOPSTOKEN`	Authenticated via DevOps token
`NONE`	Not authenticated (authentication not necessary)
`OAUTH2`	The OAuth 2.0 authentication type grant type
`TOKEN`	Authenticated via URL token

authentication.grant.type MUST be one of the following:

Value	Description
`AUTHORIZATION_CODE`	The OAuth 2.0 "Authorization Code" grant type
`CLIENT_CREDENTIALS`	The OAuth 2.0 "Client Credentials" grant type

authentication.client.id and authentication.token MUST follow the Dynatrace token format definition.

Specifically, authentication.client.id MUST be prefixed with dt0s02.

Amazon Web Services (AWS)

Fields that can come from applications running on AWS.

Fields

Resource attributes

Attribute	Type	Description	Examples
`aws.ecr.account.id`	string	experimental None
`aws.ecr.region`	string	experimental None
`aws.ecs.cluster`	string	experimental None
`aws.ecs.container.name`	string	experimental None
`aws.ecs.family`	string	experimental None
`aws.ecs.revision`	string	experimental None
`aws.ecs.task.arn`	string	experimental The full Amazon Resource Name (ARN) of the task to which the container belongs.	`arn:aws:ecs:us-west-2:111122223333:task/default/cd189a933e5849daa93386466019ab50`
`aws.ecs.docker.name`	string	experimental The name of the container supplied to Docker.	`curl-image`
`aws.ecs.container.arn`	string	experimental The full Amazon Resource Name (ARN) of the container.	`arn:aws:ecs:us-west-2:111122223333:container/05966557-f16c-49cb-9352-24b3a0dcd0e1`
`aws.ecs.docker.id`	string	experimental The Docker ID for the container.	`cd189a933e5849daa93386466019ab50-2495160603`
`aws.lambda.function.name`	string	experimental None
`aws.lambda.initialization_type`	string	experimental The AWS Lambda initialization type. See AWS_LAMBDA_INITIALIZATION_TYPE.	`snap_start`
`aws.region`	string	experimental A specific geographical AWS Cloud location.	`us-east-1`
`aws.account.id`	string	experimental A 12-digit number, such as 123456789012, that uniquely identifies an AWS account.	`123456789012`
`aws.availability_zone`	string	experimental A specific availability zone in given AWS region.	`us‑east‑1a`; `us‑east‑1b`
`aws.log_group`	string	experimental Amazon CloudWatch group of log streams that share the same retention, monitoring, and access control settings.	`/aws/lambda/a-SomeFumction-1AWHD6W1QC5DH`
`aws.log_stream`	string	experimental A sequence of log events that share the same source.	`2021/01/04/[$LATEST]b2e34f11da04232cb9f9d3d5799a5c12`
`aws.service`	string	experimental The service that identifies the AWS product.	`s3`
`aws.resource.type`	string	experimental The name of a resource type	`group`; `cluster`; `instance`
`aws.resource.id`	string	experimental The unique identifier of the resource	`i-0922cda4579db3a45`
`aws.resource.name`	string	experimental The name of the resource - value of Name tag in AWS	`my-ec2-instance`
`aws.arn`	string	experimental Amazon Resource Name (ARN)	`arn:aws:lambda:us-east-1:478983378254:function:acceptanceWeatherBackend`
`aws.alb.name`	string	experimental Application load balancer name that instance is behind	`my-alb`

aws.lambda.initialization_type MUST be one of the following:

Value	Description
`on_demand`	On demand
`provisioned_concurrency`	Provisioned concurrency
`snap_start`	SnapStart

Span attributes

Attribute	Type	Description	Examples
`aws.x_amzn_trace_id`	string	experimental Contains the `X-Amzn-Trace-Id` HTTP header for AWS X-Ray tracing.	`Root=1-63441c4a-abcdef012345678912345678`; `Self=1-63441c4a-12456789abcdef012345678;Root=1-67891233-abcdef012345678912345678`
`aws.x_amzn_request_id`	string	experimental Contains the value of the AWS 'X-Amzn-RequestId' HTTP header.	`123344566`
`aws.lambda.invoked_arn`	string	experimental The full invoked ARN as provided on the `Context` passed to the function (`Lambda-Runtime-Invoked-Function-Arn` response header from the request to `/runtime/invocation/next`).	`arn:aws:lambda:us-east-1:123456789012:function:acceptanceWeatherBackend:production`

Azure

Fields that can come from applications running on Azure.

Fields

Resource attributes

Attribute	Type	Description	Examples
`azure.subscription`	string	experimental An Azure subscription is a logical container used to provision resources in Azure.	`27e9b03f-04d2-2b69-b327-32f433f7ed21`
`azure.resource.group`	string	experimental A resource group is a container that holds related resources for an Azure solution.	`demo-backend-rg`
`azure.resource.type`	string	experimental The name of a resource type in the format: {resource-provider}/{resource-type}.	`Microsoft.ContainerService/managedClusters`
`azure.resource.id`	string	experimental A unique, immutable, identifier assigned to each Azure cloud resource.	`/subscriptions/27e9b03f-04d2-2b69-b327-32f433f7ed21/resourceGroups/demo-backend-rg/providers/Microsoft.ContainerService/managedClusters/demo-aks`
`azure.resource.name`	string	experimental User provided name of Azure cloud resource.	`demo-aks`
`azure.location`	string	experimental A specific geographical location of Azure Cloud resource.	`East US`
`azure.management_group`	string	experimental A group of Azure subscriptions used for governance use cases.	`Tenant Root Group`; `My Custom Group`
`azure.event_hub_namespace.name`	string	experimental Azure Event Hub Namespace name.	`my-event-hub`
`azure.service_bus_namespace.name`	string	experimental Azure Service Bus name.	`my-service-bus`
`azure.sql_server.name`	string	experimental Azure SQL Server name.	`contoso-sql-server`
`azure.sql_elastic_pool.name`	string	experimental Azure SQL Server Elastic Pool name.	`contoso-elastic-pool`
`azure.vm.name`	string	experimental Azure Virtual Machine name.	`my-virtual-machine`
`azure.vm_scale_set.name`	string	experimental Azure Virtual Machine Scale Set name.	`my-vmss`
`azure.vmid`	string	experimental Azure Virtual Machine unique 128bits identifier	`090556DA-D4FA-764F-A9F1-63614EDA019A`
`azure.site_name`	string	experimental Globally unique deployment information about an Azure function.	`dt-function-scripted`
`azure.class_name`	string	experimental The full qualified name of the class executing an Azure function.	`Host.Functions`

BOSH

Fields that are integral to applications managed by BOSH.

Fields

Resource attributes

Attribute	Type	Description	Examples
`bosh.name`	string	experimental A unique identifier to a deployment or instance.	`isolated_diego_cell_devima`
`bosh.instance_id`	string	experimental A unique identifier assigned to each deployed instance.	`af318409-9e9d-4a18-aca4-0fb52bbdc526`
`bosh.availability_zone`	string	experimental A specific geographical BOSH location.	`us-east-1a`

Browser

The browser namespace contains information on the browser running an application.

Fields

Attribute	Type	Description	Examples
`browser.user_agent`	string	stable Full user agent string as provided by the browser.	`Mozilla/5.0 (Windows NT 10.0; Win64; x64)`
`browser.name`	string	stable Browser name	`Mozilla`
`browser.version`	string	stable Browser version	`5.0`
`browser.type`	string	stable Type of browser	`desktop`; `mobile`; `tablet`; `robot`; `other`

Captured Attributes

Span scoped attributes (e.g. method parameters, return values, class names, …) captured by the OneAgent based on a request attribute rule. The actual name of the attribute is the prefix "captured_attribute" plus the "request attribute name" defined in the request attributes configuration. In contrast to request attributes, captured attributes contain the raw values reported by the OneAgent at the location (i.e. on the active span) where they appeared. No aggregation (first/last value, distinct values, ...), type conversion or normalization is performed on them. They are the basis for request attributes.

Fields

Attribute	Type	Description	Examples
`captured_attribute.__attribute_name__`	array	experimental Contains the span scoped raw values that were captured under the name `__attribute_name__` defined by the request attribute configuration. The values are always mapped as array according to the type of the captured attributes, so either boolean, double, long or string. If the captured attributes have mixed types (e.g. long and string, or double and long, etc.), all attributes are converted to string and stored as string array.	`[42]`; `['Platinum']`; `[32, 16, 8]`; `['Special Offer', '1702']`; `['18.35', '16']`

Cassandra

Fields

Attribute	Type	Description	Examples
`cassandra.cluster.name`	string	experimental None

Client

The client namespace contains information on the initiator of a network connection.

Fields

Attribute	Type	Description	Examples
`client.ip`	ipAddress	experimental IP address of the client (IPv4 or IPv6) making the request.	`194.232.104.141`; `2a01:468:1000:9::140`
`client.port`	long	experimental Client port number.	`65123`; `80`
`client.isp`	string	experimental The name of the Internet Service Provider (ISP) associated with the IP address of the client.	`Internet Service Provider Name`

Cloud

Fields related to cloud deployments that can be used across different providers.

Fields

Attribute	Type	Description	Examples
`cloud.availability_zone`	string	stable Identifier referring to the availability zone within a cloud vendor's region.	`us-east-1a`
`cloud.region`	string	stable Identifier referring to a geographic region of a cloud vendor's datacenter.	`us-east-1`
`cloud.resource_id`	string	stable Cloud provider-specific native identifier of the monitored cloud resource (e.g. an ARN on AWS, a fully qualified resource ID on Azure, a full resource name on GCP).	`arn:aws:lambda:REGION:ACCOUNT_ID:function:my-function`; `//run.googleapis.com/projects/PROJECT_ID/locations/LOCATION_ID/services/SERVICE_ID`; `/subscriptions/<SUBSCIPTION_GUID>/resourceGroups/<RG>/providers/Microsoft.Web/sites/<FUNCAPP>/functions/<FUNC>`
`cloud.provider`	string	experimental Name of the cloud provider.	`alibaba_cloud`
`cloud.account.id`	string	stable The cloud account ID the resource is assigned to.	`111111111111`; `opentelemetry`
`cloud.platform`	string	stable The cloud platform in use. ¹	`alibaba_cloud_ecs`
¹ The prefix of the service matches the one specified in `cloud.provider`.

cloud.provider has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`alibaba_cloud`	Alibaba Cloud
`aws`	Amazon Web Services
`azure`	Microsoft Azure
`gcp`	Google Cloud
`heroku`	Heroku Platform as a Service
`ibm_cloud`	IBM Cloud
`tencent_cloud`	Tencent Cloud

cloud.platform MUST be one of the following:

Value	Description
`alibaba_cloud_ecs`	Alibaba Cloud Elastic Compute Service
`alibaba_cloud_fc`	Alibaba Cloud Function Compute
`alibaba_cloud_openshift`	Red Hat OpenShift on Alibaba Cloud
`aws_app_runner`	AWS App Runner
`aws_ec2`	AWS Elastic Compute Cloud
`aws_ecs`	AWS Elastic Container Service
`aws_eks`	AWS Elastic Kubernetes Service
`aws_elastic_beanstalk`	AWS Elastic Beanstalk
`aws_lambda`	AWS Lambda
`aws_openshift`	Red Hat OpenShift on AWS (ROSA)
`azure_aks`	Azure Kubernetes Service
`azure_app_service`	Azure App Service
`azure_container_instances`	Azure Container Instances
`azure_functions`	Azure Functions
`azure_openshift`	Azure Red Hat OpenShift
`azure_vm`	Azure Virtual Machines
`gcp_app_engine`	Google Cloud App Engine (GAE)
`gcp_cloud_functions`	Google Cloud Functions (GCF)
`gcp_cloud_run`	Google Cloud Run
`gcp_compute_engine`	Google Cloud Compute Engine (GCE)
`gcp_kubernetes_engine`	Google Cloud Kubernetes Engine (GKE)
`gcp_openshift`	Red Hat OpenShift on Google Cloud
`ibm_cloud_openshift`	Red Hat OpenShift on IBM Cloud
`tencent_cloud_cvm`	Tencent Cloud Cloud Virtual Machine (CVM)
`tencent_cloud_eks`	Tencent Cloud Elastic Kubernetes Service (EKS)
`tencent_cloud_scf`	Tencent Cloud Serverless Cloud Function (SCF)

Cloudfoundry

Fields

Attribute	Type	Description
`cloudfoundry.application.id`	string	experimental None
`cloudfoundry.application.name`	string	experimental None
`cloudfoundry.instance.index`	string	experimental None
`cloudfoundry.space.id`	string	experimental None
`cloudfoundry.space.name`	string	experimental None

Code

Fields

Attribute	Type	Description	Examples
`code.function`	string	experimental The method or function name, or equivalent (usually rightmost part of the code unit's name). Represents the name of the function, that is represented by this span.	`serveRequest`
`code.namespace`	string	experimental The "namespace" within which `code.function` is defined. Usually the qualified class or module name, such that `code.namespace` + some separator + `code.function` form a unique identifier for the code unit.	`com.example.MyHttpService`
`code.filepath`	string	experimental The source code file name that identifies the code unit as uniquely as possible.	`/usr/local/MyApplication/content_root/app/index.php`
`code.invoked.function`	string	experimental Like `code.function`, only it represents the function that was active when a span has been started. Typically it is the function that has been instrumented. The spans duration does not reflect the duration of this function execution. Should only be set if it differs from `code.function`.	`invoke`
`code.invoked.namespace`	string	experimental Like `code.namespace`, only it represents the namespace of the function that was active when a span has been started. Typically it is the function that has been instrumented. Should only be set if it differs from `code.namespace`.	`com.sun.xml.ws.server.InvokerTube$2`
`code.invoked.filepath`	string	experimental Like `code.filepath`, only it represents the file path of the function that was active when a span has been started. Typically it is the function that has been instrumented. Should only be set if it differs from `code.filepath`.	`/usr/local/MyApplication/content_root/app/index.php`
`code.call_stack`	string	experimental The call stack of the `code.function`. The call stack starts with the `code.function` and the stack frames are separated by a line feed.	`com.example.SampleClass.doProcessing(SampleClass.java) com.example.SampleClass.doSomeWork(SampleClass.java) com.example.SampleClass.main(SampleClass.java)`

Coldfusion

Fields

Attribute	Type	Description	Examples
`coldfusion.jvm.config.file`	string	experimental None
`coldfusion.service.name`	string	experimental None

Compilation Timings

For some technologies compilation of code might be a significant contributor to request execution time. Compilation timings provide insight into this, where available.

Fields

Attribute	Type	Description	Examples
`compilation_timings.duration_sum`	duration	experimental The total duration in nanoseconds spent compiling.	`6723`
`compilation_timings.compilation_count`	long	experimental The number of compilations contributing to `compilation_timings.duration_sum`.	`7`
`compilation_timings.top_compilations`	record	experimental The top N compilations contributing to `compilation_timings.duration_sum`, represented as map from compilation unit name to duration in nanoseconds spent.	`{'/home/user/test/php/build/tmp/php-htdocs/memcached/memcachedCli.php': 1952, '/home/user/test/php/build/tmp/php-htdocs/curl_cli_uri_filtering.php': 1306}`

Container

Fields

Attribute	Type	Description	Examples
`container.id`	string	experimental Container ID. Usually a UUID, as for example used to identify Docker containers. The UUID might be abbreviated.	`a3bf90e006b2`
`container.image.name`	string	experimental Name of the image the container was built on.	`gcr.io/opentelemetry/operator`
`container.image.version`	string	experimental None	`0.1`
`container.name`	string	experimental Container name used by container runtime.	`opentelemetry-autoconf`

CICS Transaction Gateway

CTG (shorthand for "CICS Transaction Gateway") is a connector for enterprise modernization of CICS assets. It empowers various application platforms, such as Java servlets, to incorporate CICS programs.

CICS (shorthand for "Customer Information Control System") is a middleware to support rapid, high-volume online transaction processing on IBM mainframe systems on z/OS. CTG features a client and a server, which communicate via so-called GatewayRequests.

Fields

Attribute	Type	Description	Examples
`ctg.request.gateway_url`	string	experimental URL of the gateway. Only set on client-side spans.	`tcp://1.2.3.4:5678/`
`ctg.request.type`	string	experimental Type of the CTG GatewayRequest.	`BASE`
`ctg.request.call_type`	long	experimental Integer representing the call type of the CTG GatewayRequest. The set of possible values varies per request type. ¹	`2`
`ctg.request.flow_type`	long	experimental Integer representing the flow type of the CTG GatewayRequest. ²	`5`
`ctg.request.server_id`	string	experimental ID of the server. Not set for all request types.	`IPICTEST`
`ctg.request.commarea_length`	long	experimental Length of the COMMAREA. Only set when request type is ECI.	`0`
`ctg.request.term_id`	string	experimental Name of the terminal resource. Only set when request type is EPI.	`CN02`
`ctg.request.object_name`	string	experimental Name of the request object. Only set when request type is ADMIN.	``
`ctg.request.extend_mode`	long	experimental Integer representing the extend mode of the CTG GatewayRequest. Only set when request type is ECI. ³	`11`
`ctg.response.code`	long	experimental CTG response code. The set of possible values varies per request type. ⁴	`-23`
¹ https://www.ibm.com/docs/api/v1/content/SSZHFX_9.3.0/basejavadoc/constant-values.html ² The values are defined in the IBM CTG API source code. ³ https://www.ibm.com/docs/api/v1/content/SSZHFX_9.3.0/basejavadoc/constant-values.html ⁴ https://www.ibm.com/docs/api/v1/content/SSZHFX_9.3.0/basejavadoc/constant-values.html

ctg.request.type MUST be one of the following:

Value	Description
`ADMIN`	Admin request.
`AUTH`	Authentication request.
`BASE`	Base. A base GatewayRequest without a further subtype. ¹
`ECI`	External Call Interface. Enables a client application to call a CICS program synchronously or asynchronously. ²
`EPI`	External Presentation Interface. Enables a user application to install a virtual IBM 3270 terminal into a CICS server. ³
`ESI`	External Security Interface. Enables user applications to perform security-related tasks. ⁴
`XA`	CICS Request Exit. Can be used for request retry, dynamic server selection and for rejecting non-valid requests. ⁵
¹ https://www.ibm.com/support/knowledgecenter/en/SSZHFX_8.1.0/basejavadoc/com/ibm/ctg/client/GatewayRequest.html ² https://www.ibm.com/support/knowledgecenter/en/SSZHJ2_9.1.0/progguide/topics/xeci.html ³ https://www.ibm.com/support/knowledgecenter/en/SSZHFX_8.1.0/progde/xepi.html ⁴ https://www.ibm.com/support/knowledgecenter/en/SSZHJ2_9.1.0/progguide/topics/xesi.html ⁵ https://www.ibm.com/support/knowledgecenter/en/SSZHJ2_9.2.0/progguide/topics/cicsreqexit.html

Custom Services

Fields

Attribute	Type	Description	Examples
`custom_service.name`	string	experimental The name of a custom service. This field is only present if a custom service was directly created via Dynatrace OneAgent SDK.	`MyCustomService`; `AuthenticationComponent`
`custom_service.method`	string	experimental The service method of a custom service. This field is only present if a custom service was directly created via Dynatrace OneAgent SDK.	`startTask`; `run`; `authenticate`

Database

Fields

Attribute	Type	Description	Examples
`db.system`	string	experimental An identifier for the database management system (DBMS) product being used. See below for a list of well-known identifiers.	`mongodb`; `mysql`
`db.mssql.instance_name`	string	experimental The Microsoft SQL Server instance name connecting to.	`MSSQLSERVER`
`db.name`	string	experimental The name of the database being accessed.	`myDB`; `customers`
`db.statement`	string	experimental The database statement being executed. ¹	`SELECT * FROM wuser_table`; `SET mykey "WuValue"`
`db.affected_item_count`	long	experimental The number of items (rows, documents,…) affected.	`32`
`db.bind.parameters`	record[]	experimental Bind parameters represented as a key and value map. For database systems which do not have named keys the map key is the string representation of the index starting with 0. Several database requests may get aggregated into a single span. Each entry in the array holds the bind parameters for one database request.	`[{'name': 'paul', 'age': '23'}, {'name': 'mary', 'age': '32'}]`; `[{'0': 'paul', '1': '23'}, {'0': 'mary', '1': '32'}]`
`db.mongodb.collection`	string	experimental The collection being accessed within the database stated in `db.name`.	`customers`; `products`
`db.operation`	string	experimental The name of the db operation executed, e.g. the MongoDB command name, SQL keyword, Redis command name,… Not set if there are multiple operations (e.g. batch, concat) done via a single statement. ²	`drop`; `findAndModify`; `SELECT`; `PREPARE`; `GetItem`; `set`; `LPUSH`; `mutateIn`; `ReadItems`; `PURG`
`db.sql.table`	string	experimental The name of the primary table that the operation is acting upon, including the database name (if applicable).	`public.users`; `customers`
`db.result.execution_count`	long	experimental The number of operations executed on the result (e.g. fetches from SQL result set, MongoDB cursor operations).	`12`
`db.result.exception_count`	long	experimental The number of exceptions encountered while fetching the result.	`2`
`db.result.duration_sum`	duration	experimental The total duration in nanoseconds used for fetching the result.	`234`
`db.result.duration_min`	duration	experimental The minimum duration in nanoseconds used for fetching the result.	`123`
`db.result.duration_max`	duration	experimental The maximum duration in nanoseconds used for fetching the result.	`345`
`db.result.roundtrip_count`	long	experimental The number of round-trips triggered by fetching the result.	`2`
`db.dynamodb.region`	string	experimental The region of the dynamodb (see also `cloud.region`).	`us-east-1`
`db.dynamodb.table_names`	string[]	experimental The list of tables the request targets.	`[Cats, Dogs]`
`db.cassandra.table`	string	experimental The name of the primary table that the operation is acting upon, including the keyspace name (if applicable).	`mytable`; `customers`
`db.cosmosdb.container`	string	experimental The container being accessed within the database stated in `db.name`.	`users`; `customers`
`db.cosmosdb.request_charge`	double	experimental The cost of the request in Azure Cosmos DB request units (RU).	`4.95`; `2.0`
¹ The value may be sanitized to exclude sensitive information. ² Depending on the data provided on ingest this attribute may be derived by e.g. parse of `db.statement`. Parsing might fail or result might be inaccurate.

db.system has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`adabas`	Adabas (Adaptable Database System)
`cache`	InterSystems Caché
`cassandra`	Apache Cassandra
`clickhouse`	ClickHouse
`cloudscape`	Cloudscape
`cockroachdb`	CockroachDB
`coldfusion`	ColdFusion IMQ
`cosmosdb`	Microsoft Azure Cosmos DB
`couchbase`	Couchbase
`couchdb`	CouchDB
`db2`	IBM Db2
`derby`	Apache Derby
`dl/i`	IBM DL/I
`dynamodb`	Amazon DynamoDB
`edb`	EnterpriseDB
`elasticsearch`	Elasticsearch
`filemaker`	FileMaker
`firebird`	Firebird
`firstsql`	FirstSQL
`geode`	Apache Geode
`h2`	H2
`hanadb`	SAP HANA
`hbase`	Apache HBase
`hive`	Apache Hive
`hsqldb`	HyperSQL DataBase
`informix`	Informix
`ingres`	Ingres
`instantdb`	InstantDB
`interbase`	InterBase
`mariadb`	MariaDB
`maxdb`	SAP MaxDB
`memcached`	Memcached
`mongodb`	MongoDB
`mssql`	Microsoft SQL Server
`mssqlcompact`	Microsoft SQL Server Compact
`mysql`	MySQL
`neo4j`	Neo4j
`netezza`	Netezza
`opensearch`	OpenSearch
`oracle`	Oracle Database
`other_sql`	Some other SQL database. Fallback only. See notes.
`pervasive`	Pervasive PSQL
`pointbase`	PointBase
`postgresql`	PostgreSQL
`progress`	Progress Database
`redis`	Redis
`redshift`	Amazon Redshift
`spanner`	Cloud Spanner
`sqlite`	SQLite
`sybase`	Sybase
`teradata`	Teradata
`vertica`	Vertica

Deployment Attributes

Fields

Attribute	Type	Description	Examples
`deployment.release_product`	string	experimental The name of the deployed product.	`WoGo Main`
`deployment.release_stage`	string	experimental The stage the product is deployed to.	`production`
`deployment.release_version`	string	experimental The version of the deployed product.	`0.4.1`
`deployment.release_build_version`	string	experimental The build version of the deployed product.	`2021-03-24`

Device

The device namespace contains information on the device running an application. This should only be used for end-user devices or devices outside of a private infrastructure. In line with the naming conventions and guidelines, we are in this case adhering to the emerging Open Telemetry convention around this, with some additions.

Fields

Attribute	Type	Description	Examples
`device.manufacturer`	string	experimental The manufacturer of the device.	`Apple`
`device.model.identifier`	string	experimental The model identifier of the device.	`iPhone3,4`
`device.is_rooted`	boolean	experimental Indicates if a rooted device was detected.
`device.screen.width`	long	experimental Screen size width.	`2048`
`device.screen.height`	long	experimental Screen size height.	`1152`
`device.battery.level`	long	experimental The battery level of the device.	`100`
`device.orientation`	string	experimental The orientation of the device.	`landscape`

DISK

Disk attributes.

FIELDS

Resource attributes

Attribute	Type	Description	Examples
`disk.device_name`	string	experimental Disk device name (Linux, AIX)	`sda`
`disk.mountpoint`	string	experimental Primary mountpoint	`/mnt/storage`
`disk.all_mountpoints`	string[]	experimental List of all mountpoints	`[/mnt/storage, /home, /var/log]`

DL/I Database Attachment

Fields

Attribute	Type	Description	Examples
`db.dli.pcb`	string	experimental The name of the program communication block associated with this DL/I method.	`3`; `MYPCBNAM`
`db.dli.segment_name`	string	experimental The name of the last segment that was matched or returned.	`PARTROOT`
`db.dli.segment_level`	string	experimental The hierarchical level of the segment that was matched or returned.	`3`; `24`
`db.dli.processing_options`	string	experimental The PCB processing options.	`GR`
`db.dli.terminal_name`	string	experimental The DL/I database or logical terminal name associated with this DL/I method.	`HWSAM5ZD`; `10505`
`db.dli.status_code`	string	experimental The DL/I status code.	`QC`
`db.dli.pcb_type`	string	experimental The PCB type.	`DC`; `DL/I`; `F/P`

db.dli.pcb_type MUST be one of the following:

Value	Description
`DC`	Data communications.
`DL/I`	DL/I db.
`F/P`	Fast Path.

Dotnet

Fields

Attribute	Type	Description	Examples
`dotnet.dll.file`	string	experimental Filename of main dotnet assembly.
`dotnet.dll.path`	string	experimental Filepath of main dotnet assembly.

Dynatrace ActiveGate

Metadata with ActiveGate realated information.

Fields

Attribute	Type	Description	Examples
`dt.active_gate.id`	string	experimental Hexadecimal identifier of the ActiveGate prefixed with `0x`	`0xef3d21c3`
`dt.active_gate.group.name`	string	experimental The name of group ActiveGate instance belongs to	`GdanskLab`
`dt.active_gate.working_mode`	string	experimental Working mode of the ActiveGate	`cluster`

dt.active_gate.working_mode MUST be one of the following:

Value	Description
`cluster`	Cluster ActiveGate
`embedded`	Embedded ActiveGate
`environment`	Environment ActiveGate
`multitenant`	Multitenant ActiveGate

API connector fields

Attribute	Type	Description	Examples
`dt.active_gate.api_connector.config_id`	string	experimental Config long id of the endpoint configuration as a string.	`123`; `9276`
`dt.active_gate.api_connector.pipeline_identifier`	string	experimental String identifier of an api connector pipeline	`Kubernetes/Topology`
`dt.active_gate.api_connector.pipeline_status`	string	experimental Status of an api connector pipeline run	`failed`
`dt.active_gate.api_connector.technology_id`	string	experimental String identifier of an api connector technology	`Kubernetes`; `CloudFoundry`; `AWS`; `Dynatrace Extension`; `Azure`

dt.active_gate.api_connector.pipeline_status MUST be one of the following:

Value	Description
`failed`	Pipeline execution failed
`skipped`	Pipeline execution skipped
`succeeded`	Pipeline execution succeeded

Dynatrace OneAgent Metadata

Metadata of the OneAgent module that reported a signal. These attributes are what one would also see in OneAgent Health.

Fields

Attribute	Type	Description	Examples
`dt.agent.module.type`	string	experimental OneAgent module type	`apache`
`dt.agent.module.version`	string	experimental OneAgent full module version	`1.269.17.20221117-132428`
`dt.agent.module.version_short`	string	experimental OneAgent short module version, to be expected only on record types where `dt.agent.module.version`'s cardinality would be a problem	`1.269`
`dt.agent.module.id`	uid	experimental OneAgent module ID.	`031f613871fab0b4`; `fc3cd1bb276f0bed`
`dt.agent.module.parent_id`	uid	experimental OneAgent parent module ID, in case this is a so-called sub-agent	`ea89eef5db8b85a9`

dt.agent.module.type has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`apache`	apache
`dotnet`	dotnet
`dumpproc`	dumpproc
`extensions`	extensions
`go`	go
`iis`	iis
`java`	java
`log_analytics`	log_analytics
`net`	net
`nettracer`	nettracer
`nginx`	nginx
`nodejs`	nodejs
`opentracingnative`	opentracingnative
`os`	os
`php`	php
`plugin`	plugin
`process`	process
`python`	python
`remote_plugin`	remote_plugin
`ruby`	ruby
`sdk`	sdk
`support`	support
`updater`	updater
`varnish`	varnish
`wsmb`	wsmb
`z`	z_

Davis AI metadata

Some attributes are used in the Davis AI context.

Fields

Configuration fields

These fields can be set in events to influence the Davis AI behavior.

Attribute	Type	Description	Examples
`dt.davis.timeout`	long	stable The event timeout period (in minutes). Various event sources use this event property to keep an event active by regularly refreshing an initial event. The timeout defines how fast the event source must refresh an event to keep it active. To keep the event active, the event source must send the refresh within the timeout period. If no refresh is sent, the event is automatically closed by Dynatrace after the timeout period. Note that metric sources use their own configurable de-alerting windows to close events. Setting the timeout shorter than the de-alerting window will force events to close and increase the risk of false-positive alerts.
`dt.davis.is_frequent_issue_detection_allowed`	boolean	stable The flag controls whether the Davis AI should consider suppressing frequent events (true) or bypassing frequent issues check (false).
`dt.davis.analysis_time_budget`	long	stable The time budget (in seconds) that the Davis AI is granted before it must raise a problem. The analysis time budget can be set per event and controls the balance of sending out alerts early and granting the AI analysis enough time to finish its analysis. The trade-off of a short analysis budget is that the root cause and event merge analysis is limited or even skipped. For example, the time budget of 0 seconds means that the event raises a problem and sends the alert immediately, without any analysis.
`dt.davis.analysis_trigger_delay`	long	stable The time delay (in seconds) before the trigger of Davis AI analysis. For example, the delay of 0 seconds triggers a Davis® problem and the root cause analysis immediately. The trigger delay can be used to hold the analysis until all the relevant root cause data has arrived to Dynatrace. For example, it might be beneficial for cloud integrations or log integrations that report data in different schedules - you can delay the analysis until data from all sources is available. Note that while longer delays means more data is available for root cause analysis, it also delays alerts delivery.
`dt.davis.is_merging_allowed`	boolean	stable This flag controls whether the Davis AI is allowed to merge this event into a larger problem (true) or if a new problem must be created (false).
`dt.davis.is_rootcause_relevant`	boolean	stable This flag controls whether the Davis AI should include this event within the root cause analysis (true) or if it is not (false) relevant.
`dt.davis.is_problem_suppressed`	boolean	stable This flag controls whether the Davis AI suppresses the problem from showing up in the UI and sending notifications.
`dt.davis.is_entity_remapping_allowed`	boolean	stable This flag defines whether the remapping of the target entity is enabled (true) or disabled (false). If the remapping is enabled, Dynatrace can map the event to an entity extracted from the event metadata. If the remapping is disabled or the extraction is not possible, Dynatrace maps the event to the entity specified in the event configuration (for example, a specific host) or to the global environment entity.
`dt.davis.preferred_entity_type`	string	stable The preferred entity type for remapping. You can find possible values in Dynatrace UI under Settings > Topology model > Generic types. If the remapping (dt.event.allow_entity_remapping) is enabled, this property defines the entity type to which the event should be mapped. If no entity of the preferred type is extracted, no remapping is applied.	`my.custom.entity.type`

System fields

These fields can be set by Davis AI routines.

Attribute	Type	Description
`dt.davis.forecast.upper`	long	stable The upper bound of the prediction interval of a given metric forecast.
`dt.davis.forecast.point`	long	stable The point value of a metric forecast.
`dt.davis.forecast.lower`	long	stable The lower bound of the prediction interval of a given metric forecast.
`dt.davis.anomaly_detection.upper`	long	stable The upper value range limit where any value above this point is considered abnormal.
`dt.davis.anomaly_detection.lower`	long	stable The lower value range limit where any value below this point is considered abnormal.
`dt.davis.anomaly_detection.anomaly`	long	stable Boolean timeseries of 0 and 1 showing whether a single timespan is outside the normal value range and therefore considered as abnormal.
`dt.davis.anomaly_detection.alert`	long	stable Boolean time series of 0 and 1 showing whether a single timespan was alerted due to continuous violations.

Dynatrace Entity IDs

The Dynatrace OneAgent associates monitoring data with a so called Monitored Entity ID (ME ID). On OneAgent monitored environments, whenever ME IDs are accessible within the monitored system they should be used to enrich monitoring data to facilitate correlations with data primarily addressed through ME IDs coming from other channels.

The structure for keys that signify entity IDs is dt.entity.{type of entity}. The value associated with such a key must be valid Dynatrace entity identifier (see Topology and Smartscape API).

To allow linking Entity IDs across various different monitoring artifacts (logs, metrics, etc.), all string representations of Entity IDs are required to follow a canonical form, which for all current entities is defined as PREFIX-0123456789ABCDEF.

Consumers should treat the token as an opaque value and must not infer any semantics on the ID itself. Producers need to match the Entity ID that is being returned by Dynatrace Entity API verbatim.

Producers of string representation must treat the string as if it was parsed case-sensitively, even though some parts of the product may be more lenient. The structure of the entity ID is currently as follows: <ID-NAMESPACE>-<16-digit-hex-string>. The <ID-NAMESPACE> is type specific but cannot be used to determine the actual entity type reliably, especially in cases of CUSTOM_DEVICE. The <16-digit-hex-string> needs to be zero-padded (prefix) to a length of 16 digits and must use upper case letters A-F.

Current entity IDs in cannonical form can be represented structurally with the following regular expression: [A-Z][A-Z_]*-[0-9A-F]{16}.

Additional characters or changes in the format may happen in the future but will not invalidate existing IDs or ID generation rules.

Fields

Attribute	Type	Description	Examples
`dt.entity.host`	string	experimental An entity ID of an entity of type HOST.	`HOST-E0D8F94D9065F24F`
`dt.entity.host_group`	string	experimental An entity ID of an entity of type HOST_GROUP.	`HOST_GROUP-E7FBBCF7B1467174`
`dt.entity.process_group`	string	experimental An entity ID of an entity of type PROCESS_GROUP.	`PROCESS_GROUP-E0D8F94D9065F24F`
`dt.entity.process_group_instance`	string	experimental An entity ID of an entity of type PROCESS_GROUP_INSTANCE.	`PROCESS_GROUP_INSTANCE-E0D8F94D9065F24F`
`dt.entity.custom_device`	string	experimental An entity ID of an entity of type CUSTOM_DEVICE.	`CUSTOM_DEVICE-E0D8F94D9065F24F`
`dt.entity.cloud_application_instance`	string	experimental An entity ID of an entity of type CLOUD_APPLICATION_INSTANCE.	`CLOUD_APPLICATION_INSTANCE-E0D8F94D9065F24F`
`dt.entity.cloud_application`	string	experimental An entity ID of an entity of type CLOUD_APPLICATION.	`CLOUD_APPLICATION-3AB5BBF3E09A7942`
`dt.entity.cloud_application_namespace`	string	experimental An entity ID of an entity of type CLOUD_APPLICATION_NAMESPACE.	`CLOUD_APPLICATION_NAMESPACE-C61324AA70F57BCB`
`dt.entity.kubernetes_node`	string	experimental An entity ID of an entity of type KUBERNETES_NODE.	`KUBERNETES_NODE-874C66B68CE15070`
`dt.entity.kubernetes_cluster`	string	experimental An entity ID of an entity of type KUBERNETES_CLUSTER.	`KUBERNETES_CLUSTER-E0D8F94D9065F24F`
`dt.entity.kubernetes_service`	string	experimental An entity ID of an entity of type KUBERNETES_SERVICE.	`KUBERNETES_SERVICE-FE6E75BB9DF02347`
`dt.entity.apm_tenant`	string	experimental The ME ID of a Dynatrace tenant	`APM_TENANT-00000000092D72A1`; `APM_TENANT-000000000934FC65`
`dt.entity.apm_cluster`	string	experimental The ME ID of a Dynatrace cluster	`APM_CLUSTER-B4133FCE691DF7AF`
`dt.entity.apm_server`	string	experimental The ME ID of one Dynatrace server in a cluster	`APM_SERVER-0000000000000004`; `APM_SERVER-0000000000000006`
`dt.entity.container_group`	string	experimental An entity ID of an entity of type CONTAINER_GROUP.	`CONTAINER_GROUP-7C2B1C24FFB288CB`
`dt.entity.container_group_instance`	string	experimental An entity ID of an entity of type CONTAINER_GROUP_INSTANCE.	`CONTAINER_GROUP_INSTANCE-F4A1347110826781`
`dt.entity.synthetic_location`	string	experimental An entity ID of an entity of type SYNTHETIC_LOCATION.	`SYNTHETIC_LOCATION-D140F3B85BCCBD1A`
`dt.entity.service`	string	experimental An entity ID of an entity of type SERVICE.	`SERVICE-57EC3CFC1FE72449`
`dt.entity.service_method`	string	experimental An entity ID of an entity of type SERVICE_METHOD.	`SERVICE_METHOD-659B35CA9AAC96C1`
`dt.entity.service_method_group`	string	experimental An entity ID of an entity of type SERVICE_METHOD_GROUP.	`SERVICE_METHOD_GROUP-02000E1DB1CDAF9F`
`dt.entity.application`	string	experimental The ME ID of a web application.	`APPLICATION-DC92E74A7A844E6E`
`dt.entity.mobile_application`	string	experimental The ME ID of a mobile application.	`MOBILE_APPLICATION-E8A8751A60D5BCE8`
`dt.entity.custom_application`	string	experimental The ME ID of a custom application.	`CUSTOM_APPLICATION-343A92501A51F286`
`dt.entity.disk`	string	experimental An entity ID of an entity of type DISK	`DISK-5472CBC1ED0981D6`
`dt.entity.network_interface`	string	experimental An entity ID of an entity of type NETWORK_INTERFACE	`NETWORK_INTERFACE-FC7B4A5937FC125C`
`dt.entity.ec2_instance`	string	experimental An entity ID of an entity of type EC2_INSTANCE	`EC2_INSTANCE-0004DD30F142D18C`
`dt.entity.aws_availability_zone`	string	experimental An entity ID of an entity of type AWS_AVAILABILITY_ZONE	`AWS_AVAILABILITY_ZONE-6000A4E2BD2AB971`
`dt.entity.gcp_zone`	string	experimental An entity ID of an entity of type GCP_ZONE	`GCP_ZONE-3699CB75E19C8505`
`dt.entity.azure_vm`	string	experimental An entity ID of an entity of type AZURE_VM	`AZURE_VM-326478B733D6CFB0`
`dt.entity.azure_region`	string	experimental An entity ID of an entity of type AZURE_REGION	`AZURE_REGION-0DD5C79E4034F0AA`

Dynatrace Extensions

Additional extension information sent via self-monitoring.

Fields

Attribute	Type	Description	Examples
`dt.extension.ds`	string	experimental Name of the data source.	`SNMPTrap`
`dt.extension.name`	string	experimental Name of the extension.	`com.snmptrap.generic`
`dt.extension.config.id`	string	experimental Extension's monitoring configuration identifier.	`vu9U3hXa3q0AAAABAAtleHQ6ZXh0LTA0MAAIYWdfZ3JvdXAAA0FHMQAkMjY2YTIyM2YtZDgxYi0zNTNjLThlYzctYzk2YzliZjg4OGQ3vu9U3hXa3q0`
`dt.extension.status`	string	experimental The status of the component reporting SFM event	`AUTHENTICATION_ERROR`

dt.extension.status has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`AUTHENTICATION_ERROR`	Unable to connect to EEC
`DEVICE_CONNECTION_ERROR`	Failed to establish connection with the device
`EEC_CONNECTION_ERROR`	Unable to connect to EEC
`GENERIC_ERROR`	Generic status used to communicate job failed
`INVALID_ARGS_ERROR`	Invalid arguments
`INVALID_CONFIG_ERROR`	Config provided by EEC is invalid
`OK`	Extension works fine
`UNKNOWN_ERROR`	Uninitialized/unknown error

Process Grouping Fields

Attributes used for Process Group enrichment in extensions.

Dynatrace ingest fields

Attributes defined in this namespace are used by Dynatrace to describe different aspects of the ingested data.

Fields

Attribute	Type	Description	Examples
`dt.ingest.format`	string	experimental The format of the data ingested in Dynatrace via the various ingest channels. E.g., Generic log ingest, OTLP logs ingest	`dtapi/json`; `otlp/protobuf`
`dt.ingest.warnings`	string[]	experimental An array of strings that represent markers on not-expected situations that might affect correctness or completness of incomming data point. It may be for instance limits applied or processing rule failing. It should not be detailed log with what happened, just high-level class of issue that occured.	`[attr_count_trimmed, content_trimmed]`

dt.ingest.format MUST be one of the following:

Value	Description
`dtapi/json`	JSON data ingested via the Dynatrace APIs
`dtapi/plaintext`	Plain text data ingested via the Dynatrace APIs
`otlp/json`	OpenTelemetry Protocol (OTLP) JSON data ingested via the Dynatrace APIs
`otlp/protobuf`	OpenTelemetry Protocol (OTLP) Protobuf data ingested via the Dynatrace APIs

dt.ingest.warnings MUST contain only values from the following list:

Value	Description
`content_trimmed`	The content was trimmed, right after receiving it by Cluster/ActiveGate, because it exceeded the event content max byte size limit.
`content_trimmed_pipe`	The content was trimmed in post-processing (after applying processing rules) because it exceeded the event content max byte size limit
`attr_count_trimmed`	The number of attributes was trimmed, right after receiving it by Cluster/ActiveGate, because it exceeded the max number of attributes limit.
`attr_count_trimmed_pipe`	The number of attributes was trimmed in post-processing (after applying processing rules) because it exceeded the max number of attributes limit.
`attr_val_count_trimmed`	At least one multi-value attribute had values number trimmed, right after receiving it by Cluster/ActiveGate, because it exceeded the max number of attributes limit.
`attr_val_count_trimmed_pipe`	After applying processing rules, at least one multi-value attribute had its values number trimmed (after using processing rules) because it exceeded the maximum number of attributes limit.
`attr_val_size_trimmed`	At least one attribute had its value size trimmed, right after receiving it by Cluster/ActiveGate, because it exceeded the max value size in bytes limit.
`attr_val_size_trimmed_pipe`	At least one attribute had its value size trimmed (after applying processing rules) because it exceeded the max value size in bytes limit.
`timestamp_corrected`	Timestamp was too far in the future and was corrected to current time.
`common_attr_corrected`	STATUS, LOG_LEVEL or EVENT_TYPE attribute was corrected.
`processing_batch_timeout`	Batch timeout occurred during processing pipeline.
`processing_transformer_timeout`	Execution timeout in one of processing transformers occurred during processing pipeline.
`processing_transformer_error`	Execution error in one of processing transformers occurred during processing pipeline.
`processing_transformer_throttled`	Execution throttled in one of processing transformers during processing pipeline.
`processing_output_record_conversion_error`	Output conversion error occurred for some record during processing pipeline.
`processing_prepare_input_error`	Prepare input error occurred in one of enabled processing pipeline rules.

Dynatrace

Fields

Attribute	Type	Description	Examples
`dt.host_group.id`	string	experimental see https://docs.dynatrace.com/docs/shortlink/host-groups. Note that host groups are identified by their name. This is not the entity ID of Host Group Entity, for which see dt.entity.host_group Tags: `permission`	`myHostGroup`
`dt.pg_detection.cluster.id`	string	experimental `DT_CLUSTER_ID` environment variable; also see https://docs.dynatrace.com/docs/shortlink/process-groups
`dt.pg_detection.custom_entry`	string	experimental also see https://docs.dynatrace.com/docs/shortlink/process-group-properties#variables
`dt.pg_detection.declarative.id`	string	experimental None
`dt.pg_detection.environment.id`	string	experimental `DT_ENVIRONMENT_ID` environment variable
`dt.pg_detection.node.id`	string	experimental `DT_NODE_ID` environment variable; also see https://docs.dynatrace.com/docs/shortlink/process-groups
`dt.pg_detection.workload.result`	string	experimental None
`dt.security_context`	string	experimental The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model here: https://docs.dynatrace.com/docs/shortlink/dynatrace-grail Tags: `permission`
`dt.source_entity`	string	experimental The ID of the entity considered the source of the measurement. The string needs to be in the format of any MONITORED_ENTITY type. ¹	`HOST-E0D8F94D9065F24F`; `PROCESS_GROUP_INSTANCE-E0D8F94D9065F24F`
`dt.source_entity.type`	string	stable The entity type of the entity whose identifier is held in dt.source_entity. The value must be a valid entity type and consistent with dt.source_entity. Note, though, that the type identifiers are expected to be lower cased in alignment with suffixes of dt.entity.* keys.	`host`; `process_group_instance`; `cloud:azure:resource_group`
`dt.cost.costcenter`	string	stable Can be used to assign usage to a Cost Center.	`Team A`
`dt.cost.product`	string	stable Can be used to assign usage to a Product or Application ID.	`Product A`
`dt.metrics.source`	string	experimental The source from which metrics are ingested. ²	`telegraf`; `com.dynatrace.extension.sql-oracle`
¹ Value of this attribute will be based on one of dt.entity.`<type>` attributes value. That means that both attributes dt.source_entity and corresponding dt.entity.`<type>` will be set to the same ID. ² This is the framework used for capturing, processing and forwarding metrics, not the emitting monitored entity. Exemplary custom value: name of an extension sending metrics.

dt.metrics.source has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`dynatrace_codemodule`	dynatrace_codemodule
`dynatrace_ingest`	dynatrace_ingest
`dynatrace_osagent`	OsAgent
`micrometer`	Micrometer
`oneagent_metric_api`	OneAgentMetricAPI
`opentelemetry`	OpenTelemetry
`statsd`	StatsD
`telegraf`	Telegraf

Dynatrace RUM

The dt.rum namespace contains Dynatrace RUM specific fields.

Fields

Attribute	Type	Description	Examples
`dt.rum.schema_version`	string	stable The Dynatrace RUM enrichment version.	`0.1`
`dt.rum.application.id`	string	stable The Dynatrace RUM application ID (UUID for Mobile, MEid for Web)	`ea7c4b59f27d43eb`
`dt.rum.session.id`	string	stable The user session id.	`HOPCPWKILUKHFHWRRQGBHHPAFLUJUOSH-0`; `23626166142035610_1-0`
`dt.rum.instance.id`	string	stable The RUM application instance id. (Formerly known as visitor id, the internal user id, the rxVisitor cookie value.)	`3735928559`

Settings

Fields for referencing Settings 2.0 objects, schemas and scopes.

Considerations on which fields to use

Although the dt.settings.object_id is enough to identify a specific settings value within a dynatrace environment, adding explicit information about the schema, scope and/or scope type can be useful nonetheless. If your use-case will only ever involve a single schema, scope type and/or scope, documenting this is good enough - if multiple schemas, scope types and/or scopes can be involved, filling the corresponding fields is strongly recommended.

Top level fields

The top level fields contain generally relevant information for all monitoring data.

Attribute	Type	Description	Examples
`dt.settings.object_id`	string	experimental The object ID of a settings value. This corresponds to the 'objectId' field/parameter in the Settings API.	`vu9U3hXa3q0AAAABACFidWlsdGluOnJ1bS51c2VyLWV4cGVyaWVuY2Utc2NvcmUABnRlbmFudAAGdGVuYW50ACRhMzZmYmYwMy00NDY1LTNlNTYtOTZiOS1kOWMzOGQ3MzU1NmO-71TeFdrerQ`
`dt.settings.object_summary`	string	experimental The human-readable summary or name of a single value of a multivalue settings schema. This corresponds to the 'summary' field in the Settings API.	`Journey Service all errors`; `Really, this can be anything`; `My alerting rule`
`dt.settings.schema_id`	string	experimental The schema ID of a settings schema, as used in the Settings APIs.	`builtin:problem.notifications`; `app:dynatrace.jenkins:connection`
`dt.settings.schema_version`	string	experimental The version of the schema referenced by dt.settings.schema_id, as declared by the schema itself. Typically a semantic version number.	`1.0.0`; `1.2.3`
`dt.settings.scope_type`	string	experimental The type of the scope that a settings object is persisted on.	`environment`; `host_group`; `host`
`dt.settings.scope_id`	string	experimental The ID of the scope that a settings object is persisted on. This corresponds to the 'scope' field/parameter in the Settings API.	`environment`; `HOST-EFAB6D2FE7274823`
`dt.settings.scope_name`	string	experimental The human-readable name of the scope that a settings object is persisted on.	`deb-10-k3s-oi-01.lab.dynatrace.org`

Dynatrace system fields

The namespace dt.system is reserved for Grail. These fields cannot be ingested but instead will be set by Grail directly. Every record that is fetched from Grail provides these fields, but by default they are hidden. You can display them by using the fieldsAdd command.

Example query:

// display the bucket for each log record
fetch logs
| fieldsAdd dt.system.bucket

Fields

Attribute	Type	Description	Examples
`dt.system.bucket`	string	stable The Grail bucket that the record is stored in.	`default_logs`; `default_spans`; `default_bizevents`
`dt.system.monitoring_source`	string	stable Identifies the license under which the source is running.	`fullstack_host`; `infrastructure`
`dt.system.storage_interval`	string	stable Identifies the timeframe represented by individual data structures stored under a metric key.	`1 min`
`dt.system.table`	string	stable The table that the record belongs to.	`logs`; `bizevents`

dt.system.monitoring_source MUST be one of the following:

Value	Description
`discovery`	The source is running under the discovery license.
`fullstack_container`	The source is running under the full-stack container license.
`fullstack_host`	The source is running under the full-stack host license.
`infrastructure`	The source is running under the infrastructure license.
`mainframe`	The source is running under the mainframe license.

dt.system.storage_interval MUST be one of the following:

Value	Description
`1 min`	The timeframe represented by individual measurements of a metrics record in storage.

Dynatrace specific tracing fields

Fields defined in this namespace are used by Dynatrace to describe different aspects of the context propagation between spans.

Fields

Attribute	Type	Description	Examples
`dt.tracing.custom_link.id`	uid	experimental The custom link id to identify spans calling each other. The id is derived from the custom link bytes.	`736bd2684696c4a8`
`dt.tracing.custom_link.type`	string	experimental The type of the custom link defines if a mapping of the `dt.tracing.custom_link.original_bytes` to the `dt.tracing.custom_link.transformed_bytes` was applied.	`generic`
`dt.tracing.custom_link.original_bytes`	binary	experimental The original binary data of the custom link.	`ycXlxUBAQEDee9lm8pBcA8nF5cVAQEBA3nvZZvKQXAPee9lm8s4SAQ==`
`dt.tracing.custom_link.transformed_bytes`	binary	experimental The transformed binary data of the custom link, only available if a mapping was applied.	`ycXlxUBAQEDee9lm8pBcA8nF5cVAQEBA3nvZZvKQXAPee9lm8s4SAQ==`
`dt.tracing.link.id`	uid	experimental Unique identifier for a dynatrace link.
`dt.tracing.link.is_sync`	boolean	experimental `true` indicates that caller waits on the response. Only available on span links with `dt.tracing.link.direction` set to `outgoing`.
`dt.tracing.foreign_link.text`	string	experimental An incoming foreign link (could be cross-environment, or cross-product).	`FW4;129;12;-2023406815;4539717;0;17;66;c511;2h02;3h12345678;4h676767`; `FW1;129;4711;59959450;-1859959450;3;17;0`
`dt.tracing.foreign_link.bytes`	binary	experimental An incoming foreign link (could be cross-environment, or cross-product).	`00000004000000010000000200000003000000040000002300000001`
`dt.tracing.response.headers`	record[]	experimental A collection of key-value pairs containing received response headers related to tracing from an outgoing call. Used for cross-environment linking.	`[{'traceresponse': '00-7b9e3e4068167838398f50017bfad358-d4ffc7e33530967a-01'}, {'x-dt-tracestate': '9651e1a8-19506b7c@dt'}]`
`dt.tracing.link.direction`	string	experimental The direction of the span link to define the correct order between spans.	`outgoing`

dt.tracing.custom_link.type MUST be one of the following:

Value	Description
`generic`	The `dt.tracing.custom_link.original_bytes` have no special meaning.
`ibm_mq`	The `dt.tracing.custom_link.original_bytes` are an IBM MQ custom link.
`ibm_mq_ignore_qname`	The `dt.tracing.custom_link.original_bytes` are an IBM MQ custom link, but the qname part should be ignored in mapping.

dt.tracing.link.direction MUST be one of the following:

Value	Description
`incoming`	Indicates that the link represents an incoming call (the child in a parent-child relationship).
`outgoing`	Indicates that the link represents an outgoing call (the parent in a parent-child relationship).

Elasticsearch

Fields

Attribute	Type	Description	Examples
`elasticsearch.cluster.name`	string	experimental None
`elasticsearch.node.name`	string	experimental None

Endpoint

Endpoints define the public interface of services.

Fields

Attribute	Type	Description	Examples
`endpoint.name`	string	stable The endpoint name is derived from endpoint detection rules and uniquely identifies one endpoint of a particular service. Endpoint names are usually technology specific and should be defined by attributes with low cardinality like http.route or rpc.method. Endpoints are exclusively detected on request root spans.	`/`; `/get-cart`; `/productpage`; `Reviews.GetReviews`

Entity fields

Fields that describe entities.

Attribute	Type	Description	Examples
`entity.conditional_name`	string	stable The entity name as defined by conditional naming rules. This name will be calculated based on a rules on the cluster side.	`Cl-Prod1 Ser-1`
`entity.customized_name`	string	stable The entity name as defined in the entity settings screen. This name is statically defined by the user for a particular entity.	`Host 1234`
`entity.detected_name`	string	stable The entity name as detected by Dynatrace or defined by the data source of the entity. Depending on the entity type this can involve different heuristics.	`ip-10-100-200-5.eu-west-1.compute.internal`
`entity.name`	string	stable All entities have an entity.name field. The following fields will be considered in order to determine the value: `entity.customized_name`, `entity.conditional_name`, `entity.detected_name`.	`easyTravel`
`entity.type`	string	stable The entity type	`host`; `service`

Equinox

Fields

Attribute	Type	Description	Examples
`equinox.config.path`	string	experimental None

ESB

Fields

Attribute	Type	Description	Examples
`esb.workflow.name`	string	experimental The name of the workflow, aka. the message flow for the IBM ESB.	`myMessageFlow`; `YourBusinessWorkflow`; `any_flow`
`esb.application.name`	string	experimental The name of the application that holds the workflows of the business logic.	`myBusinessApp`; `YourServiceApp`; `any_work`
`esb.library.name`	string	experimental The name of the library that hosts commonly used workflows to be re-used in applications.	`myWebServicesLib`; `YourMessagingLibrary`; `any_tools`
`esb.vendor`	string	experimental The vendor of the ESB technology used.	`ibm`; `tibco`

Event

The event namespace contains common identification, categorization and context on events in Dynatrace.

Fields

Attribute	Type	Description	Examples
`event.id`	string	stable Unique identifier string of an event, is stable across multiple refreshes and updates.	`5547782627070661074_1647601320000`
`event.parent_id`	string	experimental Unique identifier string of a parent event to link parent and child events.	`5547782627070661074_1647601319999`
`event.kind`	string	stable Gives high-level information about what kind of information the event contains, without being specific to the contents of the event. Helps to determine the record type of a raw event. Tags: `permission`	`INFRASTRUCTURE_EVENT`; `DAVIS_EVENT`; `BIZ_EVENT`; `RUM_EVENT`; `AUDIT_EVENT`; `BILLING_USAGE_EVENT`
`event.category`	string	stable Standard categorization based on the significance of an event (similar to the severity level in the previous Dynatrace).	`Availability`
`event.type`	string	stable The unique type identifier of a given event. Tags: `permission`	`ESXI_HOST_MEMORY_SATURATION`; `PROCESS_RESTART`; `CPU_SATURATION`; `MEMORY_SATURATION`; `Automation Workflow`; `AppEngine Functions - Small`
`event.provider`	string	stable Source of the event, for example the name of the component or system that generated the event. Tags: `permission`	`OneAgent`; `K8S`; `Davis`; `VMWare`; `GCP`; `AWS`; `LIMA_USAGE_STREAM`
`event.name`	string	stable The human readable display name of an event type.	`Process crashed`; `CPU Saturation`
`event.description`	string	stable The human readable description text of an event.	`The current response time (11 s) exceeds the auto-detected baseline (767 ms) by 1,336 %`
`event.start`	string	stable The event start timestamp in UTC (given in Grail preferred Linux timestamp nano precision format).	`16481073970000`
`event.end`	string	stable The event end timestamp in UTC (given in Grail preferred Linux timestamp nano precision format).	`16481073970000`
`event.status`	string	stable Status of an event as being either Active or Closed.	`Active`
`event.status_transition`	string	experimental An enum that shows the transition of the above event state.	`Recovered`
`event.group_label`	string	experimental Group label of an event.	`Availability`
`event.outcome`	string	stable Denotes whether the event represents a success or a failure from the perspective of the entity that produced the event (e.g. an HTTP response code).	`200`; `success`; `failure`
`event.version`	string	stable Describes the version of the event.	`1.0.0`

Values

Values are either in title-case or screaming snake case.

event.category SHOULD be one of the following:

Value	Description
`Availability`	availability
`Error`	error
`Slowdown`	slowdown
`Resource contention`	resource_contention
`Warning`	warning
`Info`	info
`Vulnerability management`	vulnerability_management

event.status SHOULD be one of the following:

Value	Description
`Active`	active
`Closed`	closed

event.status_transition SHOULD be one of the following:

Value	Description
`Created`	created
`Updated`	updated
`Refreshed`	refreshed
`Resolved`	resolved
`Recovered`	recovered
`Closed`	closed
`Timed out`	timed out
`Reopened`	reopened

Exception

Fields

Attribute	Type	Description	Examples
`exception.type`	string	experimental The type of the exception (its fully-qualified class name, if applicable).	`java.net.ConnectException`; `OSError`
`exception.message`	string	experimental The exception message.	`Division by zero`
`exception.file_name`	string	experimental The name of the file where the exception happened.	`https://www.foo.bar/path/main.js`
`exception.line_number`	long	experimental The line number where the exception happened.	`1401`
`exception.column_number`	long	experimental The column number where the exception happened.	`12304`
`exception.stack_trace`	string	experimental The stack trace of the exception. The format depends on the technology and source. While OneAgent formats stack traces to unify them across technologies, are stack traces from an OpenTelemetry source in the format they were sent to Dynatrace.	`@https://www.foo.bar/path/main.js:59:26 e@https://www.foo.bar/path/lib/1.1/lib.js:2:30315`
`exception.escaped`	boolean	experimental `true` indicates that the exception was recorded at a point where it is known that the exception escaped the scope of the span.
`exception.id`	uid	experimental The identifier of an exception, it should be unique within a list of exceptions. The identifier is used to reference the exception.
`exception.caused_by_id`	uid	experimental The `exception.id` of the exception the current exception was caused by.
`exception.is_caused_by_root`	boolean	experimental Is set to `true` if the exception is first exception of a caused by chain.

Function as a Service (FaaS)

Fields that can be expected from serverless functions or Function as a Service (FaaS) on various cloud platforms.

Fields

Resource attributes

Attribute	Type	Description	Examples
`faas.name`	string	experimental The name of the single function that this runtime instance executes. ¹	`my-function`; `myazurefunctionapp/some-function-name`; `test_function`
`faas.version`	string	experimental The immutable version of the function being executed. ²	`14`; `254`
`faas.max_memory`	long	experimental The amount of memory available to the serverless function in Bytes.
¹ This is the name of the function as configured/deployed on the FaaS platform and is usually different from the name of the callback function (which may be stored in the `code.namespace`/`code.function` span attributes). ² Value of the field depends on a cloud provider. This field is not set for Azure.

Span attributes

Attribute	Type	Description	Examples
`faas.invoked_provider`	string	experimental The cloud provider of the invoked function. Will be equal to the `cloud.provider` resource attribute of the invoked function.	`alibaba_cloud`
`faas.invoked_name`	string	experimental The name of the invoked function.	`my-function`
`faas.invoked_region`	string	experimental The cloud region of the invoked function. ¹	`eu-central-1`
`faas.coldstart`	boolean	experimental A boolean that is true if the serverless function is executed for the first time (aka cold-start).
`faas.trigger`	string	experimental Type of the trigger which caused this function invocation.	`datasource`
¹ Will be equal to the `cloud.region` resource attribute of the invoked function.

faas.invoked_provider has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`alibaba_cloud`	Alibaba Cloud
`aws`	Amazon Web Services
`azure`	Microsoft Azure
`gcp`	Google Cloud
`tencent_cloud`	Tencent Cloud

faas.trigger MUST be one of the following:

Value	Description
`datasource`	A response to some data source operation such as a database or filesystem read/write.
`http`	To provide an answer to an inbound HTTP request
`other`	If none of the others apply
`pubsub`	A function is set to be executed when messages are sent to a messaging system.
`timer`	A function is scheduled to be executed regularly.

Feature Flag

Attribute	Type	Description	Examples
`feature_flag.key`	string	experimental The unique identifier of the feature flag.	`logo-color`
`feature_flag.provider_name`	string	experimental The name of the service provider that performs the flag evaluation.	`Flag Manager`
`feature_flag.variant`	string	experimental SHOULD be a semantic identifier for a value. If one is unavailable, a stringified version of the value can be used. ¹	`red`; `true`; `on`
¹ A semantic identifier, commonly referred to as a variant, provides a means for referring to a value without including the value itself. This can provide additional context for understanding the meaning behind a value. For example, the variant `red` maybe be used for the value `#c05543`.

A stringified version of the value can be used in situations where a semantic identifier is unavailable. String representation of the value should be determined by the implementer.

Google Cloud

Fields

Attribute	Type	Description	Examples
`gcp.app_engine.instance`	string	experimental None
`gcp.app_engine.service`	string	experimental None
`gcp.cloud_run.service`	string	experimental None
`gcp.instance.id`	string	experimental A permanent identifier that is unique within your Google Cloud project.	`6639848141313102286`
`gcp.region`	string	experimental A region is a specific geographical location where you can host your resources.	`europe-west3`
`gcp.zone`	string	experimental A zone is a subset of a region. Each region has three or more zones.	`europe-west3-c`
`gcp.location`	string	experimental Region or zone the instance of the GCP resource is running on.	`europe-west3-c`
`gcp.project.id`	string	experimental The identifier of the GCP project associated with this resource.	`dynatrace-gcp-extension`
`gcp.instance.name`	string	experimental The name to display for the instance in the Cloud Console.	`single-vm-test`
`gcp.resource.type`	string	experimental The name of a resource type.	`cloudsql_database`
`gcp.resource.name`	string	experimental The globally unique resource name in Google Cloud convention	`//cloudfunctions.googleapis.com/projects/gcp-example-project/locations/us-central1/functions/examplefunction`

Geolocation

The geo namespace contains geo location information. This section only holds all currently agreed upon fields in the Dynatrace Semantic Dictionary. Aligned closely to the ECS, with some adaptions around field groupings

Fields

Attribute	Type	Description	Examples
`geo.continent.name`	string	stable English name of the continent.	`North America`
`geo.country.name`	string	stable English name of the country.	`Canada`
`geo.region.name`	string	stable English name of the region.	`Quebec`
`geo.city.name`	string	stable English name of the city.	`Montreal`

Glassfish

Fields

Attribute	Type	Description	Examples
`glassfish.domain.name`	string	experimental The name of the domain this instance belongs to.
`glassfish.instance.name`	string	experimental The instance's name.

Go

Fields

Attribute	Type	Description	Examples
`go.linkage`	string	experimental None

Host

Fields describing a host.

Host naming

Dynatrace aims to use the best fitting name for the field host.name. See below, how Dynatrace determines the host name in an ordered by precedence fashion:

1. Customized the host name

Dynatrace supports customizing the host.name property. A custom set host name takes precedence over the auto detection mechanisms described further down.

Place a configuration file containing the desired name in a specific directory as described in this Documentation
Alternatively, the oneagentctl tool can be used to set a custom host name. See Documentation for details.

2a. Linux & AIX

The result of the system call to the standard C library's gethostname() if it can be interpreted as a fully qualified domain name (FQDN) and doesn't contain "localhost".
Otherwise, a system call to getaddrinfo() for port 80 is issued, again sanity checking whether the returned name is an FQDN and doesn't contain "localhost".

2b. Windows

On Windows, the system call GetComputerNameExA is used to determine a host's name. In particular, the resulting name is composed of <hostname>.<domainname> with the following details
- hostname = ComputerNameDnsHostname retrieved by GetComputerNameEx
- domainname = ComputerNameDnsDomain retrieved by GetComputerNameEx
Defaults to the string EmptyHostName if neither property can be resolved.

Fields

Attribute	Type	Description	Examples
`host.name`	string	experimental The host name as determined on the data source (e.g. OneAgent, extensions, OpenTelemetry, …). Important: This is not the name of the host entity, which can be modified based on naming rules. Tags: `permission`	`ip-10-178-54-32.ec2.internal`

HTTP

Attribute	Type	Description	Examples
`http.request.method`	string	experimental HTTP request method.	`GET`; `POST`; `HEAD`
`http.response.status_code`	long	experimental HTTP response status code.	`200`
`http.response.reason_phrase`	string	experimental The HTTP reason phrase (HTTP1 only).	`Not found`
`http.request.body.size`	long	experimental The size of the request payload body in bytes. This is the number of bytes transferred excluding headers and is often, but not always, present as the Content-Length header. For requests using transport encoding, this should be the compressed size.	`3495`
`http.response.body.size`	long	experimental The size of the response payload body in bytes. This is the number of bytes transferred excluding headers and is often, but not always, present as the Content-Length header. For requests using transport encoding, this should be the compressed size.	`3495`
`http.request.header.__key__`	string	experimental HTTP request headers, `__key__` being the lowercase HTTP header name, e.g. "http.request.header.accept-encoding". The value is a string. If there are multiple headers with the same name or multiple header values, the values will be comma separated into a single string.	`https://www.foo.bar/`; `gzip, deflate, br`; `1.2.3.4, 1.2.3.5`
`http.response.header.__key__`	string	experimental HTTP response headers, `__key__` being the lowercase HTTP header name, e.g. "http.response.header.content-type". The value is a string. If there are multiple headers with the same name or multiple header values, the values will be comma separated into a single string.	`909`; `text/html; charset=utf-8`; `abc, def`
`http.route`	string	experimental The matched route (path template in the format used by the respective server framework).	`/users/:userID?`; `{controller}/{action}/{id?}`

Attribute	Type	Description	Examples
`http.server_name`	string	experimental The server name as configured by the webserver if available. If no such name exists the local hostname and bound port. In Kubernetes the base pod name is used.	`MyServer`; `localhost:8000`

Hybris

Fields

Attribute	Type	Description	Examples
`hybris.bin.dir`	string	experimental None	`/opt/hybris-60/hybris/bin`
`hybris.config.dir`	string	experimental None	`/opt/hybris-60/hybris/config`
`hybris.data.dir`	string	experimental None	`/opt/hybris-60/hybris/data`

Reference

IBM

Fields

Attribute	Type	Description	Examples
`ibm.ace.integration_node.name`	string	experimental The name of the integration node (aka. broker) that manages one or more integration server.	`myIntegrationNode`; `YourBroker`; `the_management_instance`
`ibm.ace.integration_server.name`	string	experimental The name of the either broker-managed or standalone integration server (formerly known as execution group or dataflow engine).	`myIntegrationServer`; `YourExecutionGroup`; `dataflow_engine`
`ibm.cics.aor`	string	experimental None
`ibm.cics.region`	string	experimental None
`ibm.cics.program`	string	experimental The name of the CICS program.	`EDUCHAN`
`ibm.cics.tor`	string	experimental None
`ibm.ctg.name`	string	experimental None
`ibm.ims.connect`	string	experimental None
`ibm.ims.control`	string	experimental None
`ibm.ims.mpr`	string	experimental None
`ibm.ims.soap_gw.name`	string	experimental None

Iis

Fields

Attribute	Type	Description	Examples
`iis.app_pool.name`	string	experimental None
`iis.role.name`	string	experimental None

Java

Fields

Attribute	Type	Description
`java.jar.file`	string	experimental None
`java.jar.path`	string	experimental None
`java.main.class`	string	experimental None
`java.main.module`	string	experimental None

JBoss

Fields

Attribute	Type	Description	Examples
`jboss.home`	string	experimental The instance's home directory.
`jboss.mode`	string	experimental The instance's operating mode.	`org.jboss.as.standalone`; `org.jboss.as.server`
`jboss.server.name`	string	experimental The instance's server name.

Kubernetes

Fields

Attribute	Type	Description	Examples
`k8s.cluster.name`	string	stable (Optional) The name of the cluster in Dynatrace. Doesn't need to be unique, nor immutable. Tags: `permission`	`unguard-dev`; `k3s-oneagent`
`k8s.cluster.uid`	string	stable A pseudo-ID for the cluster, set to the UID of the kube-system namespace.	`1c7a24c7-ff51-46e0-bcc9-c52637ceec57`
`k8s.node.name`	string	stable The name of the Node.	`cluster-pool-1-c3c7423d-azth`
`k8s.container.name`	string	stable The name of the Container from Pod specification, must be unique within a Pod. Container runtime usually uses different globally unique name (`container.name`).	`redis`
`k8s.namespace.name`	string	stable The name of the namespace that the pod is running in. Tags: `permission`	`default`
`k8s.pod.name`	string	stable The name of the Pod.	`opentelemetry-pod-autoconf`
`k8s.pod.uid`	string	stable The UID of the Pod.	`275ecb36-5aa8-4c2a-9c47-d8bb681b9aff`
`k8s.workload.name`	string	stable The name of the Workload.	`checkoutservice`
`k8s.workload.kind`	string	stable The type of the Workload.	`deployment`; `statefulset`; `cronjob`; `job`; `daemonset`; `replicaset`
`k8s.service.name`	string	stable The name of the Kubernetes Service.	`my-service`

Standard fields used for log events

Fields relevant for log events

Fields

Attribute	Type	Description	Examples
`loglevel`	string	experimental The log event severity level.	`ERROR`; `INFO`; `TRACE`
`log.source`	string	experimental Human readable attribute which allows to identify log stream. ¹ Tags: `permission`	`/var/log/messages`; `Windows Event Log`; `Docker Container Output`; `stdout`
`log.iostream`	string	experimental The I/O stream to which the log was emitted.	`stdout`; `stderr`
¹ Can contain e.g. a file path, standard output, an URI etc., depending on log stream type. The value should be stable for one logical source, so e.g. not affected by log file rotation digits.

loglevel MUST be one of the following:

Value	Description
`ALERT`	alert
`CRITICAL`	critical
`DEBUG`	debug
`EMERGENCY`	emergency
`ERROR`	error
`FATAL`	fatal
`INFO`	info
`NONE`	none
`NOTICE`	notice
`SEVERE`	severe
`TRACE`	trace
`WARN`	warn

log.iostream MUST be one of the following:

Value	Description
`stderr`	std_err
`stdout`	std_out

Messaging

Fields

Attribute	Type	Description	Examples
`messaging.system`	string	experimental An identifier for the messaging system. See below for a list of well-known identifiers.	`kafka`; `rabbitmq`
`messaging.operation`	string	experimental A string identifying the kind of messaging operation. ¹	`peek`
`messaging.message.id`	string	experimental A value used by the messaging system as an identifier for the message, represented as a string.	`452a7c7c7c7048c2f887f61572b18fc2`
`messaging.message.conversation_id`	string	experimental The conversation ID identifying the conversation to which the message belongs, represented as a string. Sometimes called "Correlation ID".	`MyConversationId`
`messaging.message.payload_size_bytes`	long	experimental The (uncompressed) size of the message payload in bytes.	`2738`
`messaging.destination.name`	string	experimental The message destination name ²	`MyQueue`; `MyTopic`
`messaging.destination.manager_name`	string	experimental The destination's manager name ³	`MyBroker`
`messaging.destination.kind`	string	experimental The kind of message destination	`queue`; `topic`
`messaging.destination.temporary`	boolean	experimental A boolean that is true if the message destination is temporary and might not exist anymore after messages are processed.
`messaging.source.name`	string	experimental The message source name ⁴	`MyQueue`; `MyTopic`
`messaging.source.manager_name`	string	experimental The source's manager name ⁵	`MyBroker`
`messaging.source.kind`	string	experimental The kind of message source	`queue`; `topic`
`messaging.source.temporary`	boolean	experimental A boolean that is true if the message source is temporary and might not exist anymore after messages are processed.
¹ If a custom value is used for `messaging.operation`, it MUST be of low cardinality. ² Destination name SHOULD uniquely identify a specific queue, topic or other entity within the broker. ³ Manager name SHOULD uniquely identify the broker. ⁴ Source name SHOULD uniquely identify a specific queue, topic, or other entity within the broker. ⁵ Manager name SHOULD uniquely identify the broker.

messaging.system has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`activemq`	ActiveMQ
`artemis`	ActiveMQ Artemis
`aws_sns`	Amazon Simple Notification Service (SNS)
`aws_sqs`	Amazon Simple Queue Service (SQS)
`azure_eventgrid`	Azure Event Grid
`azure_eventhubs`	Azure Event Hubs
`azure_servicebus`	Azure Service Bus
`gcp_pubsub`	Google Cloud Pub/Sub
`hornetq`	HornetQ
`jms`	Java Message Service
`kafka`	Apache Kafka
`mqseries`	IBM MQ
`msmq`	MSMQ
`rabbitmq`	RabbitMQ
`rocketmq`	Apache RocketMQ
`sag_webmethods_is`	Software AG, webMethods Integration Server
`tibco_ems`	Tibco EMS
`weblogic`	Oracle WebLogic
`websphere`	IBM WebSphere Application Server

messaging.operation has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`peek`	A message is received from a destination by a message consumer/server, but left there.
`process`	A message that was previously received from a destination is processed by a message consumer/server.
`publish`	A message is sent to a destination by a message producer/client.
`receive`	A message is received from a destination by a message consumer/server.

messaging.destination.kind MUST be one of the following:

Value	Description
`queue`	A message sent to a queue
`topic`	A message sent to a topic

messaging.source.kind MUST be one of the following:

Value	Description
`queue`	A message received from a queue
`topic`	A message received from a topic

Akka Messaging

Attribute	Type	Description	Examples
`messaging.akka.actor.system`	string	experimental Name of the actor system.	`RequesterSystem`; `ResponseSystem`
`messaging.akka.actor.path`	string	experimental Path to actor inside actor system.	`/system/log1-Logging$DefaultLogger`; `/remote/akka.tcp/RequesterSystem@localhost:52133/user/requestActor/$a`
`messaging.akka.actor.kind`	string	experimental Name of the top level actor. See The Akka actor hierarchy	`system`; `user`
`messaging.akka.actor.type`	string	experimental Fully qualified type name of actor.	`com.acme.RespondingActor`
`messaging.akka.message.type`	string	experimental Fully qualified type name of the message.	`java.lang.String`; `akka.event.Logging$Info2`; `com.acme.twosuds.ResponseActor$RequestMessage`

Module Insights

In webserver technologies a multitude of modules might be contributing to handling a single web request. Module insights provides timings for these, where available.

Fields

Attribute	Type	Description	Examples
`module_insights.modules`	record	experimental Modules executed as part of this web request, represented as map from module name to duration in nanoseconds spent.	`{'HttpRedirectionModule': 10299, 'BasicAuthenticationModule': 4665}`

Network

These attributes may be used for any network related operation.

Fields

Attribute	Type	Description	Examples
`network.transport`	string	experimental OSI Transport Layer or Inter-process Communication method	`tcp`; `udp`
`network.type`	string	experimental OSI Network Layer or non-OSI equivalent.	`ipv4`; `ipv6`
`network.protocol.name`	string	experimental OSI Application Layer or non-OSI equivalent.	`amqp`; `http`; `mqtt`
`network.protocol.version`	string	experimental Version of the application layer protocol used.	`1.1`; `3.1.1`
`network.carrier.name`	string	experimental Name of the mobile carrier.	`Magenta`; `AT&T`
`network.connection.type`	string	experimental Internet connection type.	`cellular`; `wifi`
`network.connection.subtype`	string	experimental Details connection.type, like cellular or wifi technology.	`lte`; `802.11x`

network.transport has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`inproc`	In-process communication. ¹
`other`	Something else (non IP-based).
`pipe`	Named or anonymous pipe.
`tcp`	TCP
`udp`	UDP
`unix`	Unix domain socket.
¹ Signals that there is only in-process communication not using a "real" network protocol in cases where network attributes would normally be expected. Usually all other network attributes can be left out in that case.

network.type has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`ipv4`	IPv4
`ipv6`	IPv6

Network device

Fields that are used in extensions to describe network devices.

Fields

Attribute	Type	Description	Examples
`device`	string	deprecated Used in Extension Framework 2.0 Address (IP address with port) used by a monitored device to communicate with an extension.	`10.102.0.45:161`
`device.address`	ipAddress	deprecated Used in Extension Framework 2.0 IP address used by a monitored device to communicate with an extension.	`10.102.0.45`
`device.port`	string	deprecated Used in Extension Framework 2.0 Port used by a monitored device to communicate with an extension.	`161`
`device.name`	string	deprecated Used in Extension Framework 2.0 Name of a device monitored by an extension.	`AT1i-WLC-TestingLab.dynatrace.org`

Nodejs

Fields

Attribute	Type	Description
`nodejs.app.base.dir`	string	experimental None
`nodejs.app.name`	string	experimental None
`nodejs.script.name`	string	experimental None

Openstack

Fields that can come from applications running on Openstack.

Fields

Resource attributes

Attribute	Type	Description	Examples
`openstack.availability_zone`	string	experimental A specific availability zone in given openstack region.	`us-east-1a`
`openstack.instance_uuid`	string	experimental UUID of specific openstack instance.	`6790cb48-f8e9-4773-bcea-001469de0599`

Origin

The origin of a request associated with this event.

Attribute	Type	Description	Examples
`origin.type`	string	experimental Origin type of the request associated with this event.	`REST`; `LOCAL`
`origin.address`	string	experimental Source IP address of the request associated with this event if not of 'LOCAL' type.	`10.11.12.13`
`origin.x_forwarded_for`	string	experimental The verbatim value of the X-Forwarded-For HTTP request header (if present) of the request associated with the event.	`1.2.3.4`
`origin.session`	string	experimental The id of the browser session (if present) associated with the event.	`node0hfznc`

origin.type MUST be one of the following:

Value	Description
`LOCAL`	The event provider issued the request locally.
`REST`	The event provider received an external REST API call.

OS

The os namespace contains information on the operating system running an application.

Fields

Attribute	Type	Description	Examples
`os.name`	string	stable Human readable operating system name.	`iOS`
`os.version`	string	stable Version of the operating system.	`15.3.1`

Php

Fields

Attribute	Type	Description
`php.cli.script.path`	string	experimental None
`php.cli.working.dir`	string	experimental None
`php.drupal.application.name`	string	experimental None
`php.fpm.pool.name`	string	experimental None
`php.symfony.application.name`	string	experimental None
`php.wordpress.blog.name`	string	experimental also see https://developer.wordpress.org/reference/functions/get_bloginfo/

Process

Fields

Attribute	Type	Description	Examples
`process.executable.name`	string	experimental The name of the process executable. On Linux based systems, can be set to the `Name` in `proc/[pid]/status`. On Windows, can be set to the base name of `GetProcessImageFileNameW`.	`otelcol`
`process.executable.path`	string	experimental The full path to the process executable. On Linux based systems, can be set to the target of `proc/[pid]/exe`. On Windows, can be set to the result of `GetProcessImageFileNameW`.	`/usr/bin/cmd/otelcol`
`process.pid`	long	experimental Process Identifier (PID) as observed by the monitored process.	`1234`

Request

Fields

Attribute	Type	Description	Examples
`request.id`	uid	experimental Present on every span of a request. All spans within one request share the same identifier. The ID is a hex-encoded numerical value and not globally unique, but guaranteed to be unique within one particular trace.	`95efd70fcdb5b7b3`; `96835e1d65490b48`
`request.is_root_span`	boolean	experimental Marks the root of a request. This means the first span that is the start of the request within a service.
`request.is_failed`	boolean	experimental Indicates that the request is considered failed according to the failure detection rules. Only present on the request root span.

Request Attributes

Request scoped attributes (e.g. method parameters, return values, class names, …) captured by the OneAgent based on a request attribute definition. The actual name of the attribute is the prefix "request_attribute" plus the "request attribute name" defined in the request attributes configuration. Request attributes are built based on captured attributes and other attributes like HTTP header values or "normal" span attributes, on which the aggregations (first/last value, distinct values, ...), type conversion and normalizations defined in the request attribute configuration are performed. They are evaluated for an entire request (possibly consisting of multiple spans) and are stored only on the request root node.

Fields

Attribute	Type	Description	Examples
`request_attribute.__attribute_name__`	array	experimental Contains the request scoped reconciled values of the attribute named `__attribute_name__` defined by the request attribute configuration. The data type of the value depends on the request attribute definition.	`42`; `Platinum`; `['Product A', 'Product B']`; `['Special Offer', '1702']`

Remote Procedure Calls

Fields

Attribute	Type	Description	Examples
`rpc.system`	string	experimental A string identifying the remoting system or framework. See below for a list of well-known identifiers.	`apache_cxf`; `dotnet_wcf`; `grpc`; `jax_ws`
`rpc.service`	string	experimental The full (logical) name of the service being called, including its package name, if applicable. ¹	`myservice.EchoService`
`rpc.method`	string	experimental The name of the (logical) method being called ²	`exampleMethod`
`rpc.namespace`	string	experimental The namespace of the method being called. In SOAP, it would be the XML namespace.	`tempuri.org`
¹ This is the logical name of the service from the RPC interface perspective, which can be different from the name of any implementing class. The `code.namespace` attribute may be used to store the latter (despite the attribute name, it may include a class name; e.g., class with method actually executing the call on the server side, RPC client stub class on the client side). ² This is the logical name of the method from the RPC interface perspective, which can be different from the name of any implementing method/function. The `code.function` attribute may be used to store the latter (e.g., method actually executing the call on the server side, RPC client stub method on the client side).

rpc.system has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`apache_axis`	Apache Axis
`apache_cxf`	Apache CXF
`apache_wink`	Apache Wink
`dotnet_remoting`	.NET Remoting
`dotnet_wcf`	.NET WCF
`grpc`	gRPC
`java_rmi`	Java RMI
`jax_ws`	JAX-WS
`jboss`	JBoss
`jersey`	Jersey
`openedge`	Progress OpenEdge
`resteasy`	JBoss RESTEasy
`restlet`	Restlet
`spring_ws`	Spring Web Services
`tibco_ws`	Tibco Web Services
`weblogic_ws`	WebLogic Web Services
`webmethods`	Webmethods

Attribute	Type	Description	Examples
`rpc.grpc.status_code`	long	experimental The numeric status code of the gRPC request.

Server

The server namespace contains information on the responder of a network connection.

Fields

Attribute	Type	Description	Examples
`server.address`	string	experimental Logical server hostname, matches server FQDN if available, and IP or socket address if FQDN is not known.	`example.com`
`server.resolved_ips`	ipAddress[]	experimental A list of IP adresses that are the result of DNS resolution of `server.address`.	`[194.232.104.141, 2a01:468:1000:9::140]`
`server.port`	long	experimental Logical server port number.	`65123`; `80`

Service

Fields

Attribute	Type	Description	Examples
`service.name`	string	stable The logical name of the service.	`shoppingcart`

Servlet

Fields

Attribute	Type	Description	Examples
`servlet.context.name`	string	experimental also see https://docs.oracle.com/javaee/6/api/javax/servlet/ServletContext.html#getServletContextName
`servlet.context.path`	string	experimental also see https://docs.oracle.com/javaee/6/api/javax/servlet/ServletContext.html#getContextPath

SNMP

Fields that are used in SNMP extensions.

Fields

Attribute	Type	Description	Examples
`version`	string	deprecated Used in Extension Framework 2.0 The SNMP version.	`SNMPv3`
`trap_oid`	string	deprecated Used in Extension Framework 2.0 The trap OID of a given event.	`SNMPv2-MIB::coldStart`

Softwareag

Fields

Attribute	Type	Description	Examples
`softwareag.install.root`	string	experimental None
`softwareag.product.prop.name`	string	experimental None

Span

Fields

Attribute	Type	Description	Examples
`span.id`	uid	stable A unique identifier for a span within a trace. The `span.id` is a 8-byte id and hex-encoded if shown as a string.	`f76281848bd8288c`
`span.parent_id`	uid	stable The `span.id` of this span's parent span. The `span.parent_id` is a 8-byte id and hex-encoded if shown as a string.	`f76281848bd8288c`
`span.alternate_parent_id`	uid	experimental The alternative `span.id` of this span's parent span. In case a trace is monitored by more tracing systems (e.g. OneAgent + OpenTelemetry) there might be two potential parent spans. If these two spans differ, `span.parent_id` holds the `span.id` of the parent which is known to originate from same tenant and this attribute shows the other. The `span.alternate_parent_id` is a 8-byte id and hex-encoded if shown as a string.	`f76281848bd8288c`
`span.is_subroutine`	boolean	experimental `true` indicates that this span is a subroutine of its parent span. The spans represent functions running on the same thread on the same call stack.
`span.kind`	string	stable Distinguishes between spans generated in a particular context.	`server`
`span.events`	record[]	experimental A collection of events. An event is an optional time-stamped annotation of the span, consisting of a name and key-value pairs.
`span.links`	record[]	experimental A collection of links. A link is a reference from this span to a whole trace or a span in the same or different trace.
`span.is_exit_by_exception`	boolean	experimental Set to `true` if the span was exited by an exception. If set to `false` the span has exception events but the span was not exited by one of them.
`span.exit_by_exception_id`	uid	experimental The `exception.id` of the exception the its `span.events` with the current span exited. The referenced exception has set the attribute `exception.escaped` to true.
`span.timing.cpu`	duration	experimental The overall CPU time spent executing the span including the CPU times of child spans which are running on the same thread on the same call stack.
`span.timing.cpu_self`	duration	experimental The CPU time spent exclusively on executing this span not including the CPU times of any children.
`span.status_code`	string	experimental Defines the status of a span, predominantly used to indicate a processing error. This field is not present if the reported span status is `unset`.	`error`
`span.status_message`	string	experimental An optional text that can provide a descriptive error message in case the `span.status_code` is `error`.	`Connection closed before message completed`; `Error sending request for url`

span.kind MUST be one of the following:

Value	Description
`client`	Indicates that the span describes a request to some remote service.
`consumer`	Indicates that a span describes a child of an asynchronous `producer` request.
`internal`	Default Value. Indicates that the span represents an internal operation.
`link`	Indicates that the span describes a Dynatrace link node.
`producer`	Indicates that the span describes the initiator of an asynchronous request.
`server`	Indicates that the span covers server-side handling of a synchronous RPC or other remote request.

span.status_code MUST be one of the following:

Value	Description
`error`	An error happened while processing the span.
`ok`	The span was explicitly validated as having completed successfully, despite maybe even containing information about an error.

Span Event

Fields

Attribute	Type	Description	Examples
`span_event.name`	string	experimental Some span events have a defined semantics based on the name of the span event.	`exception`

span_event.name has the following list of well-known values. If one of them applies, then the respective value MUST be used, otherwise a custom value MAY be used.

Value	Description
`bizevent`	Indicates that the span event represents a business event
`exception`	Indicates that the span event represents an exception
`feature_flag`	Indicates that the span event represents a feature flag

Reference

Language Independent Interface Types For OpenTelemetry

Spring

Fields

Attribute	Type	Description
`spring.application.name`	string	experimental also see https://docs.spring.io/spring-boot/docs/current/reference/html/application-properties.html#application-properties.core.spring.application.name
`spring.profile.name`	string	experimental the active profile (last value of spring.profiles.active)
`spring.startup.class`	string	experimental None

Supportability

Additional information about the attributes of a data point.

Fields

Attribute	Type	Description	Examples
`supportability.non_persisted_attribute_keys`	string[]	experimental A string array of attributes keys which where not stored as they where not allow-listed or where removed during the pipeline steps.	`["my_span_attribute", "db.name"]`
`supportability.dropped_attributes_count`	long	experimental The number of attributes that were discarded on the source. Attributes can be discarded because their keys are too long or because there are too many attributes.	`1`
`supportability.dropped_events_count`	long	experimental The number of span events that were discarded on the source.	`1`
`supportability.dropped_links_count`	long	experimental The number of span links that were discarded on the source.	`1`
`supportability.endpoint_name_rule`	string	experimental Name of the pipeline rule that generated the unified service `endpoint.name`.	`http.route`; `rpc.method`
`supportability.flaws`	string[]	experimental A string array of one or multiple error codes indicating issues in the assembly of a trace in Dynatrace. Typically, issues come from erroneous (3rd party) instrumentations (e.g. not sending a required field), data loss due to network connectivity (e.g. missing parent span) or conditions implied by the nature of the trace (e.g. trace exceeding the depth limit). The attribute is only present in case an assembly issue was detected (the list will not be empty). For more information and details about specific error codes, please reach out to Dynatrace support.	`[C4, S3, A2]`
`supportability.custom_service.rule_id`	uid	experimental The id of a custom service configuration rule. This field is only present if a custom service was configured as automatic instrumentation rule in Dynatrace.	`4d76194c11a9426197a9062548f9e66e`
`supportability.atm_sampling_ratio`	long	experimental The denominator of the sampling ratio of the Dynatrace OneAgent, the attribute is only set if adaptive traffic management (ATM) is active on the Dynatrace OneAgent. A numerator is not specified as it is always 1. If for example the Dynatrace OneAgent samples with a probability of 1/16 (6,25%) the value of `supportability.atm_sampling_ratio` would be 16 and the numerator is 1.	`16`
`supportability.alr_sampling_ratio`	long	experimental The denominator of the sampling ratio of the Dynatrace cluster, the attribute is only set if adaptive load redution (ALR) is active on the Dynatrace cluster. A numerator is not specified as it is always 1. If for example the Dynatrace cluster samples with a probability of 1/8 (12,5%) the value of `supportability.alr_sampling_ratio` would be 8 and the numerator is 1.	`8`
`supportability.original_start_time`	timestamp	experimental The original start time of the span. Only available if the value of the `start_time` attribute was truncated. Truncating the start time is technically required for long running spans that have a start time older than three days in the past.	`1649822520123123123`

Telemetry

The telemetry.sdk.* fields are used to describe the telemetry SDK in OpenTelemetry or ODIN ingest. It can be considered the closest equivalent of ODIN/OTel data to dt.agent.module.*.

The telemetry.exporter.* fields are used to define the exporter that exports telemetry data and is expected to be different for each exporter in case when multiple exporters co-exist.

Fields

Attribute	Type	Description	Examples
`telemetry.exporter.name`	string	experimental The exporter name.	`odin`
`telemetry.exporter.version`	string	experimental The full agent/exporter version.	`1.285.1.20240101-256988`
`telemetry.exporter.package_version`	string	experimental The version as exposed to the package manager (e.g. npm).	`1.285.1`
`telemetry.sdk.name`	string	experimental The name of the telemetry SDK.	`odin`; `opentelemetry`
`telemetry.sdk.version`	string	experimental The version string of the telemetry SDK.	`1.20.0`
`telemetry.sdk.language`	string	experimental The programming language/tech of the telemetry SDK.	`nodejs`; `python`; `java`

Thread

Fields

Attribute	Type	Description	Examples
`thread.id`	long	experimental Current "managed" thread id (as opposed to OS thread id).	`42`
`thread.name`	string	experimental Current thread name.	`main`

TIBCO Business Works

Fields

Attribute	Type	Description
`tibco.businessworks_ce.app.name`	string	experimental None
`tibco.businessworks_ce.version`	string	experimental None
`tibco.businessworks.app.node.name`	string	experimental None
`tibco.businessworks.app.space.name`	string	experimental None
`tibco.businessworks.domain.name`	string	experimental None
`tibco.businessworks.home`	string	experimental None
`tibco.businessworks.property.file.path`	string	experimental None
`tibco.businessworks.property.file.name`	string	experimental None

Time correction

The time_correction namespace contains information on time corrections applied to the timestamps of an event like "timestamp", "event.start" or "event.end". Time corrections may be necessary if events are reported with timestamps that are completely off compared to cluster time, for example data reported by RUM agents can be off depending on client time.

Fields

Attribute	Type	Description	Examples
`time_correction.offset`	long	experimental The offset of the original timestamps to the corrected timestamps in nanoseconds (`<corrected timestamp>` = `<original timestamp>` + `<offset>`). May be a negative number. Example: original timestamp: 1670399998423233001, offset: 127927969312, corrected timestamp: 1670400126351202313	`127927969312`
`time_correction.is_applied`	boolean	experimental Gives hint if the time correction has already been applied to the timestamps of this event.

Trace

Fields

Attribute	Type	Description	Examples
`trace.id`	uid	stable A unique identifier for a trace. The `trace.id` is a 16-byte id and hex-encoded if shown as a string.	`357bf70f3c617cb34584b31bd4616af8`
`trace.state`	string	experimental The trace state in the w3c-trace-context format.	`f4fe05b2-bd92206c@dt=fw4;3;abf102d9;c4592;0;0;0;2ee;5607;2h01;3habf102d9;4h0c4592;5h01;6h5f9a543f1184a52b1b744e383038911c;7h6564df6f55bd6eae,apmvendor=boo,foo=bar`
`trace.alternate_id`	uid	experimental The preserved trace id when OneAgent and other tracing systems monitor the same process and the trace id from the other tracing system was replaced by the OneAgent trace id. The `trace.alternate_id` is a 16-byte id and hex-encoded if shown as a string.	`357bf70f3c617cb34584b31bd4616af8`

URL

The url namespace contains semantic conventions for URL and its components.

Fields

Attribute	Type	Description	Examples
`url.scheme`	string	experimental The URI scheme component identifying the used protocol.	`https`; `ftp`; `telnet`
`url.full`	string	experimental Absolute URL describing a network resource according to RFC3986.	`https://www.foo.bar/docs/search?q=OpenTelemetry#SemConv`
`url.path`	string	experimental The URI path component.	`/docs/search`
`url.truncated_path`	string	experimental Truncated URI path component for endpoint detection of certain technologies that do not provide a `http.route`. The truncation logic depends on the technology and is a best effort to provide a stable value. Example Adobe Experience Manager (AEM): First two parts of `url.path`. Truncated value of `/content/wknd/us/en/` is `/content/wknd`.	`/docs`
`url.query`	string	experimental The URI query component.	`q=OpenTelemetry`
`url.fragment`	string	experimental The URI fragment component.	`SemConv`

User

Representation of a physical or logical user.

Attribute	Type	Description	Examples
`user.id`	string	experimental Unique identifer of a user.	`35ba9499-f87c-4047-962c-14dc32e255e5`
`user.organization`	string	experimental Organization the user belongs to.	`DYNATRACE`; `CUSTOMER`; `PARTNER`
`user.name`	string	experimental Full name of the user.	`Wolfgang Amadeus Mozart`
`user.email`	string	experimental E-mail of the user.	`user@mail.com`

user.organization MUST be one of the following:

Value	Description
`CUSTOMER`	Customer organization
`DYNATRACE`	Dynatrace organization
`PARTNER`	Dynatrace partner organization

user.organization MUST be one of the following:

Value	Description
`DYNATRACE`	Dynatrace organization
`CUSTOMER`	Customer organization
`PARTNER`	Dynatrace partner organization

VMware

Fields that can come from applications running on VMware.

Fields

Resource attributes

Attribute	Type	Description	Examples
`vmware.hypervisor.name`	string	experimental ESXi Host.	`my-hypervisor.lab.dynatrace.org`
`vmware.vcenter.name`	string	experimental The name of the vCenter server with multi-hypervisor environment.	`my-vcenter.lab.dynatrace.org`
`vmware.nic.name`	string	experimental ESXi Host Network Interface.	`vmnic0`; `vmnic1`; `vmnic2`
`vmware.datacenter.name`	string	experimental The name of data center hypervisor is running in.	`srvwasapp1Cell01`
`vmware.vm.name`	string	experimental The name of the virtual machine.	`easytravel-demo`
`vmware.disk.name`	string	experimental ESXi Host Disk.	`srvwasapp1Cell01`

Vulnerability

Fields

Attribute	Type	Description	Examples
`vulnerability.id`	string	stable Dynatrace unique identifier for the vulnerability.	`2039861408676243188`
`vulnerability.display_id`	string	stable Dynatrace user-readable identifier for the vulnerability.	`S-1234`
`vulnerability.external_id`	string	stable External provider's unique identifier for the vulnerability.	`SNYK-JAVA-ORGAPACHEHTTPCOMPONENTS-30646`
`vulnerability.type`	string	stable Classification of the vulnerability based on commonly accepted enums, such as CWE.	`Improper Input Validation`
`vulnerability.stack`	string	experimental Level of the vulnerable component in the technological stack.	`CODE`; `CODE_LIBRARY`; `SOFTWARE`; `CONTAINER_ORCHESTRATION`
`vulnerability.technology`	string	stable Technology of the vulnerable component.	`JAVA`; `DOT_NET`; `GO`; `PHP`; `NODE_JS`; `KUBERNETES`
`vulnerability.title`	string	stable Title of the vulnerability.	`Improper Input Validation`
`vulnerability.description`	string	stable Description of the vulnerability.	`More detailed description about improper input validation vulnerability.`
`vulnerability.url`	string	stable Dynatrace URL to the details page of the vulnerability. \|	`https://example.com`
`vulnerability.external_url`	string	stable External provider's URL to the details page of the vulnerability.	`https://example.com`
`vulnerability.references.cve`	string[]	stable List of the vulnerability's CVE IDs.	`[CVE-2021-41079]`
`vulnerability.references.cwe`	string[]	stable List of the vulnerability's CWE IDs.	`[CWE-20]`
`vulnerability.references.owasp`	string[]	stable List of vulnerability's OWASP IDs.	`[2021:A3]`
`vulnerability.resolution.status`	string	stable Vulnerability's resolution status.	`OPEN`; `RESOLVED`
`vulnerability.resolution.change_date`	timestamp	stable Timestamp of the vulnerability's last status change.	`2023-03-22T13:19:37.466Z`
`vulnerability.cvss.base_score`	double	stable Vulnerability's CVSS base score provided by NVD.	`8.1`
`vulnerability.cvss.version`	string	stable Vulnerability's CVSS score version.	`3.1`
`vulnerability.risk.score`	double	stable Vulnerability's risk score defined by the provider. For Dynatrace, Davis Security Score.	`8.1`
`vulnerability.risk.level`	string	stable Vulnerability's risk score level defined by the provider. For Dynatrace, the Davis Security Score level.	`LOW`; `MEDIUM`; `HIGH`; `CRITICAL`
`vulnerability.risk.scale`	string	stable Scale by which the vulnerability's risk score and risk score level defined by the provider are measured.	`Davis Security Score`
`vulnerability.davis_assessment.score`	double	stable Vulnerability's Davis Security Score (1-10) calculated by Dynatrace.	`8.1`
`vulnerability.davis_assessment.level`	string	stable Vulnerability's risk level based on Davis Security Score.	`LOW`; `MEDIUM`; `HIGH`; `CRITICAL`
`vulnerability.davis_assessment.exposure_status`	string	stable Vulnerability's internet exposure status.	`NOT_AVAILABLE`; `NOT_DETECTED`; `PUBLIC_NETWORK`
`vulnerability.davis_assessment.data_assets_status`	string	stable Vulnerability's reachability of related data assets by affected entities.	`NOT_AVAILABLE`; `NOT_DETECTED`; `REACHABLE`
`vulnerability.davis_assessment.assessment_mode`	string	stable Availability of the information based on which the vulnerability assessment has been done.	`FULL`; `NOT_AVAILABLE`; `REDUCED`
`vulnerability.davis_assessment.exploit_status`	string	stable Vulnerability's public exploits status.	`AVAILABLE`; `NOT_AVAILABLE`
`vulnerability.davis_assessment.vulnerable_function_status`	string	stable Usage status of the vulnerable functions causing the vulnerability.	`IN_USE`; `NOT_AVAILABLE`; `NOT_IN_USE`
`vulnerability.first_seen`	timestamp	stable Timestamp of when the vulnerability was first detected.	`2023-03-22T13:19:36.945Z`
`vulnerability.parent.resolution.status`	string	stable Current status of the vulnerability.	`OPEN`; `RESOLVED`
`vulnerability.parent.resolution.change_date`	string	stable Timestamp of the vulnerability's last status change.	`2023-03-22T13:19:37.466Z`
`vulnerability.parent.risk.score`	double	stable Vulnerability's risk score defined by the provider. For Dynatrace, Davis Security Score.	`8.1`
`vulnerability.parent.risk.level`	string	stable Vulnerability's risk score level defined by the provider. For Dynatrace, the Davis Security Score level.	`LOW`; `MEDIUM`; `HIGH`; `CRITICAL`
`vulnerability.parent.davis_assessment.score`	double	stable Vulnerability's Davis Security Score (1-10) calculated by Dynatrace.	`8.1`
`vulnerability.parent.davis_assessment.level`	string	stable Vulnerability's Davis Security Score level.	`LOW`; `MEDIUM`; `HIGH`; `CRITICAL`
`vulnerability.parent.davis_assessment.exposure_status`	string	stable Vulnerability's internet exposure status.	`NOT_AVAILABLE`; `NOT_DETECTED`; `PUBLIC_NETWORK`
`vulnerability.parent.davis_assessment.data_assets_status`	string	stable Vulnerability's reachability of related data assets by affected entities.	`NOT_AVAILABLE`; `NOT_DETECTED`; `REACHABLE`
`vulnerability.parent.davis_assessment.assessment_mode`	string	stable Availability of the information based on which the vulnerability assessment has been done.	`FULL`; `NOT_AVAILABLE`; `REDUCED`
`vulnerability.parent.davis_assessment.vulnerable_function_status`	string	stable Usage status of vulnerable functions causing the vulnerability. Status is `IN_USE` when there's at least one vulnerable function in use by an application.	`IN_USE`; `NOT_AVAILABLE`; `NOT_IN_USE`
`vulnerability.parent.first_seen`	string	stable Timestamp of when the vulnerability was first detected.	`2023-03-22T13:19:36.945Z`
`vulnerability.parent.mute.status`	string	stable Vulnerability's mute status.	`MUTED`; `NOT_MUTED`
`vulnerability.mute.status`	string	stable Vulnerability's mute status.	`MUTED`; `NOT_MUTED`
`vulnerability.mute.user`	string	stable User who last changed the vulnerability's mute status.	`user@example.com`
`vulnerability.parent.mute.user`	string	stable User who last changed the vulnerability's mute status.	`user@example.com`
`vulnerability.mute.reason`	string	stable Reason for muting or unmuting the vulnerability.	`FALSE_POSITIVE`; `IGNORE`; `AFFECTED`; `CONFIGURATION_NOT_AFFECTED`; `FALSE_POSITIVE`; `OTHER`
`vulnerability.parent.mute.reason`	string	stable Reason for muting or unmuting the vulnerability.	`FALSE_POSITIVE`; `IGNORE`; `AFFECTED`; `CONFIGURATION_NOT_AFFECTED`; `FALSE_POSITIVE`; `OTHER`
`vulnerability.mute.change_date`	timestamp	stable Timestamp of the vulnerability's last muted or unmuted action.	`2023-03-22T13:19:36.945Z`
`vulnerability.parent.mute.change_date`	timestamp	stable Timestamp of the last mute or unmute action of the vulnerability.	`2023-03-22T13:19:36.945Z`
`vulnerability.previous.risk.score`	double	stable Vulnerability's previous risk score (in case the risk score has changed).	`8.1`
`vulnerability.previous.risk.level`	string	stable Vulnerability's previous risk score level (in case the risk score level has changed).	`LOW`; `MEDIUM`; `HIGH`; `CRITICAL`
`vulnerability.previous.cvss.base_score`	double	stable Vulnerability's previous CVSS base score (in case the CVSS base score has changed).	`8.1`
`vulnerability.previous.davis_assessment.score`	double	stable Vulnerability's previous Davis Security Score (in case Davis Security Score has changed).	`8.1`
`vulnerability.previous.davis_assessment.level`	string	stable Vulnerability's previous risk level (in case the risk level has changed).	`LOW`; `MEDIUM`; `HIGH`; `CRITICAL`
`vulnerability.previous.davis_assessment.exploit_status`	string	stable Vulnerability's previous public exploit status (in case the public exploit status has changed).	`AVAILABLE`; `NOT_AVAILABLE`
`vulnerability.previous.davis_assessment.exposure_status`	string	stable Vulnerability's previous internet exposure status (in case the internet exposure status has changed).	`NOT_AVAILABLE`; `NOT_DETECTED`; `PUBLIC_NETWORK`
`vulnerability.previous.davis_assessment.data_assets_status`	string	stable Vulnerability's previous reachability of related data assets by affected entities (in case the reachability has changed).	`NOT_AVAILABLE`; `NOT_DETECTED`; `REACHABLE`
`vulnerability.previous.davis_assessment.vulnerable_function_status`	string	stable Vulnerability's previous vulnerable function status (in case the vulnerable function status has changed).	`IN_USE`; `NOT_AVAILABLE`; `NOT_IN_USE`
`vulnerability.previous.mute.status`	string	stable Vulnerability's previous mute status (in case the mute status has changed).	`MUTED`; `NOT_MUTED`
`vulnerability.previous.mute.user`	string	stable User who last changed the vulnerability's mute status (in case the mute status was last changed by a different user).	`user@example.com`
`vulnerability.previous.mute.reason`	string	stable Reason for last muting or unmuting the vulnerability (in case the reason for muting or unmuting the vulnerability has changed).	`Muted: False positive`
`vulnerability.previous.mute.change_date`	string	stable Timestamp of the vulnerability's previous mute status (in case the mute status has changed).	`2023-03-22T13:19:36.945Z`
`vulnerability.previous.resolution.status`	string	stable Vulnerability's previous resolution status (in case the resolution status has changed).	`OPEN`; `RESOLVED`
`vulnerability.code_location.name`	string	stable Name of the code location where the code-level vulnerability was detected.	`org.dynatrace.profileservice.BioController.markdownToHtml(String):80`

WebLogic

Fields

Attribute	Type	Description	Examples
`weblogic.cluster.name`	string	experimental The name of the cluster this instance belongs to.	`OrderManagement2`
`weblogic.domain.name`	string	experimental The name of the domain this instance belongs to.	`CustomerManagementFulfillmentSvc`
`weblogic.home`	string	experimental The instance's home directory.	`/apps/infra/wls/bin/10.3.6_64/wlserver_10.3/server`
`weblogic.server.name`	string	experimental The instance's server name.	`OrderManagement2Srv1`

WebSphere

Fields

Attribute	Type	Description	Examples
`websphere.cell.name`	string	experimental The name of the cell this instance belongs to.	`srvwasapp1Cell01`
`websphere.cluster.name`	string	experimental The name of the cluster this instance belongs to.	`CluApp1`
`websphere.node.name`	string	experimental The name of the node this instance belongs to.	`nodeSrvApp2`
`websphere.server.name`	string	experimental The instance's server name.	`SrvApp2`

WebSphere Liberty

Fields

Attribute	Type	Description	Examples
`websphere_liberty.server.name`	string	experimental The instance's server name.	`defaultServer`

z/OS

Fields zos resource attributes

Attribute	Type	Description	Examples
`zos.address_space_id`	long	experimental The address space identifier (ASID) of the z/OS address space.	`1`; `296`
`zos.job_name`	string	experimental The jobname of the z/OS address space.	`CICSAOR0`; `CTGATM00`; `IMSCR15`
`zos.job_id`	string	experimental The job id of the z/OS address space.	`JOB12345`
`zos.job_step_id`	string	experimental The step id within the job within the z/OS address space.	`00000001`; `00000002`
`zos.lpar_name`	string	experimental The name of the LPAR that the z/OS address space executes within.	`S0W1`; `ABCD`
`zos.sys_id`	string	experimental The system ID of the CICS/IMS address space.	`C259`; `CICS`; `IMSF`

Fields zos transactions general

Attribute	Type	Description	Examples
`zos.transaction.id`	string	experimental The ID of this transaction.	`CEMT`; `DTAX`; `IVTNO`
`zos.transaction.call_type`	string	experimental The type of transaction call that was invoked.	`CTG`
`zos.transaction.job_name`	string	experimental The jobname of the z/OS address space that the transaction executed in.	`CICSAOR0`; `CTGATM00`; `IMSCR15`
`zos.transaction.lpar_name`	string	experimental The name of the LPAR that the transaction executed on.	`S0W1`; `ABCD`
`zos.transaction.program_type`	string	experimental The type of transaction that was executed.	`DLI_DB`; `DLI_DC`; `MQ`; `DB2`

zos.transaction.call_type MUST be one of the following:

Value	Description
`CTG`	A CTG request triggered this transaction.
`DPL`	A CICS DPL request triggered this transaction.
`HTTP`	An HTTP or HTTPS request triggered this transaction.
`IMS_CONNECT`	An IMS Connect request triggered this transaction.
`IMS_CONNECT_API`	An IMS Connect API request triggered this transaction.
`ITRA`	An IMS TM Resource Adapter request triggered this transaction.
`MQ`	An MQ operation triggered this transaction.
`MSC`	An IMS MSC request triggered this transaction.
`PGM_SWITCH`	An IMS Program Switch request triggered this transaction.
`SDK`	An SDK call triggered this transaction.
`SHARED_QUEUE`	An IMS Shared Queue request triggered this transaction.
`SOAP`	A SOAP request triggered this transaction.
`START`	An EXEC CICS START triggered this transaction.
`TTX`	A green screen terminal transaction code triggered this transaction.
`TX`	A CICS or IMS transaction code triggered this transaction.
`ZOS_CONNECT`	A z/OS Connect request triggered this transaction.

zos.transaction.program_type MUST be one of the following:

Value	Description
`DB2`	The transaction performs DB2 database actions.
`DLI_DB`	The transaction performs DLI database actions.
`DLI_DC`	The transaction performs DLI data communications actions.
`MQ`	The transaction performs MQ Queue actions.

Fields cics transasctions

Attribute	Type	Description	Examples
`cics.transaction.system_id`	string	experimental The system ID of the CICS region that this transaction executed on.	`C259`; `CICS`
`cics.transaction.task_id`	long	experimental The CICS task ID of this transaction.	`1234`
`cics.transaction.unit_of_work_id`	long	experimental The unit of work ID for this transaction, which is normally represented as a hex value.	`15977055984148641282`; `15977055491352760323`
`cics.transaction.path.name`	string	experimental The path name, only applicable for web requests.	`/dtrouter`; ``
`cics.transaction.user_id`	string	experimental The user ID of the user who triggered this transaction.	`USER1`; `anon`
`cics.transaction.client.ip`	ipAddress	experimental IP address of the client (IPv4 or IPv6) that made the request that triggered the transaction.	`194.232.104.141`; `2a01:468:1000:9::140`
`cics.transaction.client.port`	long	experimental Port number of the client that made the request that triggered the transaction.	`65123`; `80`
`cics.transaction.class_name`	string	experimental The name of the transaction class of this transaction.	`null`; `DFHTCL00`
`cics.transaction.wlm.service_class_name`	string	experimental The name of the z/OS Workload Manager (WLM) service class of this transaction.	`null`; `SYSSTC`; `VEL15I5`
`cics.transaction.wlm.reporting_service_class_name`	string	experimental The name of the z/OS Workload Manager (WLM) reporting service class of this transaction.	`null`; `BAT_ATM`; `RC_CICS`

Fields cics files

Attribute	Type	Description	Examples
`cics.file_name`	string	experimental The logical name of the file, as defined in CEDA.	`EXMPCAT`; `CICSFILE`
`cics.file.is_local`	boolean	experimental A boolean that is true if the file is defined within the CICS region that it executed in.	`True`
`cics.file.defining_region_name`	string	experimental The system ID of the CICS region that is defined on the request.	`C259`; `CICS`

Fields ims transactions

Attribute	Type	Description	Examples
`ims.message.transaction.terminal_name`	string	experimental The terminal name that this IMS transaction executed on.	`HWSAM5ZD`; `10505`
`ims.message.transaction.unit_of_work_id`	long	experimental The unit of work ID for this transaction, which is normally represented as a hex value.	`5981228500318430862871015129591113287966852300630664295044916520394057871645605888`; `5981112713529734741010744557477214433959078921583025076794253743298954785382793216`
`ims.message.transaction.user_id`	string	experimental The user ID of the user who triggered this transaction.	`USER1`; `anon`
`ims.message.transaction.message.size`	long	experimental The size of the message.	`10`; `421`
`ims.message.transaction.message.segment_count`	long	experimental The number of segments in the message.	`1`; `5`

Fields ims execution transactions

Attribute	Type	Description	Examples
`ims.execution.transaction.psb_name`	string	experimental The PSB name that this IMS transaction executed on.	`HWSAM5ZD`; `10505`
`ims.execution.transaction.unit_of_work_id`	long	experimental The unit of work ID for this transaction, which is normally represented as a hex value.	`5981228500318430862871015129591113287966852300630664295044916520394057871645605888`; `5981112713529734741010744557477214433959078921583025076794253743298954785382793216`
`ims.execution.transaction.schedule_count`	long	experimental The schedule count for this transaction.	`346613`; `421`
`ims.execution.transaction.commit_count`	long	experimental The commit count for this transaction.	`4`; `5`
`ims.execution.transaction.execution_class`	long	experimental The execution class of this transaction.	`45`; `66`
`ims.execution.transaction.current_priority`	long	experimental The current priority of this transaction.	`1`; `5`

Fields ims connect transactions

Attribute	Type	Description	Examples
`ims.connect.transaction.user_id`	string	experimental The user ID of the user who triggered this transaction.	`USER1`; `anon`
`ims.connect.transaction.client.ip`	ipAddress	experimental IP address of the client (IPv4 or IPv6) that made the request that triggered the transaction.	`194.232.104.141`; `2a01:468:1000:9::140`
`ims.connect.transaction.server.port`	long	experimental Port number on the IMS Connect server that received the request for this transaction	`65123`; `80`

Fields ims tm resource adapter (ITRA) transactions

Attribute	Type	Description	Examples
`ims.tm.resource.adapter.semantic_detection_version`	string	experimental The detection version for this transaction.	`1`
`ims.tm.resource.adapter.transaction.datastore_name`	string	experimental The datastore name used by this transaction.	`IMS1500`
`ims.tm.resource.adapter.transaction.lpar_name`	string	experimental The name of the LPAR that the transaction executed on.	`S0W1`; `ABCD`
`ims.tm.resource.adapter.transaction.client.ip`	ipAddress	experimental IP address of the client (IPv4 or IPv6) that made the request that triggered the transaction.	`194.232.104.141`; `2a01:468:1000:9::140`
`ims.tm.resource.adapter.transaction.client.port`	long	experimental Port number of the client that made the request that triggered the transaction.	`65123`; `80`
`ims.tm.resource.adapter.transaction.interaction_verb`	long	experimental The interaction verb that triggered the transaction.	`0`
`ims.tm.resource.adapter.transaction.commit_mode`	long	experimental The commit mode of the transaction.	`0`
`ims.tm.resource.adapter.transaction.sync_level`	long	experimental Indicates the synchronization level of the transaction. This only applies when the interaction verb is set to "SYNC_SEND_RECEIVE", "SYNC_SEND", or "SYNC_RECEIVE_CALLOUT". This attribute applies to both conversational and non-conversational applications. It is used in conjuction with the ims.transaction.request.transaction.commit_mode attribute.	`0`

ims.tm.resource.adapter.transaction.interaction_verb MUST be one of the following:

Value	Description
`0`	SYNC_SEND
`1`	SYNC_SEND_RECEIVE
`3`	SYNC_END_CONVERSATION
`4`	SYNC_RECEIVE_ASYNCOUTPUT
`5`	SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_NOWAIT
`6`	SYNC_RECEIVE_ASYNCOUTPUT_SINGLE_WAIT
`7`	SYNC_RECEIVE_CALLOUT

ims.tm.resource.adapter.transaction.commit_mode MUST be one of the following:

Value	Description
`0`	The commit happens before sending the response.
`1`	The commit is deferred until the response has been sent and acknowledged.

ims.tm.resource.adapter.transaction.sync_level MUST be one of the following:

Value	Description
`0`	There will be no synchronization.
`1`	Synchronization will be confirmed.

z/OS Connect

Fields

Attribute	Type	Description	Examples
`zosconnect.request.id`	long	experimental The z/OS Connect request ID.	`2215`
`zosconnect.service.provider.name`	string	experimental The service provider name.	`CICS-1.0`
`zosconnect.sor.reference`	string	experimental The system of record reference.	`cicsConn`
`zosconnect.sor.identifier`	string	experimental The system of record identifier. The format differs depending on the SOR type. ¹	`localhost:8080`
`zosconnect.sor.resource`	string	experimental Identifier for the resource invoked on the system of record. The format differs depending on the SOR type. ²	`01,DFH0XCMN`
`zosconnect.sor.type`	string	experimental The system of record type.	`CICS`
`zosconnect.request.body.size`	long	experimental The size of the request payload in bytes.	`234`
`zosconnect.response.body.size`	long	experimental The size of the response payload in bytes.	`125`
`zosconnect.api.name`	string	experimental The z/OS Connect API name.	`catalog`
`zosconnect.service.name`	string	experimental The z/OS Connect service name.	`placeOrder`
`zosconnect.api.description`	string	experimental The z/OS Connect API description.	`API for the CICS catalog manager sample application`
`zosconnect.service.description`	string	experimental The z/OS Connect service description.	`EDUCHAN service using the CICS Service Provider`
`zosconnect.api.version`	string	experimental The z/OS Connect API version.	`1.0.0`
`zosconnect.service.version`	string	experimental The z/OS Connect service version.	`2.0`
`zosconnect.request.type`	string	experimental The type of the REST request. ³	`ADMIN`
¹ see https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/javadoc/com/ibm/zosconnect/spi/Data.html?view=embed#SOR_IDENTIFIER ² see https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/javadoc/com/ibm/zosconnect/spi/Data.html?view=embed#SOR_RESOURCE ³ see https://www.ibm.com/support/knowledgecenter/SS4SVW_3.0.0/javadoc/com/ibm/zosconnect/spi/Data.RequestType.html

zosconnect.sor.type MUST be one of the following:

Value	Description
`CICS`	cics
`IMS`	ims
`MQ`	mq
`REST`	rest
`WOLA`	wola

zosconnect.request.type MUST be one of the following:

Value	Description
`ADMIN`	admin
`API`	api
`SERVICE`	service
`UNKNOWN`	unknown