Smartscape - Synthetic

Reference
Published Apr 09, 2026

This section documents the entity types related to Dynatrace Synthetic Monitoring. These entities represent synthetic monitors, their steps, the locations from which they run, and the credential vault entries they use. All synthetic entity types are prefixed with BROWSER_MONITOR, HTTP_MONITOR, NETWORK_AVAILABILITY_MONITOR, SYNTHETIC_LOCATION, or CREDENTIAL_VAULT_ENTRY.

You can get an overview of all Synthetic entities with the following DQL query:

smartscapeNodes "BROWSER_MONITOR"
| append [smartscapeNodes "HTTP_MONITOR"]
| append [smartscapeNodes "NETWORK_AVAILABILITY_MONITOR"]
| append [smartscapeNodes "SYNTHETIC_LOCATION"]
| append [smartscapeNodes "CREDENTIAL_VAULT_ENTRY"]
| summarize by:type, count()

All synthetic monitor entities (BROWSER_MONITOR, HTTP_MONITOR, NETWORK_AVAILABILITY_MONITOR) implement the i.synthetic_monitor_interface, which provides common fields for monitor configuration, lifecycle, and execution tracking:

Synthetic monitor interface fields

Attribute	Type	Description	Examples
`created_by`	string	experimental The identifier of the user or system that created the synthetic monitor.	`dt0s08.self-monitoring-slo-configuration-dev@heimdall.dynatrace.com`; `dt0c01.MT2UKK4NT2RT63KETYPJX7BT`
`enabled`	boolean	experimental Indicates whether the synthetic monitor is enabled.	`true`; `false`
`frequency`	long	experimental The frequency of the synthetic monitor executions, expressed in minutes.	`5`; `10`; `15`
`last_failed_execution_timestamp`	timestamp	experimental The timestamp of the last failed execution of the synthetic monitor.	`2026-03-24T13:20:11.933000000+01:00`
`last_modification_source`	string	experimental The source of the last modification of the synthetic monitor, such as "system" or "rest".	`system`; `webui`
`last_modification_timestamp`	timestamp	experimental The timestamp of the last modification of the synthetic monitor.	`2026-01-30T11:33:24.770000000+01:00`
`last_modified_by`	string	experimental The identifier of the user or system that last modified the synthetic monitor.	`tomasz.lis@dynatrace.com`; `SyntheticModificationHelper`
`last_successful_execution_timestamp`	timestamp	experimental The timestamp of the last successful execution of the synthetic monitor.	`2026-03-24T13:24:08.247000000+01:00`

The BROWSER_MONITOR and BROWSER_MONITOR_STEP entities additionally implement i.synthetic_screenshot_interface, providing screenshot capture fields for both successful and failed executions.

The SYNTHETIC_LOCATION entity implements i.synthetic_location_interface, which provides geolocation and infrastructure fields describing the location from which monitors are executed.

Entity types

Entity type	Classic model	Description	Model
`BROWSER_MONITOR`	`dt.entity.synthetic_test`	A browser-based synthetic monitor that simulates user interactions with a web application.	browser_monitor.md
`BROWSER_MONITOR_STEP`	`dt.entity.synthetic_test_step`	An individual step within a browser synthetic monitor.	browser_monitor_step.md
`HTTP_MONITOR`	`dt.entity.http_check`	An HTTP-based synthetic monitor that checks availability and performance of HTTP endpoints.	http_monitor.md
`HTTP_MONITOR_STEP`	`dt.entity.http_check_step`	An individual step within an HTTP synthetic monitor.	http_monitor_step.md
`NETWORK_AVAILABILITY_MONITOR`	`dt.entity.multiprotocol_monitor`	A network-level synthetic monitor that checks availability using protocols such as ICMP or TCP.	network_availability_monitor.md
`SYNTHETIC_LOCATION`	`dt.entity.synthetic_location`	A physical or virtual location (public or private) from which synthetic monitors execute their tests.	synthetic_location.md
`CREDENTIAL_VAULT_ENTRY`	—	A set of credentials stored in the credential vault, used by synthetic monitors for authentication.	credential_vault_entry.md

Relationships between Synthetic entities

The following diagram summarizes the key relationships between synthetic entity types:

BROWSER_MONITOR / HTTP_MONITOR / NETWORK_AVAILABILITY_MONITOR runs_on → SYNTHETIC_LOCATION
BROWSER_MONITOR contains → BROWSER_MONITOR_STEP
HTTP_MONITOR contains → HTTP_MONITOR_STEP
BROWSER_MONITOR_STEP belongs_to → BROWSER_MONITOR
HTTP_MONITOR_STEP belongs_to → HTTP_MONITOR
BROWSER_MONITOR / HTTP_MONITOR uses → CREDENTIAL_VAULT_ENTRY
HTTP_MONITOR updates → CREDENTIAL_VAULT_ENTRY
BROWSER_MONITOR / HTTP_MONITOR is_assigned_to → FRONTEND
BROWSER_MONITOR monitors → FRONTEND
HTTP_MONITOR monitors → SERVICE
NETWORK_AVAILABILITY_MONITOR monitors → HOST

Credential Vault Entry

Smartscape node type: CREDENTIAL_VAULT_ENTRY

Representation of a Credential Vault Entry entity, which represents a set of credentials that can be used in synthetic monitors for authentication purposes.

Query

Load all CREDENTIAL_VAULT_ENTRY entities.

smartscapeNodes CREDENTIAL_VAULT_ENTRY

Base entity fields (i.base_entity)

The following base fields are used for all entities.

Attribute	Type	Description	Examples
`id`	smartscapeId	stable The entity ID.	`HOST-1234`; `K8S_POD-1234`; `SERVICE-1234`
`id_classic`	string	stable The entity ID that was used in the classic entity store. This ID is present in old monitoring data.	`HOST-1234`; `CLOUD_APPLICATION-1234`; `SERVICE-1234`
`name`	string	stable The entity name.	`localhost`; `easyTravel`; `product-catalog`
`type`	string	stable The entity type.	`HOST`; `K8S_POD`; `SERVICE`
`tags`	record	stable A consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, `release` or `name`). The value of each nested field is the tag value from one or multiple contexts. Tags for specific context can be queried via `tags:context` field. Note that rule-based tags do not exist in the new model.	`tags[tag_key-1] = [context_A_tag_val-1, context_B_tag_val-1]`; `tags[tag_key-2] = context_C_tag_val-1`; `tags:context_A[tag_key-1] = context_A_tag_val-1`
`lifetime`	timeframe	stable The lifetime of the entity. `classicField: lifetime`	`{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }`
`references`	record	stable Provides 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.	`{ references[runs_on.host] : [HOST-1234,HOST-5678], references[runs_on.container] : [CONTAINER-1234] }`
`dt.security_context`	string[]	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`	`[]`

Credential Vault Entry fields (i.dt.smartscape.credential_vault_entry.fields)

Attribute	Type	Description	Examples
`owner`	string	experimental The owner of the credential vault entry, which could be an individual or a team responsible for managing the credentials.	`john.doe@company.com`; `platform-team`
`credential.type`	string	experimental The type of the credential vault entry, which indicates the type of credentials stored.	`USERNAME_PASSWORD`; `TOKEN`

Synthetic Browser Monitor

Smartscape node type: BROWSER_MONITOR

Representation of a Synthetic Browser Monitor entity.

Query

Load all BROWSER_MONITOR entities.

smartscapeNodes BROWSER_MONITOR

Base entity fields (i.base_entity)

The following base fields are used for all entities.

Attribute	Type	Description	Examples
`id`	smartscapeId	stable The entity ID.	`HOST-1234`; `K8S_POD-1234`; `SERVICE-1234`
`id_classic`	string	stable The entity ID that was used in the classic entity store. This ID is present in old monitoring data.	`HOST-1234`; `CLOUD_APPLICATION-1234`; `SERVICE-1234`
`name`	string	stable The entity name.	`localhost`; `easyTravel`; `product-catalog`
`type`	string	stable The entity type.	`HOST`; `K8S_POD`; `SERVICE`
`tags`	record	stable A consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, `release` or `name`). The value of each nested field is the tag value from one or multiple contexts. Tags for specific context can be queried via `tags:context` field. Note that rule-based tags do not exist in the new model.	`tags[tag_key-1] = [context_A_tag_val-1, context_B_tag_val-1]`; `tags[tag_key-2] = context_C_tag_val-1`; `tags:context_A[tag_key-1] = context_A_tag_val-1`
`lifetime`	timeframe	stable The lifetime of the entity. `classicField: lifetime`	`{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }`
`references`	record	stable Provides 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.	`{ references[runs_on.host] : [HOST-1234,HOST-5678], references[runs_on.container] : [CONTAINER-1234] }`
`dt.security_context`	string[]	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`	`[]`

Synthetic monitor interface fields (i.synthetic_monitor_interface)

Attribute	Type	Description	Examples
`enabled`	boolean	experimental Indicates whether the synthetic monitor is enabled.	`true`; `false`
`created_by`	string	experimental The identifier of the user or system that created the synthetic monitor.	`dt0s08.self-monitoring-slo-configuration-dev@heimdall.dynatrace.com`; `dt0c01.MT2UKK4NT2RT63KETYPJX7BT`
`last_failed_execution_timestamp`	timestamp	experimental The timestamp of the last failed execution of the synthetic monitor.	`2026-03-24T13:20:11.933000000+01:00`
`last_successful_execution_timestamp`	timestamp	experimental The timestamp of the last successful execution of the synthetic monitor.	`2026-03-24T13:24:08.247000000+01:00`
`last_modification_source`	string	experimental The source of the last modification of the synthetic monitor, such as "system" or "rest".	`system`; `webui`
`last_modified_by`	string	experimental The identifier of the user or system that last modified the synthetic monitor.	`tomasz.lis@dynatrace.com`; `SyntheticModificationHelper`
`last_modification_timestamp`	timestamp	experimental The timestamp of the last modification of the synthetic monitor.	`2026-01-30T11:33:24.770000000+01:00`
`frequency`	long	experimental The frequency of the synthetic monitor executions, expressed in minutes.	`5`; `10`; `15`

Synthetic screenshot interface fields (i.synthetic_screenshot_interface)

Fields specific to synthetic screenshot interfaces.

Attribute	Type	Description	Examples
`screenshot.thumbnail_uri`	string	experimental The URI of the thumbnail image of the synthetic monitor screenshot.	`https://ruxit-synth-screencap-dev.s3.amazonaws.com/uitestautomation/gmg80500/4201424270307144688/101552201328/Action_1_thumb.jpeg`
`screenshot.regular_uri`	string	experimental The URI of the regular image of the synthetic monitor screenshot.	`https://ruxit-synth-screencap-dev.s3.amazonaws.com/uitestautomation/gmg80500/4201424270307144688/101552201328/Action_1_regular.jpeg`
`screenshot.timestamp`	timestamp	experimental The timestamp of when the synthetic monitor screenshot was taken.	`2026-03-24T13:20:11.933000000+01:00`
`screenshot.location`	string	experimental The location where the synthetic monitor screenshot was taken.	`SYNTHETIC_LOCATION-D140F3B85BCCBD1A`
`screenshot.error.thumbnail_uri`	string	experimental The URI of the thumbnail image of the synthetic monitor screenshot taken during an error.	`https://ruxit-synth-screencap-dev.s3.amazonaws.com/uitestautomation/gmg80500/4201424270307144688/101539908374/Action_1_thumb.jpeg`
`screenshot.error.regular_uri`	string	experimental The URI of the regular image of the synthetic monitor screenshot taken during an error.	`https://ruxit-synth-screencap-dev.s3.amazonaws.com/uitestautomation/gmg80500/4201424270307144688/101539908374/Action_1_regular.jpeg`
`screenshot.error.timestamp`	timestamp	experimental The timestamp of when the synthetic monitor screenshot was taken during an error.	`2026-01-30T11:33:24.770000000+01:00`
`screenshot.error.location`	string	experimental The location where the synthetic monitor screenshot was taken during an error.	`SYNTHETIC_LOCATION-D140F3B85BCCBD1A`

Synthetic primary tags fields (i.primary_tags)

The following fields are common for all synthetic events.

Attribute	Type	Description	Examples
`dt.synthetic.monitor.id`	string	experimental The identifier of the monitor.	`HTTP_CHECK-6349B98E1CD87352`
`dt.entity.synthetic_test`	string	resource stable An entity ID of an entity of type SYNTHETIC_TEST. Tags: `entity-id`	`SYNTHETIC_TEST-A140F3B85BCCBD1A`
`dt.entity.http_check`	string	resource stable An entity ID of an entity of type HTTP_CHECK. Tags: `entity-id`	`HTTP_CHECK-A140F3B85BCCBD1A`
`dt.entity.multiprotocol_monitor`	string	resource stable An entity ID of an entity of type MULTIPROTOCOL_MONITOR. Tags: `entity-id`	`MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A`
`dt.entity.external_synthetic_test`	string	resource stable An entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST. Tags: `entity-id`	`EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A`
`monitor.name`	string	experimental The name of the monitor.	`Monitor name`
`dt.synthetic.step.id`	string	experimental The identifier of the monitor step.	`HTTP_CHECK_STEP-5349B98E1CD87352`
`dt.entity.synthetic_test_step`	string	resource stable An entity ID of an entity of type SYNTHETIC_TEST_STEP. Tags: `entity-id`	`SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A`
`dt.entity.http_check_step`	string	resource stable An entity ID of an entity of type HTTP_CHECK_STEP. Tags: `entity-id`	`HTTP_CHECK_STEP-A140F3B85BCCBD1A`
`dt.entity.external_synthetic_test_step`	string	resource stable An entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP. Tags: `entity-id`	`EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A`
`step.name`	string	experimental The name of the step.	`Step name`
`step.sequence_number`	long	experimental The sequence number of the step (numbered from 0).	`0`
`dt.synthetic.monitored_entity_ids`	array	experimental IDs of monitored entities.	`APPLICATION-EA7C4B59F27D43EB`
`primary_tags.__key__`	string	experimental User-defined primary grail tags, `__key__` prefixed with `primary_tags.`. The value is a string.	`tag-value`; `value`
`dt.security_context`	string	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`

Browser Monitor fields (i.dt.smartscape.browser_monitor.fields)

Attribute	Type	Description	Examples
`url`	string	experimental The URL of the synthetic browser monitor.	`https://www.dynatrace.com`; `https://umsaywsjuo.dev.apps.dynatracelabs.com/ui/apps/`
`device_profile`	string	experimental The device profile used for the synthetic browser monitor, such as "Desktop", "Custom", or a specific mobile device profile like "Apple iPhone 12 Pro".	`Desktop`; `Custom`; `Apple iPhone 12 Pro`

Browser Monitor relationship fields

Attribute	Type	Description	Examples
`contains`	record	stable Relationship field that contains all `contains`-relationships as nested fields. Opposite direction: `belongs_to` Relationships: `smartscapeId dt.smartscape.browser_monitor_step`
`is_assigned_to`	record	experimental Defines assignment relationship, where the source is assigned to the destination. Similar to `is_attached_to`, but introduced to preserve naming consistency Examples: A synthetic monitor is assigned to a frontend. Relationships: `smartscapeId dt.smartscape.frontend`	`BROWSER_MONITOR is_assigned_to FRONTEND`
`monitors`	record	experimental Defines monitoring relationship, where the source monitors the destination. Examples: A synthetic monitor monitors a frontend. A synthetic monitor or OneAgent monitors a host. Relationships: `smartscapeId dt.smartscape.frontend`	`BROWSER_MONITOR monitors FRONTEND`; `HTTP_MONITOR monitors SERVICE`; `ONEAGENT monitors HOST`
`runs_on`	record	stable Defines 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: `smartscapeId dt.smartscape.synthetic_location`
`uses`	record	stable Similar to `is_attached_to` but in the opposite direction. Examples: EC2 Instance uses DHCP options, Auto Scaling Group uses EC2 Launch Template Relationships: `smartscapeId dt.smartscape.credential_vault_entry`	`K8S_POD uses K8S_CONFIGMAP`

Synthetic Browser Monitor Step

Smartscape node type: BROWSER_MONITOR_STEP

Representation of a Synthetic Browser Monitor Step entity.

Query

Load all BROWSER_MONITOR_STEP entities.

smartscapeNodes BROWSER_MONITOR_STEP

Base entity fields (i.base_entity)

The following base fields are used for all entities.

Attribute	Type	Description	Examples
`id`	smartscapeId	stable The entity ID.	`HOST-1234`; `K8S_POD-1234`; `SERVICE-1234`
`id_classic`	string	stable The entity ID that was used in the classic entity store. This ID is present in old monitoring data.	`HOST-1234`; `CLOUD_APPLICATION-1234`; `SERVICE-1234`
`name`	string	stable The entity name.	`localhost`; `easyTravel`; `product-catalog`
`type`	string	stable The entity type.	`HOST`; `K8S_POD`; `SERVICE`
`tags`	record	stable A consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, `release` or `name`). The value of each nested field is the tag value from one or multiple contexts. Tags for specific context can be queried via `tags:context` field. Note that rule-based tags do not exist in the new model.	`tags[tag_key-1] = [context_A_tag_val-1, context_B_tag_val-1]`; `tags[tag_key-2] = context_C_tag_val-1`; `tags:context_A[tag_key-1] = context_A_tag_val-1`
`lifetime`	timeframe	stable The lifetime of the entity. `classicField: lifetime`	`{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }`
`references`	record	stable Provides 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.	`{ references[runs_on.host] : [HOST-1234,HOST-5678], references[runs_on.container] : [CONTAINER-1234] }`
`dt.security_context`	string[]	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`	`[]`

Synthetic screenshot interface fields (i.synthetic_screenshot_interface)

Fields specific to synthetic screenshot interfaces.

Attribute	Type	Description	Examples
`screenshot.thumbnail_uri`	string	experimental The URI of the thumbnail image of the synthetic monitor screenshot.	`https://ruxit-synth-screencap-dev.s3.amazonaws.com/uitestautomation/gmg80500/4201424270307144688/101552201328/Action_1_thumb.jpeg`
`screenshot.regular_uri`	string	experimental The URI of the regular image of the synthetic monitor screenshot.	`https://ruxit-synth-screencap-dev.s3.amazonaws.com/uitestautomation/gmg80500/4201424270307144688/101552201328/Action_1_regular.jpeg`
`screenshot.timestamp`	timestamp	experimental The timestamp of when the synthetic monitor screenshot was taken.	`2026-03-24T13:20:11.933000000+01:00`
`screenshot.location`	string	experimental The location where the synthetic monitor screenshot was taken.	`SYNTHETIC_LOCATION-D140F3B85BCCBD1A`
`screenshot.error.thumbnail_uri`	string	experimental The URI of the thumbnail image of the synthetic monitor screenshot taken during an error.	`https://ruxit-synth-screencap-dev.s3.amazonaws.com/uitestautomation/gmg80500/4201424270307144688/101539908374/Action_1_thumb.jpeg`
`screenshot.error.regular_uri`	string	experimental The URI of the regular image of the synthetic monitor screenshot taken during an error.	`https://ruxit-synth-screencap-dev.s3.amazonaws.com/uitestautomation/gmg80500/4201424270307144688/101539908374/Action_1_regular.jpeg`
`screenshot.error.timestamp`	timestamp	experimental The timestamp of when the synthetic monitor screenshot was taken during an error.	`2026-01-30T11:33:24.770000000+01:00`
`screenshot.error.location`	string	experimental The location where the synthetic monitor screenshot was taken during an error.	`SYNTHETIC_LOCATION-D140F3B85BCCBD1A`

Synthetic primary tags fields (i.primary_tags)

The following fields are common for all synthetic events.

Attribute	Type	Description	Examples
`dt.synthetic.monitor.id`	string	experimental The identifier of the monitor.	`HTTP_CHECK-6349B98E1CD87352`
`dt.entity.synthetic_test`	string	resource stable An entity ID of an entity of type SYNTHETIC_TEST. Tags: `entity-id`	`SYNTHETIC_TEST-A140F3B85BCCBD1A`
`dt.entity.http_check`	string	resource stable An entity ID of an entity of type HTTP_CHECK. Tags: `entity-id`	`HTTP_CHECK-A140F3B85BCCBD1A`
`dt.entity.multiprotocol_monitor`	string	resource stable An entity ID of an entity of type MULTIPROTOCOL_MONITOR. Tags: `entity-id`	`MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A`
`dt.entity.external_synthetic_test`	string	resource stable An entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST. Tags: `entity-id`	`EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A`
`monitor.name`	string	experimental The name of the monitor.	`Monitor name`
`dt.synthetic.step.id`	string	experimental The identifier of the monitor step.	`HTTP_CHECK_STEP-5349B98E1CD87352`
`dt.entity.synthetic_test_step`	string	resource stable An entity ID of an entity of type SYNTHETIC_TEST_STEP. Tags: `entity-id`	`SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A`
`dt.entity.http_check_step`	string	resource stable An entity ID of an entity of type HTTP_CHECK_STEP. Tags: `entity-id`	`HTTP_CHECK_STEP-A140F3B85BCCBD1A`
`dt.entity.external_synthetic_test_step`	string	resource stable An entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP. Tags: `entity-id`	`EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A`
`step.name`	string	experimental The name of the step.	`Step name`
`step.sequence_number`	long	experimental The sequence number of the step (numbered from 0).	`0`
`dt.synthetic.monitored_entity_ids`	array	experimental IDs of monitored entities.	`APPLICATION-EA7C4B59F27D43EB`
`primary_tags.__key__`	string	experimental User-defined primary grail tags, `__key__` prefixed with `primary_tags.`. The value is a string.	`tag-value`; `value`
`dt.security_context`	string	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`

Browser Monitor Step fields (i.dt.smartscape.browser_monitor_step.fields)

Attribute	Type	Description	Examples
`step.sequence_number`	long	stable The sequence number of the step within the synthetic browser monitor, indicating the order of execution of the steps.	`42`; `5`; `1`

Browser Monitor Step relationship fields

Attribute	Type	Description	Examples
`belongs_to`	record	stable This 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: `smartscapeId dt.smartscape.browser_monitor`	`SERVICE belongs_to K8S_CLUSTER`; `K8S_POD belongs_to K8S_NAMESPACE`

Synthetic HTTP Monitor

Smartscape node type: HTTP_MONITOR

Representation of a Synthetic HTTP Monitor entity.

Query

Load all HTTP_MONITOR entities.

smartscapeNodes HTTP_MONITOR

Base entity fields (i.base_entity)

The following base fields are used for all entities.

Attribute	Type	Description	Examples
`id`	smartscapeId	stable The entity ID.	`HOST-1234`; `K8S_POD-1234`; `SERVICE-1234`
`id_classic`	string	stable The entity ID that was used in the classic entity store. This ID is present in old monitoring data.	`HOST-1234`; `CLOUD_APPLICATION-1234`; `SERVICE-1234`
`name`	string	stable The entity name.	`localhost`; `easyTravel`; `product-catalog`
`type`	string	stable The entity type.	`HOST`; `K8S_POD`; `SERVICE`
`tags`	record	stable A consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, `release` or `name`). The value of each nested field is the tag value from one or multiple contexts. Tags for specific context can be queried via `tags:context` field. Note that rule-based tags do not exist in the new model.	`tags[tag_key-1] = [context_A_tag_val-1, context_B_tag_val-1]`; `tags[tag_key-2] = context_C_tag_val-1`; `tags:context_A[tag_key-1] = context_A_tag_val-1`
`lifetime`	timeframe	stable The lifetime of the entity. `classicField: lifetime`	`{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }`
`references`	record	stable Provides 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.	`{ references[runs_on.host] : [HOST-1234,HOST-5678], references[runs_on.container] : [CONTAINER-1234] }`
`dt.security_context`	string[]	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`	`[]`

Synthetic monitor interface fields (i.synthetic_monitor_interface)

Attribute	Type	Description	Examples
`enabled`	boolean	experimental Indicates whether the synthetic monitor is enabled.	`true`; `false`
`created_by`	string	experimental The identifier of the user or system that created the synthetic monitor.	`dt0s08.self-monitoring-slo-configuration-dev@heimdall.dynatrace.com`; `dt0c01.MT2UKK4NT2RT63KETYPJX7BT`
`last_failed_execution_timestamp`	timestamp	experimental The timestamp of the last failed execution of the synthetic monitor.	`2026-03-24T13:20:11.933000000+01:00`
`last_successful_execution_timestamp`	timestamp	experimental The timestamp of the last successful execution of the synthetic monitor.	`2026-03-24T13:24:08.247000000+01:00`
`last_modification_source`	string	experimental The source of the last modification of the synthetic monitor, such as "system" or "rest".	`system`; `webui`
`last_modified_by`	string	experimental The identifier of the user or system that last modified the synthetic monitor.	`tomasz.lis@dynatrace.com`; `SyntheticModificationHelper`
`last_modification_timestamp`	timestamp	experimental The timestamp of the last modification of the synthetic monitor.	`2026-01-30T11:33:24.770000000+01:00`
`frequency`	long	experimental The frequency of the synthetic monitor executions, expressed in minutes.	`5`; `10`; `15`

Synthetic primary tags fields (i.primary_tags)

The following fields are common for all synthetic events.

Attribute	Type	Description	Examples
`dt.synthetic.monitor.id`	string	experimental The identifier of the monitor.	`HTTP_CHECK-6349B98E1CD87352`
`dt.entity.synthetic_test`	string	resource stable An entity ID of an entity of type SYNTHETIC_TEST. Tags: `entity-id`	`SYNTHETIC_TEST-A140F3B85BCCBD1A`
`dt.entity.http_check`	string	resource stable An entity ID of an entity of type HTTP_CHECK. Tags: `entity-id`	`HTTP_CHECK-A140F3B85BCCBD1A`
`dt.entity.multiprotocol_monitor`	string	resource stable An entity ID of an entity of type MULTIPROTOCOL_MONITOR. Tags: `entity-id`	`MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A`
`dt.entity.external_synthetic_test`	string	resource stable An entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST. Tags: `entity-id`	`EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A`
`monitor.name`	string	experimental The name of the monitor.	`Monitor name`
`dt.synthetic.step.id`	string	experimental The identifier of the monitor step.	`HTTP_CHECK_STEP-5349B98E1CD87352`
`dt.entity.synthetic_test_step`	string	resource stable An entity ID of an entity of type SYNTHETIC_TEST_STEP. Tags: `entity-id`	`SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A`
`dt.entity.http_check_step`	string	resource stable An entity ID of an entity of type HTTP_CHECK_STEP. Tags: `entity-id`	`HTTP_CHECK_STEP-A140F3B85BCCBD1A`
`dt.entity.external_synthetic_test_step`	string	resource stable An entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP. Tags: `entity-id`	`EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A`
`step.name`	string	experimental The name of the step.	`Step name`
`step.sequence_number`	long	experimental The sequence number of the step (numbered from 0).	`0`
`dt.synthetic.monitored_entity_ids`	array	experimental IDs of monitored entities.	`APPLICATION-EA7C4B59F27D43EB`
`primary_tags.__key__`	string	experimental User-defined primary grail tags, `__key__` prefixed with `primary_tags.`. The value is a string.	`tag-value`; `value`
`dt.security_context`	string	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`

HTTP Monitor fields (i.dt.smartscape.http_monitor.fields)

Attribute	Type	Description	Examples
`http_monitor.type`	string	experimental The type of the synthetic HTTP monitor, such as "HTTP" or "HIGH_RESOURCE", which indicates the resource requirements and capabilities of the monitor.	`HTTP`; `HIGH_RESOURCE`

HTTP Monitor relationship fields

Attribute	Type	Description	Examples
`contains`	record	stable Relationship field that contains all `contains`-relationships as nested fields. Opposite direction: `belongs_to` Relationships: `smartscapeId dt.smartscape.http_monitor_step`
`is_assigned_to`	record	experimental Defines assignment relationship, where the source is assigned to the destination. Similar to `is_attached_to`, but introduced to preserve naming consistency Examples: A synthetic monitor is assigned to a frontend. Relationships: `smartscapeId dt.smartscape.frontend`	`BROWSER_MONITOR is_assigned_to FRONTEND`
`monitors`	record	experimental Defines monitoring relationship, where the source monitors the destination. Examples: A synthetic monitor monitors a frontend. A synthetic monitor or OneAgent monitors a host. Relationships: `smartscapeId dt.smartscape.service`	`BROWSER_MONITOR monitors FRONTEND`; `HTTP_MONITOR monitors SERVICE`; `ONEAGENT monitors HOST`
`runs_on`	record	stable Defines 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: `smartscapeId dt.smartscape.synthetic_location`
`updates`	record	experimental Similar to `uses` but with a stronger connotation where the source actively updates or modifies the target. It implies that the source has some level of control or influence over the target. Examples: A synthetic monitor updates credentials in a credential vault entry. Relationships: `smartscapeId dt.smartscape.credential_vault_entry`	`HTTP_MONITOR updates CREDENTIAL_VAULT_ENTRY`
`uses`	record	stable Similar to `is_attached_to` but in the opposite direction. Examples: EC2 Instance uses DHCP options, Auto Scaling Group uses EC2 Launch Template Relationships: `smartscapeId dt.smartscape.credential_vault_entry`	`K8S_POD uses K8S_CONFIGMAP`

Synthetic HTTP Monitor Step

Smartscape node type: HTTP_MONITOR_STEP

Representation of a Synthetic HTTP Monitor Step entity.

Query

Load all HTTP_MONITOR_STEP entities.

smartscapeNodes HTTP_MONITOR_STEP

Base entity fields (i.base_entity)

The following base fields are used for all entities.

Attribute	Type	Description	Examples
`id`	smartscapeId	stable The entity ID.	`HOST-1234`; `K8S_POD-1234`; `SERVICE-1234`
`id_classic`	string	stable The entity ID that was used in the classic entity store. This ID is present in old monitoring data.	`HOST-1234`; `CLOUD_APPLICATION-1234`; `SERVICE-1234`
`name`	string	stable The entity name.	`localhost`; `easyTravel`; `product-catalog`
`type`	string	stable The entity type.	`HOST`; `K8S_POD`; `SERVICE`
`tags`	record	stable A consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, `release` or `name`). The value of each nested field is the tag value from one or multiple contexts. Tags for specific context can be queried via `tags:context` field. Note that rule-based tags do not exist in the new model.	`tags[tag_key-1] = [context_A_tag_val-1, context_B_tag_val-1]`; `tags[tag_key-2] = context_C_tag_val-1`; `tags:context_A[tag_key-1] = context_A_tag_val-1`
`lifetime`	timeframe	stable The lifetime of the entity. `classicField: lifetime`	`{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }`
`references`	record	stable Provides 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.	`{ references[runs_on.host] : [HOST-1234,HOST-5678], references[runs_on.container] : [CONTAINER-1234] }`
`dt.security_context`	string[]	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`	`[]`

Synthetic primary tags fields (i.primary_tags)

The following fields are common for all synthetic events.

Attribute	Type	Description	Examples
`dt.synthetic.monitor.id`	string	experimental The identifier of the monitor.	`HTTP_CHECK-6349B98E1CD87352`
`dt.entity.synthetic_test`	string	resource stable An entity ID of an entity of type SYNTHETIC_TEST. Tags: `entity-id`	`SYNTHETIC_TEST-A140F3B85BCCBD1A`
`dt.entity.http_check`	string	resource stable An entity ID of an entity of type HTTP_CHECK. Tags: `entity-id`	`HTTP_CHECK-A140F3B85BCCBD1A`
`dt.entity.multiprotocol_monitor`	string	resource stable An entity ID of an entity of type MULTIPROTOCOL_MONITOR. Tags: `entity-id`	`MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A`
`dt.entity.external_synthetic_test`	string	resource stable An entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST. Tags: `entity-id`	`EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A`
`monitor.name`	string	experimental The name of the monitor.	`Monitor name`
`dt.synthetic.step.id`	string	experimental The identifier of the monitor step.	`HTTP_CHECK_STEP-5349B98E1CD87352`
`dt.entity.synthetic_test_step`	string	resource stable An entity ID of an entity of type SYNTHETIC_TEST_STEP. Tags: `entity-id`	`SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A`
`dt.entity.http_check_step`	string	resource stable An entity ID of an entity of type HTTP_CHECK_STEP. Tags: `entity-id`	`HTTP_CHECK_STEP-A140F3B85BCCBD1A`
`dt.entity.external_synthetic_test_step`	string	resource stable An entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP. Tags: `entity-id`	`EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A`
`step.name`	string	experimental The name of the step.	`Step name`
`step.sequence_number`	long	experimental The sequence number of the step (numbered from 0).	`0`
`dt.synthetic.monitored_entity_ids`	array	experimental IDs of monitored entities.	`APPLICATION-EA7C4B59F27D43EB`
`primary_tags.__key__`	string	experimental User-defined primary grail tags, `__key__` prefixed with `primary_tags.`. The value is a string.	`tag-value`; `value`
`dt.security_context`	string	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`

HTTP Monitor Step fields (i.dt.smartscape.http_monitor_step.fields)

Attribute	Type	Description	Examples
`step.url`	string	experimental The URL that is accessed in this step of the synthetic HTTP monitor.	`https://8.8.8.8:443/blah`; `wp.pl`
`step.sequence_number`	long	stable The sequence number of the step within the synthetic browser monitor, indicating the order of execution of the steps.	`42`; `5`; `1`

HTTP Monitor Step relationship fields

Attribute	Type	Description	Examples
`belongs_to`	record	stable This 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: `smartscapeId dt.smartscape.http_monitor`	`SERVICE belongs_to K8S_CLUSTER`; `K8S_POD belongs_to K8S_NAMESPACE`

Synthetic Location

Smartscape node type: SYNTHETIC_LOCATION

Representation of a Synthetic Location entity.

Query

Load all SYNTHETIC_LOCATION entities.

smartscapeNodes SYNTHETIC_LOCATION

Base entity fields (i.base_entity)

The following base fields are used for all entities.

Attribute	Type	Description	Examples
`id`	smartscapeId	stable The entity ID.	`HOST-1234`; `K8S_POD-1234`; `SERVICE-1234`
`id_classic`	string	stable The entity ID that was used in the classic entity store. This ID is present in old monitoring data.	`HOST-1234`; `CLOUD_APPLICATION-1234`; `SERVICE-1234`
`name`	string	stable The entity name.	`localhost`; `easyTravel`; `product-catalog`
`type`	string	stable The entity type.	`HOST`; `K8S_POD`; `SERVICE`
`tags`	record	stable A consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, `release` or `name`). The value of each nested field is the tag value from one or multiple contexts. Tags for specific context can be queried via `tags:context` field. Note that rule-based tags do not exist in the new model.	`tags[tag_key-1] = [context_A_tag_val-1, context_B_tag_val-1]`; `tags[tag_key-2] = context_C_tag_val-1`; `tags:context_A[tag_key-1] = context_A_tag_val-1`
`lifetime`	timeframe	stable The lifetime of the entity. `classicField: lifetime`	`{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }`
`references`	record	stable Provides 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.	`{ references[runs_on.host] : [HOST-1234,HOST-5678], references[runs_on.container] : [CONTAINER-1234] }`
`dt.security_context`	string[]	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`	`[]`

Synthetic location interface fields (i.synthetic_location_interface)

Attribute	Type	Description	Examples
`location_type`	string	experimental The type of the synthetic location, such as "PUBLIC" or "PRIVATE".	`PUBLIC`; `PRIVATE`
`stage`	string	experimental The current stage of the synthetic location.	`COMING_SOON`; `BETA`
`deployment_type`	string	experimental The deployment type of the synthetic location, such as "KUBERNETES".	`STANDARD`; `KUBERNETES`
`modification_timestamp`	timestamp	experimental The timestamp of the last modification of the synthetic location.	`2026-03-25T00:23:33.006000000+01:00`
`browser.autoupdate`	boolean	experimental Indicates whether browser autoupdate is enabled.	`true`; `false`
`cloud.provider`	string	resource stable Name of the cloud provider.	`Amazon EC2`; `Azure`; `Alibaba`; `Google cloud`
`geo.continent.name`	string	resource stable English name of the continent.	`North America`
`geo.country.name`	string	resource stable English name of the country.	`Canada`
`geo.region.name`	string	resource stable English name of the region.	`Quebec`
`geo.city.name`	string	resource stable English name of the city.	`Montreal`
`geo.country.iso_code`	string	resource experimental The two-letter country code. The format complies with ISO 3166-1 alpha-2.	`CA`; `GB`
`geo.region.iso_code`	string	resource experimental ISO 3166-2 region code. In case a country has more levels of subdivisions, the field contains the level of subdivision preferred by Dynatrace.	`CA-QC`; `GB-CAM`
`geo.location.latitude`	double	resource experimental The approximate latitude. The format complies with WGS 84. Tags: `sensitive-user-events`	`45.505918`
`geo.location.longitude`	double	resource experimental The approximate longitude. The format complies with WGS 84. Tags: `sensitive-user-events`	`-73.61483`

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 Platform
`heroku`	Heroku Platform as a Service
`ibm_cloud`	IBM Cloud
`tencent_cloud`	Tencent Cloud

Synthetic Location relationship fields

Synthetic Network Availability Monitor

Smartscape node type: NETWORK_AVAILABILITY_MONITOR

Representation of a Synthetic Network Availability Monitor entity.

Query

Load all NETWORK_AVAILABILITY_MONITOR entities.

smartscapeNodes NETWORK_AVAILABILITY_MONITOR

Base entity fields (i.base_entity)

The following base fields are used for all entities.

Attribute	Type	Description	Examples
`id`	smartscapeId	stable The entity ID.	`HOST-1234`; `K8S_POD-1234`; `SERVICE-1234`
`id_classic`	string	stable The entity ID that was used in the classic entity store. This ID is present in old monitoring data.	`HOST-1234`; `CLOUD_APPLICATION-1234`; `SERVICE-1234`
`name`	string	stable The entity name.	`localhost`; `easyTravel`; `product-catalog`
`type`	string	stable The entity type.	`HOST`; `K8S_POD`; `SERVICE`
`tags`	record	stable A consolidated record that aggregates all tag values originating from different contexts. Each nested field within tags represents a specific key (for example, `release` or `name`). The value of each nested field is the tag value from one or multiple contexts. Tags for specific context can be queried via `tags:context` field. Note that rule-based tags do not exist in the new model.	`tags[tag_key-1] = [context_A_tag_val-1, context_B_tag_val-1]`; `tags[tag_key-2] = context_C_tag_val-1`; `tags:context_A[tag_key-1] = context_A_tag_val-1`
`lifetime`	timeframe	stable The lifetime of the entity. `classicField: lifetime`	`{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }`
`references`	record	stable Provides 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.	`{ references[runs_on.host] : [HOST-1234,HOST-5678], references[runs_on.container] : [CONTAINER-1234] }`
`dt.security_context`	string[]	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`	`[]`

Synthetic monitor interface fields (i.synthetic_monitor_interface)

Attribute	Type	Description	Examples
`enabled`	boolean	experimental Indicates whether the synthetic monitor is enabled.	`true`; `false`
`created_by`	string	experimental The identifier of the user or system that created the synthetic monitor.	`dt0s08.self-monitoring-slo-configuration-dev@heimdall.dynatrace.com`; `dt0c01.MT2UKK4NT2RT63KETYPJX7BT`
`last_failed_execution_timestamp`	timestamp	experimental The timestamp of the last failed execution of the synthetic monitor.	`2026-03-24T13:20:11.933000000+01:00`
`last_successful_execution_timestamp`	timestamp	experimental The timestamp of the last successful execution of the synthetic monitor.	`2026-03-24T13:24:08.247000000+01:00`
`last_modification_source`	string	experimental The source of the last modification of the synthetic monitor, such as "system" or "rest".	`system`; `webui`
`last_modified_by`	string	experimental The identifier of the user or system that last modified the synthetic monitor.	`tomasz.lis@dynatrace.com`; `SyntheticModificationHelper`
`last_modification_timestamp`	timestamp	experimental The timestamp of the last modification of the synthetic monitor.	`2026-01-30T11:33:24.770000000+01:00`
`frequency`	long	experimental The frequency of the synthetic monitor executions, expressed in minutes.	`5`; `10`; `15`

Synthetic primary tags fields (i.primary_tags)

The following fields are common for all synthetic events.

Attribute	Type	Description	Examples
`dt.synthetic.monitor.id`	string	experimental The identifier of the monitor.	`HTTP_CHECK-6349B98E1CD87352`
`dt.entity.synthetic_test`	string	resource stable An entity ID of an entity of type SYNTHETIC_TEST. Tags: `entity-id`	`SYNTHETIC_TEST-A140F3B85BCCBD1A`
`dt.entity.http_check`	string	resource stable An entity ID of an entity of type HTTP_CHECK. Tags: `entity-id`	`HTTP_CHECK-A140F3B85BCCBD1A`
`dt.entity.multiprotocol_monitor`	string	resource stable An entity ID of an entity of type MULTIPROTOCOL_MONITOR. Tags: `entity-id`	`MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A`
`dt.entity.external_synthetic_test`	string	resource stable An entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST. Tags: `entity-id`	`EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A`
`monitor.name`	string	experimental The name of the monitor.	`Monitor name`
`dt.synthetic.step.id`	string	experimental The identifier of the monitor step.	`HTTP_CHECK_STEP-5349B98E1CD87352`
`dt.entity.synthetic_test_step`	string	resource stable An entity ID of an entity of type SYNTHETIC_TEST_STEP. Tags: `entity-id`	`SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A`
`dt.entity.http_check_step`	string	resource stable An entity ID of an entity of type HTTP_CHECK_STEP. Tags: `entity-id`	`HTTP_CHECK_STEP-A140F3B85BCCBD1A`
`dt.entity.external_synthetic_test_step`	string	resource stable An entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP. Tags: `entity-id`	`EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A`
`step.name`	string	experimental The name of the step.	`Step name`
`step.sequence_number`	long	experimental The sequence number of the step (numbered from 0).	`0`
`dt.synthetic.monitored_entity_ids`	array	experimental IDs of monitored entities.	`APPLICATION-EA7C4B59F27D43EB`
`primary_tags.__key__`	string	experimental User-defined primary grail tags, `__key__` prefixed with `primary_tags.`. The value is a string.	`tag-value`; `value`
`dt.security_context`	string	resource stable The security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission model Tags: `permission`

i.dt.smartscape.network_availability_monitor.fields

Attribute	Type	Description	Examples
`network_monitor.type`	string	experimental The type of the synthetic network availability monitor, such as "ICMP" or "TCP", which indicates the protocol used for monitoring network availability.	`ICMP`; `TCP`

Network Availability Monitor relationship fields

Relationships of a network_availability_monitor entity

Attribute	Type	Description	Examples
`monitors`	record	experimental Defines monitoring relationship, where the source monitors the destination. Examples: A synthetic monitor monitors a frontend. A synthetic monitor or OneAgent monitors a host. Relationships: `smartscapeId dt.smartscape.host`	`BROWSER_MONITOR monitors FRONTEND`; `HTTP_MONITOR monitors SERVICE`; `ONEAGENT monitors HOST`
`runs_on`	record	stable Defines 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: `smartscapeId dt.smartscape.synthetic_location`