This section contains all entity types that are considered core entities.
smartscapeNodes {HOST, PROCESS, SERVICE, CONTAINER}
Smartscape node name: dt.service.name
Smartscape node type: SERVICE
An Application Observability (AppObs) service entity detected by service detection.
Service entities represent the horizontal topology of your environment based on distributed tracing data, providing detailed insights into caller-callee relationships.
Unlike other Smartscape entities, service entities do not contain primary Grail fields due to the flexibility of service detection rules. Use the following service timeseries instead to query this data (refer to the query examples below).
dt.service.request.countdt.service.messaging.receive.countdt.service.messaging.process.countdt.service.faas_invoke.countFind all service entities.
smartscapeNodes SERVICE
Count all service relationships, grouped by relationship type.
smartscapeEdges "*"| filter source_type == "SERVICE"| fields type, source_id, source_type, target_id, target_type, dt.system.edge_kind| summarize count(), by:{type}
Count runs_on relationships from services, grouped by target entity type.
smartscapeEdges runs_on| filter source_type == "SERVICE"| summarize count(), by:{target_type}
Count belongs_to relationships from services, grouped by target entity type.
smartscapeEdges belongs_to| filter source_type == "SERVICE"| summarize count(), by:{target_type}
Traverse all service-to-service call relationships of a service.
smartscapeNodes SERVICE| filter id == toSmartscapeId("SERCICE-0123456789ABCDEF")| traverse {"calls"}, {"SERVICE"}, direction:"forward"
Query the average response time for all downstream services called by a specific service (identified by its ID).
timeseries avg(dt.service.request.response_time), filter:dt.smartscape.service in [smartscapeEdges "calls"| filter source_type == "SERVICE"| filter source_id == toSmartscapeId("SERCICE-0123456789ABCDEF")| fields target_id], by:{dt.smartscape.service}
Query the 95th percentile response time for all downstream services called by a specific service (identified by its name).
timeseries responseTime_p95_timeseries = percentile(dt.service.request.response_time, 95), filter:dt.smartscape.service in [smartscapeNodes "SERVICE"| filter name == "checkout-service"| traverse {"calls"}, {"SERVICE"}, direction:"forward"| fields id], by:{dt.smartscape.service}, nonempty: true| fieldsAdd metricName = "Response time p95"
Get service entities with primary fields
timeseries avg(dt.service.request.count), by:{dt.smartscape.service, dt.service.name, aws.account.id,aws.region,azure.location,azure.resource.group,azure.subscription,dt.host_group.id,gcp.project.id,gcp.region,k8s.cluster.name,k8s.namespace.name}| fields id = dt.smartscape.service, name = dt.service.name, aws.account.id,aws.region,azure.location,azure.resource.group,azure.subscription,dt.host_group.id,gcp.project.id,gcp.region,k8s.cluster.name,k8s.namespace.name
The following base fields are used for all entities.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| smartscapeId | stableA Smartscape ID consists of two components: an UPPER_CASE entity type and a random 16-character hexadecimal unique identifier, separated by a dash. Use Smartscape conversion functions when working with strings that represent Smartscape IDs. |
|
| string | deprecatedThe entity ID that was used in the classic entity store. This ID is present in old monitoring data. Not all entities have this ID, and it is not generated for new entities. Use the |
|
| string | stableThe entity name. |
|
| string | stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity. |
|
| record | stableA consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, |
|
| timeframe | stableThe lifetime of the entity. This is a record with two nested fields: |
|
| record | stableProvides access to static edges pointing to other entities. In this record each nested field represents a relationship type and target type, and the value is an array of target smartscape IDs. This field is hidden by default but can be added using the fieldsAdd command. |
|
| string[] | resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: |
|
Fields specific to services.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | stableThe version of the service detection mechanism used to identify the service. Either |
|
| string | stableThe SDv1 service type. This field is available only if |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| record | stableThis is similar to an aggregation in UML. It is a many-to-many relationship without existential properties (the destination is not composed of the sources).Relationships: |
|
| record | stableDefines a "horizontal" relationship between two entities that "call" each other. The "calls" relation does not imply a parent/child or other strong structural relation but rather a dynamic communication association. Examples: Typical examples include services calling other services, but also services calling databases, queue brokers, or other infrastructure entities.Relationships: | |
| record | stableDefines a "vertical" relation of an entity running on some other entity. It does not imply any composition or aggregation but only a looser association between the entities. One entity can run on multiple other entities. Examples: Service running on a POD, a CONTAINER or a HOST.Relationships: |
Smartscape node name: container.name
Smartscape node type: CONTAINER
A container entity. Provides the core container fields plus potentially additional platform specific fields.
Load all container entities from Smartscape and get their names.
smartscapeNodes CONTAINER| fields name
Get all hosts that run containers in the "travel-advisor-demo" namespace.
smartscapeNodes CONTAINER| filter k8s.namespace.name == "travel-advisor-demo"| traverse runs_on, HOST
Get all containers with their IDs, names, namespace names, and Kubernetes labels.
smartscapeNodes CONTAINER| fields id, name, k8s.namespace.name, k8s_labels = getNodeField(references[belongs_to.k8s_namespace][0], "tags:k8s.labels")
The following base fields are used for all entities.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| smartscapeId | stableA Smartscape ID consists of two components: an UPPER_CASE entity type and a random 16-character hexadecimal unique identifier, separated by a dash. Use Smartscape conversion functions when working with strings that represent Smartscape IDs. |
|
| string | deprecatedThe entity ID that was used in the classic entity store. This ID is present in old monitoring data. Not all entities have this ID, and it is not generated for new entities. Use the |
|
| string | stableThe entity name. |
|
| string | stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity. |
|
| record | stableA consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, |
|
| timeframe | stableThe lifetime of the entity. This is a record with two nested fields: |
|
| record | stableProvides access to static edges pointing to other entities. In this record each nested field represents a relationship type and target type, and the value is an array of target smartscape IDs. This field is hidden by default but can be added using the fieldsAdd command. |
|
| string[] | resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource experimentalName of the image the container was built on. |
|
| string | resource experimental |
|
| string | resource experimentalImmutable SHA‑256 hash of an image that uniquely identifies the exact image content in a registry. |
|
| string | resource experimentalContainer ID. Usually a UUID, as for example used to identify Docker containers. The UUID might be abbreviated. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource stableThe user-defined name of the cluster in Dynatrace. Doesn't need to be unique or immutable.Tags: |
|
| string | resource stableA pseudo-ID for the cluster, by default set to the UID of the kube-system namespace. |
|
| string | resource stableThe name of the namespace that the pod is running in.Tags: |
|
| string | resource stableThe name of the workload. |
|
| string | resource stableThe type of the workload. The value is the Kubernetes object kind of the workload in lowercase. |
|
| string | resource stableName of the node. |
|
| string | resource stableThe name of the pod. |
|
| string | resource stableThe UID of the pod. |
|
| string | resource stableThe name of the container from the pod specification; must be unique within a pod. Container runtime usually uses different globally unique name ( |
|
| string | resource experimentalThe type of the Kubernetes container. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| record | stableThis is similar to an aggregation in UML. It is a many-to-many relationship without existential properties (the destination is not composed of the sources).Relationships: |
|
| record | stableDefines if the instance is part of a cluster, similar to a composition in UML. The source (child) cannot exist without the destination (parent).Relationships: |
|
| record | stableDefines a "vertical" relation of an entity running on some other entity. It does not imply any composition or aggregation but only a looser association between the entities. One entity can run on multiple other entities. Examples: Service running on a POD, a CONTAINER or a HOST.Relationships: |
Smartscape node type: FRONTEND
Representation of a Digital Experience Monitoring (DEM) frontend entity.
Load all FRONTEND entities.
smartscapeNodes FRONTEND
The following base fields are used for all entities.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| smartscapeId | stableA Smartscape ID consists of two components: an UPPER_CASE entity type and a random 16-character hexadecimal unique identifier, separated by a dash. Use Smartscape conversion functions when working with strings that represent Smartscape IDs. |
|
| string | deprecatedThe entity ID that was used in the classic entity store. This ID is present in old monitoring data. Not all entities have this ID, and it is not generated for new entities. Use the |
|
| string | stableThe entity name. |
|
| string | stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity. |
|
| record | stableA consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, |
|
| timeframe | stableThe lifetime of the entity. This is a record with two nested fields: |
|
| record | stableProvides access to static edges pointing to other entities. In this record each nested field represents a relationship type and target type, and the value is an array of target smartscape IDs. This field is hidden by default but can be added using the fieldsAdd command. |
|
| string[] | resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | stableThe frontend name determined at ingest.Tags: |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| record | stableDefines a "horizontal" relationship between two entities that "call" each other. The "calls" relation does not imply a parent/child or other strong structural relation but rather a dynamic communication association. Examples: Typical examples include services calling other services, but also services calling databases, queue brokers, or other infrastructure entities.Relationships: |
Smartscape node name: disk.name
Smartscape node type: DISK
A disk entity. Represents a storage disk attached to a host.
Load all disks and get the host groups of their parent hosts
smartscapeNodes DISK| fieldsAdd dt.host_group.id = getNodeField(references[belongs_to.host][0], "dt.host_group.id")
Get all disks attached to the sap-hana-db host
smartscapeNodes HOST| filter name == "sap-hana-db"| traverse belongs_to, DISK, direction:backward
The following base fields are used for all entities.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| smartscapeId | stableA Smartscape ID consists of two components: an UPPER_CASE entity type and a random 16-character hexadecimal unique identifier, separated by a dash. Use Smartscape conversion functions when working with strings that represent Smartscape IDs. |
|
| string | deprecatedThe entity ID that was used in the classic entity store. This ID is present in old monitoring data. Not all entities have this ID, and it is not generated for new entities. Use the |
|
| string | stableThe entity name. |
|
| string | stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity. |
|
| record | stableA consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, |
|
| timeframe | stableThe lifetime of the entity. This is a record with two nested fields: |
|
| record | stableProvides access to static edges pointing to other entities. In this record each nested field represents a relationship type and target type, and the value is an array of target smartscape IDs. This field is hidden by default but can be added using the fieldsAdd command. |
|
| string[] | resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | resource stableUnique identifier of remote disk |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| record | stableThis is similar to an aggregation in UML. It is a many-to-many relationship without existential properties (the destination is not composed of the sources).Relationships: |
|
Smartscape node name: host.name
Smartscape node type: HOST
A host entity representing either a virtual or physical machine, providing an OS-level view of the infrastructure. When OneAgent is running in application-only mode within a container, it can't provide a full OS-level view for the host running the container, so no host entity is created.
The tags field may contain tags from the following sources:
tags:environment: Environment tags—see Define tags and metadata for hoststags:aws: AWS tags defined on the EC2 instance - requires access to tags in the instance metadatatags:azure: Azure tags defined on the Azure VMtags:gcp: GCP tags defined on the GCP Compute Engine instanceFind all hosts that belong to the discovery-mode-demo host group.
smartscapeNodes HOST| filter dt.host_group.id == "discovery-mode-demo"
Find all hosts that belong to the demoability team.
smartscapeNodes HOST| filter tags[dt_owner_team] == "team-demoability"
Find all resources of hosts that belong to the discovery-mode-demo host group.
smartscapeNodes HOST| filter dt.host_group.id == "discovery-mode-demo"| traverse {belongs_to}, {DISK, NETWORK_INTERFACE}, direction:backward
Find all EC2 instances that run hosts with x86 architecture and get their host group IDs.
smartscapeNodes HOST| filter host.additional_system_info[system.architecture] == "x86"| traverse runs_on, AWS_EC2_INSTANCE, fieldsKeep:dt.host_group.id| fields id, name, dt.host_group.id = dt.traverse.history[-1][dt.host_group.id]
The following base fields are used for all entities.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| smartscapeId | stableA Smartscape ID consists of two components: an UPPER_CASE entity type and a random 16-character hexadecimal unique identifier, separated by a dash. Use Smartscape conversion functions when working with strings that represent Smartscape IDs. |
|
| string | deprecatedThe entity ID that was used in the classic entity store. This ID is present in old monitoring data. Not all entities have this ID, and it is not generated for new entities. Use the |
|
| string | stableThe entity name. |
|
| string | stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity. |
|
| record | stableA consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, |
|
| timeframe | stableThe lifetime of the entity. This is a record with two nested fields: |
|
| record | stableProvides access to static edges pointing to other entities. In this record each nested field represents a relationship type and target type, and the value is an array of target smartscape IDs. This field is hidden by default but can be added using the fieldsAdd command. |
|
| string[] | resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: |
|
Fields that are provided for compute units, both virtual machines and physical hosts.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | experimentalNumber of primary compute units available on the monitored host. On bare metal machines this means physical CPUs. In virtualized environments these are the cores exposed by the hypervisor (vCPUs). Use logical_cores for scheduler visible count. |
|
| string | experimentalNumber of logical execution contexts (logical cores) visible to the operating system scheduler on monitored host. This includes SMT / Hyper-Threading. |
|
| string | experimentalTotal memory of monitored host, expressed in bytes. |
|
| string | experimentalVirtual Machine SKU |
|
| string | experimentalTodo |
|
| ipAddress[] | experimentalIP address that is publicaly accessible. This is usually an IP address assigned to a NAT gateway or a load balancer, rather than to the instance itself. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| record | experimentalAdditional system information. Some attributes here are only available on certain systems (e.g. system.lpar exists only on AIX). Several attributes are numbered. E.g. attributes starting with system.processor_. will have the underscore programatically replaced with an index like [12], starting from [0]. Note that in these examples, a '_' is replaced with '[x]', where x is a number starting from 0. | |
| record[] | experimentalAn array of software technologies associated with a host entity. Contains individual records with the following fields: type, edition, version. |
|
| record | experimentalA collection of additional metadata information imported to Dynatrace. |
|
| string | resource experimentalVirtualization hypervisor identified. For physical machines, this value is empty. |
|
| string[] | experimentalA collection of MAC addresses that can be used to identify this entity. |
|
| string | resource experimentalArchitecture of the CPU, discovered from the operating system. |
|
| string | resource experimentalType of discovered operating system. |
|
| string | resource stableThe complete OS version, including patch, build, and other information. |
|
| long | resource experimentalPhysical memory of the monitored host, expressed in bytes. The value might be different than the total available memory, if features such as Active Memory Expansion are used. |
|
| string | resource stableSee Organize your environment using host groups. Note that host groups are identified by their name, not by the entity ID of the host group entity. For details on the entity ID, see |
|
| ipAddress[] | experimentalA collection of IP addresses that may be used to identify this entity. |
|
| boolean | resource experimentalIndicates whether the host has public traffic detected via eBPF Discovery. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource stableThe user-defined name of the cluster in Dynatrace. Doesn't need to be unique or immutable.Tags: |
|
| string | resource stableA pseudo-ID for the cluster, by default set to the UID of the kube-system namespace. |
|
| string | resource stableName of the node. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource stableA specific availability zone or array of zones in given AWS region. |
|
| string | resource stableA specific geographical AWS Cloud location.Tags: |
|
| string | resource stableUnique, immutable identifier assigned to the AWS cloud resource. |
|
| string | resource stableThe 12-digit number, such as 123456789012, that uniquely identifies an AWS account.Tags: |
|
| string | resource stableAmazon Resource Name (ARN). |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource stableA resource group is a container that holds related resources for an Azure solution.Tags: |
|
| string | resource stableAn Azure subscription is a logical container used to provision resources in Azure.Tags: |
|
| string | resource experimentalA unique, immutable identifier assigned to each Azure cloud resource. |
|
| string | resource stableA specific geographical location of Azure cloud resource.Tags: |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource stableIdentifier of the GCP project associated with this resource.Tags: |
|
| string | resource stableA region is a specific geographical location where you can host your resources.Tags: |
|
| string | resource stableThe globally unique resource name in Google Cloud Platform convention. |
|
| string | resource stableRegion or zone where GCP resource instance is running. |
|
| string | resource stableThe name of a monitored resource type available in Google Cloud Monitoring and Logging. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | resource experimentalNumber of virtual CPUs for AIX LPAR. |
|
| long | resource experimentalLogical CPUs on the monitored host. Applies to AIX LPARs. |
|
| long | resource experimentalNumber of threads for AIX Simultaneous Multithreading feature. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource experimentalThe name of the LPAR that the z/OS address space executes within. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource experimentalA unique identifier to a deployment or instance. |
|
| string | resource experimentalA unique identifier assigned to each deployed instance. |
|
| string | resource experimentalA specific geographical BOSH location. |
|
| string | resource stableBOSH depoloyment ID, retrievied from /var/vcap on monitored host. |
|
| string | resource stableBOSH instance name, retrievied from /var/vcap on monitored host. |
|
| string | resource stableVersion of BOSH stemcell, retrievied from /var/vcap on monitored host. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| record | stableDefines a "horizontal" relationship between two entities that "call" each other. The "calls" relation does not imply a parent/child or other strong structural relation but rather a dynamic communication association. Examples: Typical examples include services calling other services, but also services calling databases, queue brokers, or other infrastructure entities.Relationships: |
Smartscape node name: network_interface.name
Smartscape node type: NETWORK_INTERFACE
A network interface entity. Represents a network interface attached to a host.
Load all network interfaces and get the host name of their parent hosts
smartscapeNodes NETWORK_INTERFACE| fieldsAdd host.name = getNodeName(references[belongs_to.host][0])
Find the host to which the network interface with the specified MAC address is attached.
smartscapeNodes NETWORK_INTERFACE| filter mac == "16:FF:F1:39:CE:99"| traverse belongs_to, HOST
The following base fields are used for all entities.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| smartscapeId | stableA Smartscape ID consists of two components: an UPPER_CASE entity type and a random 16-character hexadecimal unique identifier, separated by a dash. Use Smartscape conversion functions when working with strings that represent Smartscape IDs. |
|
| string | deprecatedThe entity ID that was used in the classic entity store. This ID is present in old monitoring data. Not all entities have this ID, and it is not generated for new entities. Use the |
|
| string | stableThe entity name. |
|
| string | stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity. |
|
| record | stableA consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, |
|
| timeframe | stableThe lifetime of the entity. This is a record with two nested fields: |
|
| record | stableProvides access to static edges pointing to other entities. In this record each nested field represents a relationship type and target type, and the value is an array of target smartscape IDs. This field is hidden by default but can be added using the fieldsAdd command. |
|
| string[] | resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: |
|
Fields specific to network interfaces.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| long | experimentalSpeed of the network interface, expressed in bits per second. |
|
| string[] | experimentalA collection of MAC addresses that can be used to identify this entity. |
|
| ipAddress[] | experimentalA collection of IP addresses that may be used to identify this entity. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| record | stableThis is similar to an aggregation in UML. It is a many-to-many relationship without existential properties (the destination is not composed of the sources).Relationships: |
|
Smartscape node name: os_service.display_name
Smartscape node type: OS_SERVICE
Representation of an operating system service, which is a background process that performs specific functions and is typically managed by the operating system's service manager. OS services can include things like web servers, database servers, and other types of background processes that are essential for the functioning of an operating system and its applications.
Get all OS services attached to the sap-hana-db host
smartscapeNodes HOST| filter name == "sap-hana-db"| traverse belongs_to, OS_SERVICE, direction:backward
The following base fields are used for all entities.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| smartscapeId | stableA Smartscape ID consists of two components: an UPPER_CASE entity type and a random 16-character hexadecimal unique identifier, separated by a dash. Use Smartscape conversion functions when working with strings that represent Smartscape IDs. |
|
| string | deprecatedThe entity ID that was used in the classic entity store. This ID is present in old monitoring data. Not all entities have this ID, and it is not generated for new entities. Use the |
|
| string | stableThe entity name. |
|
| string | stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity. |
|
| record | stableA consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, |
|
| timeframe | stableThe lifetime of the entity. This is a record with two nested fields: |
|
| record | stableProvides access to static edges pointing to other entities. In this record each nested field represents a relationship type and target type, and the value is an array of target smartscape IDs. This field is hidden by default but can be added using the fieldsAdd command. |
|
| string[] | resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource experimentalUnique OS service name. On Windows, this is the short programmatic key as reported by the Service Control Manager (e.g., |
|
| string | resource experimentalThe full path to the process executable. On Linux based systems, this can be set to the target of |
|
| string | resource experimentalCurrent startup type. |
|
| string | experimentalCurrent running state. |
|
| string | resource experimentalManufacturer of the service. On Linux based systems, the value will always be |
|
| boolean | experimentalBoolean attribute deciding whether the service status triggers alerts or not. |
os_service.startup_type MUST be one of the following:
| Value | Description |
|---|---|
| Windows specific. Automatic: The service starts at system logon. |
| Windows specific. Automatic (Delayed Start): The service starts a short while after the system has finished starting up. |
| Windows specific. Automatic (Delayed Start, Trigger Start) |
| Windows specific. Automatic (Trigger Start): This service will start automatically at boot. |
| Linux specific. Service is configured to not start when the system boots, but can be started manually, or as a dependency of another service. |
| Linux specific. Service is marked for starting up on boot. |
| Linux specific. Service is marked for starting up on boot. |
| Windows specific. Manual: The service starts only when explicitly summoned. |
| Windows specific. Manual (Trigger Start): This service will not start automatically at boot. |
| Linux specific. Service will run only if another unit depends on it. |
os_service.status MUST be one of the following:
| Value | Description |
|---|---|
| Service is activating. |
| Service is active. |
| Service continues pending. |
| Service is deactivating. |
| Service failed to start. |
| Service is inactive. |
| Service paused pending. |
| Service is currently paused. |
| Service is reloading. |
| Service is currently running. |
| Service started pending. |
| Service stopped pending. |
| Service is currently stopped. |
| Attribute | Type | Description | Examples |
|---|---|---|---|
| record | stableDefines a "vertical" relation of an entity running on some other entity. It does not imply any composition or aggregation but only a looser association between the entities. One entity can run on multiple other entities. Examples: Service running on a POD, a CONTAINER or a HOST.Relationships: |
Smartscape node name: process.name
Smartscape node type: PROCESS
The process entity aggregates similar processes executing on the same operating system (native or containerized), ensuring data continuity across process restarts and grouping workers performing similar roles. In Dynatrace Classic, this corresponds to the Process Group Instance (PGI).
The tags field may contain tags from the following sources:
tags:environment: Tags based on environment variablesFind all NodeJS processes.
smartscapeNodes PROCESS| fieldsAdd process.software_technologies = arrayConcat(process.software_technologies.os,process.software_technologies.webserver,process.software_technologies.nodejs)| expand process.software_technologies| filter process.software_technologies[type] == "NODE_JS"| dedup id
Find all hosts that have processes listening on port 8080.
smartscapeNodes PROCESS| filter in(port, 8080)| traverse runs_on, HOST
Find all processes with command line arguments "java -jar app.jar".
smartscapeNodes PROCESS| filter process.metadata[COMMAND_LINE_ARGS] == "java -jar app.jar"
Find all processes that call processes with executable name "java".
smartscapeNodes PROCESS| filter process.metadata[EXE_NAME] == "java"| traverse calls, PROCESS, direction:backward
Get a list of all software technologies detected on processes
smartscapeNodes PROCESS| fieldsAdd process.software_technologies = arrayConcat(process.software_technologies.os,process.software_technologies.java,process.software_technologies.dotnet,process.software_technologies.webserver,process.software_technologies.wsb,process.software_technologies.php,process.software_technologies.nodejs,process.software_technologies.ruby,process.software_technologies.varnish,process.software_technologies.go,process.software_technologies.python)
Get the process type based on detected software technologies
smartscapeNodes PROCESS| fieldsAdd process_type = coalesce(if (process.software_technologies.os ~ "REDIS", "REDIS"),if (process.software_technologies.os ~ "MONGODB", "MONGODB"),if (process.software_technologies.os ~ "MSSQL", "MSSQL"),if (process.software_technologies.os ~ "MYSQL", "MYSQL"),if (process.software_technologies.os ~ "SQLITE", "SQLITE"),if (process.software_technologies.os ~ "POSTGRES", "POSTGRES"),if (process.software_technologies.os ~ "ORACLE_DB", "ORACLE_DB"),if (process.software_technologies.os ~ "DB2", "DB2"),if (process.software_technologies.os ~ "TOMCAT", "TOMCAT"),if (process.software_technologies.os ~ "WEBLOGIC", "WEBLOGIC"),if (process.software_technologies.os ~ "WEBSPHERE", "WEBSPHERE"),if (process.software_technologies.os ~ "ACTIVEMQ_CLIENT", "ACTIVEMQ_CLIENT"),if (process.software_technologies.os ~ "JAVA", "JAVA"),if (process.software_technologies.os ~ "NGINX", "NGINX"),if (process.software_technologies.os ~ "APACHE_HTTPD", "APACHE_HTTPD"),if (process.software_technologies.os ~ "IIS_APP_POOL", "IIS_APP_POOL"),if (process.software_technologies.os ~ "IIS", "IIS"),if (process.software_technologies.os ~ "DOTNET", "DOTNET"),if (process.software_technologies.os ~ "NODE_JS", "NODE_JS"),if (process.software_technologies.os ~ "PHP", "PHP"),if (process.software_technologies.os ~ "PYTHON", "PYTHON"),if (process.software_technologies.os ~ "RUBY", "RUBY"),if (process.software_technologies.os ~ "GO", "GO"),if (process.software_technologies.os ~ "ERLANG", "ERLANG"),if (process.software_technologies.os ~ "IBM_CICS_REGION", "IBM_CICS_REGION"),if (process.software_technologies.os ~ "HAPROXY", "HAPROXY"),if (process.software_technologies.os ~ "ENVOY", "ENVOY"),if (process.software_technologies.os ~ "LINUX_SYSTEM", "LINUX_SYSTEM"),if (process.software_technologies.os ~ "WINDOWS_SYSTEM", "WINDOWS_SYSTEM"),if (isNotNull(process.software_technologies.os), process.software_technologies.os[0][type]))
The following base fields are used for all entities.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| smartscapeId | stableA Smartscape ID consists of two components: an UPPER_CASE entity type and a random 16-character hexadecimal unique identifier, separated by a dash. Use Smartscape conversion functions when working with strings that represent Smartscape IDs. |
|
| string | deprecatedThe entity ID that was used in the classic entity store. This ID is present in old monitoring data. Not all entities have this ID, and it is not generated for new entities. Use the |
|
| string | stableThe entity name. |
|
| string | stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity. |
|
| record | stableA consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, |
|
| timeframe | stableThe lifetime of the entity. This is a record with two nested fields: |
|
| record | stableProvides access to static edges pointing to other entities. In this record each nested field represents a relationship type and target type, and the value is an array of target smartscape IDs. This field is hidden by default but can be added using the fieldsAdd command. |
|
| string[] | resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: |
|
Contains fields that share values for all entities belonging to a given process group.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource experimentalThe identifier shared by all entities belonging to a given process group. |
|
| string | resource stableThe name of the process group as it was detect by the agent. |
|
Fields specific to processes.
| Attribute | Type | Description | Examples |
|---|---|---|---|
| array | experimentalKeys of non-ignored input parameters used to calculate the process entity ID. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| boolean | resource experimentalTrue if given process is running inside container. | |
| string | resource experimentalThe architecture of the monitored entity in terms of how many bits compose a basic value. |
|
| record | experimentalA collection of additional metadata information imported to Dynatrace. |
|
| long[] | experimentalA collection of layer 4 ports used to identify this entity. |
|
| record | resource experimentalIt contains a diagnostic collection of input parameters that were used or could have been used in assigning processes to the process entity. |
|
| record[] | experimentalAn array of software technologies observed by the OneAgent OS module associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| record[] | experimentalAn array of software technologies observed by the OneAgent Java module associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| record[] | experimentalAn array of software technologies observed by the OneAgent .NET module associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| record[] | experimentalAn array of web server software technologies observed by the OneAgent web server modules associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| record[] | experimentalAn array of software technologies observed by the OneAgent WSMB module associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| record[] | experimentalAn array of software technologies observed by the OneAgent PHP module associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| record[] | experimentalAn array of software technologies observed by the OneAgent Node.js module associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| record[] | experimentalAn array of software technologies observed by the OneAgent Ruby module associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| record[] | experimentalAn array of software technologies observed by the OneAgent Varnish module associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| record[] | experimentalAn array of software technologies observed by the OneAgent Go module associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| record[] | experimentalAn array of software technologies observed by the OneAgent Python module associated with a process entity. Contains individual records with the following fields: type, edition, version. |
|
| boolean | resource experimentalIndicates whether the process has public traffic detected via eBPF Discovery. |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| string | resource stableThe user-defined name of the cluster in Dynatrace. Doesn't need to be unique or immutable.Tags: |
|
| Attribute | Type | Description | Examples |
|---|---|---|---|
| record | stableDefines a "horizontal" relationship between two entities that "call" each other. The "calls" relation does not imply a parent/child or other strong structural relation but rather a dynamic communication association. Examples: Typical examples include services calling other services, but also services calling databases, queue brokers, or other infrastructure entities.Relationships: | |
| record | stableDefines a "vertical" relation of an entity running on some other entity. It does not imply any composition or aggregation but only a looser association between the entities. One entity can run on multiple other entities. Examples: Service running on a POD, a CONTAINER or a HOST.Relationships: |