Try it free

Smartscape - Synthetic

  • Reference
  • Published May 07, 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

AttributeTypeDescriptionExamples

created_by

string

experimentalThe identifier of the user or system that created the synthetic monitor.

dt0s08.self-monitoring-slo-configuration-dev@heimdall.dynatrace.com; dt0c01.MT2UKK4NT2RT63KETYPJX7BT

deleted

boolean

experimentalIndicates whether the synthetic monitor is deleted.

true; false

enabled

boolean

experimentalIndicates whether the synthetic monitor is enabled.

true; false

frequency

long

experimentalThe frequency of the synthetic monitor executions, expressed in minutes.

5; 10; 15

last_failed_execution_timestamp

timestamp

experimentalThe timestamp of the last failed execution of the synthetic monitor.

2026-03-24T13:20:11.933000000+01:00

last_modification_source

string

experimentalThe source of the last modification of the synthetic monitor, such as "system" or "rest".

system; webui

last_modification_timestamp

timestamp

experimentalThe timestamp of the last modification of the synthetic monitor.

2026-01-30T11:33:24.770000000+01:00

last_modified_by

string

experimentalThe identifier of the user or system that last modified the synthetic monitor.

tomasz.lis@dynatrace.com; SyntheticModificationHelper

last_successful_execution_timestamp

timestamp

experimentalThe 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 typeClassic modelDescriptionModel

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

The following base fields are used for all entities.

AttributeTypeDescriptionExamples

id

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.

<type>-017198AD253CBD63

id_classic

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 id field instead, which is the Smartscape ID.

<type>-017198AD253CBD63

name

string

stableThe entity name.

localhost; easyTravel; product-catalog

type

string

stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity.

TYPE_A

tags

record

stableA 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

stableThe lifetime of the entity. This is a record with two nested fields: start and end, which represent the time when the entity was first and last observed, respectively. Each time an entity is updated, the end time is updated to the current time.

{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }

references

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.

{ references[runs_on.host] : [HOST-C251A1173C2B4B39,HOST-0E9038C7C4409D69], references[runs_on.container] : [CONTAINER-68A08967EF4F675B] }

dt.security_context

string[]

resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: permission

[]

Credential Vault Entry fields

AttributeTypeDescriptionExamples

owner

string

experimentalThe 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

experimentalThe 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

The following base fields are used for all entities.

AttributeTypeDescriptionExamples

id

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.

<type>-017198AD253CBD63

id_classic

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 id field instead, which is the Smartscape ID.

<type>-017198AD253CBD63

name

string

stableThe entity name.

localhost; easyTravel; product-catalog

type

string

stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity.

TYPE_A

tags

record

stableA 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

stableThe lifetime of the entity. This is a record with two nested fields: start and end, which represent the time when the entity was first and last observed, respectively. Each time an entity is updated, the end time is updated to the current time.

{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }

references

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.

{ references[runs_on.host] : [HOST-C251A1173C2B4B39,HOST-0E9038C7C4409D69], references[runs_on.container] : [CONTAINER-68A08967EF4F675B] }

dt.security_context

string[]

resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: permission

[]

Synthetic monitor interface fields

AttributeTypeDescriptionExamples

enabled

boolean

experimentalIndicates whether the synthetic monitor is enabled.

true; false

created_by

string

experimentalThe 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

experimentalThe timestamp of the last failed execution of the synthetic monitor.

2026-03-24T13:20:11.933000000+01:00

last_successful_execution_timestamp

timestamp

experimentalThe timestamp of the last successful execution of the synthetic monitor.

2026-03-24T13:24:08.247000000+01:00

last_modification_source

string

experimentalThe source of the last modification of the synthetic monitor, such as "system" or "rest".

system; webui

last_modified_by

string

experimentalThe identifier of the user or system that last modified the synthetic monitor.

tomasz.lis@dynatrace.com; SyntheticModificationHelper

last_modification_timestamp

timestamp

experimentalThe timestamp of the last modification of the synthetic monitor.

2026-01-30T11:33:24.770000000+01:00

frequency

long

experimentalThe frequency of the synthetic monitor executions, expressed in minutes.

5; 10; 15

deleted

boolean

experimentalIndicates whether the synthetic monitor is deleted.

true; false

Synthetic screenshot interface fields

Fields specific to synthetic screenshot interfaces.

AttributeTypeDescriptionExamples

screenshot.thumbnail_uri

string

experimentalThe 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

experimentalThe 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

experimentalThe timestamp of when the synthetic monitor screenshot was taken.

2026-03-24T13:20:11.933000000+01:00

screenshot.location

string

experimentalThe location where the synthetic monitor screenshot was taken.

SYNTHETIC_LOCATION-D140F3B85BCCBD1A

screenshot.error.thumbnail_uri

string

experimentalThe 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

experimentalThe 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

experimentalThe timestamp of when the synthetic monitor screenshot was taken during an error.

2026-01-30T11:33:24.770000000+01:00

screenshot.error.location

string

experimentalThe location where the synthetic monitor screenshot was taken during an error.

SYNTHETIC_LOCATION-D140F3B85BCCBD1A

Synthetic primary tags fields

The following fields are common for all synthetic events.

AttributeTypeDescriptionExamples

dt.synthetic.monitor.id

string

experimentalThe identifier of the monitor.

HTTP_CHECK-6349B98E1CD87352

dt.entity.synthetic_test

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST.Tags: entity-id

SYNTHETIC_TEST-A140F3B85BCCBD1A

dt.entity.http_check

string

resource stableAn entity ID of an entity of type HTTP_CHECK.Tags: entity-id

HTTP_CHECK-A140F3B85BCCBD1A

dt.entity.multiprotocol_monitor

string

resource stableAn entity ID of an entity of type MULTIPROTOCOL_MONITOR.Tags: entity-id

MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A

dt.entity.external_synthetic_test

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A

monitor.name

string

experimentalThe name of the monitor.

Monitor name

dt.synthetic.step.id

string

experimentalThe identifier of the monitor step.

HTTP_CHECK_STEP-5349B98E1CD87352

dt.entity.synthetic_test_step

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST_STEP.Tags: entity-id

SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

dt.entity.http_check_step

string

resource stableAn 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 stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

step.name

string

experimentalThe name of the step.

Step name

step.sequence_number

long

experimentalThe sequence number of the step (numbered from 0).

0

dt.synthetic.monitored_entity_ids

array

experimentalIDs of monitored entities.

APPLICATION-EA7C4B59F27D43EB

primary_tags.__key__

string

experimentalUser-defined primary grail tags, __key__ prefixed with primary_tags.. The value is a string.

tag-value; value

dt.security_context

string

resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: permission

Browser Monitor fields

AttributeTypeDescriptionExamples

url

string

experimentalThe URL of the synthetic browser monitor.

https://www.dynatrace.com; https://umsaywsjuo.dev.apps.dynatracelabs.com/ui/apps/

device_profile

string

experimentalThe 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

AttributeTypeDescriptionExamples

contains

record

stableRelationship field that contains all contains-relationships as nested fields.Opposite direction: belongs_toRelationships:smartscapeId dt.smartscape.browser_monitor_step

is_assigned_to

record

experimentalDefines 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

experimentalDefines 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

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:smartscapeId dt.smartscape.synthetic_location

uses

record

stableSimilar to is_attached_to but in the opposite direction. Examples: EC2 Instance uses DHCP options, Auto Scaling Group uses EC2 Launch TemplateRelationships: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

The following base fields are used for all entities.

AttributeTypeDescriptionExamples

id

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.

<type>-017198AD253CBD63

id_classic

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 id field instead, which is the Smartscape ID.

<type>-017198AD253CBD63

name

string

stableThe entity name.

localhost; easyTravel; product-catalog

type

string

stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity.

TYPE_A

tags

record

stableA 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

stableThe lifetime of the entity. This is a record with two nested fields: start and end, which represent the time when the entity was first and last observed, respectively. Each time an entity is updated, the end time is updated to the current time.

{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }

references

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.

{ references[runs_on.host] : [HOST-C251A1173C2B4B39,HOST-0E9038C7C4409D69], references[runs_on.container] : [CONTAINER-68A08967EF4F675B] }

dt.security_context

string[]

resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: permission

[]

Synthetic screenshot interface fields

Fields specific to synthetic screenshot interfaces.

AttributeTypeDescriptionExamples

screenshot.thumbnail_uri

string

experimentalThe 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

experimentalThe 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

experimentalThe timestamp of when the synthetic monitor screenshot was taken.

2026-03-24T13:20:11.933000000+01:00

screenshot.location

string

experimentalThe location where the synthetic monitor screenshot was taken.

SYNTHETIC_LOCATION-D140F3B85BCCBD1A

screenshot.error.thumbnail_uri

string

experimentalThe 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

experimentalThe 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

experimentalThe timestamp of when the synthetic monitor screenshot was taken during an error.

2026-01-30T11:33:24.770000000+01:00

screenshot.error.location

string

experimentalThe location where the synthetic monitor screenshot was taken during an error.

SYNTHETIC_LOCATION-D140F3B85BCCBD1A

Synthetic primary tags fields

The following fields are common for all synthetic events.

AttributeTypeDescriptionExamples

dt.synthetic.monitor.id

string

experimentalThe identifier of the monitor.

HTTP_CHECK-6349B98E1CD87352

dt.entity.synthetic_test

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST.Tags: entity-id

SYNTHETIC_TEST-A140F3B85BCCBD1A

dt.entity.http_check

string

resource stableAn entity ID of an entity of type HTTP_CHECK.Tags: entity-id

HTTP_CHECK-A140F3B85BCCBD1A

dt.entity.multiprotocol_monitor

string

resource stableAn entity ID of an entity of type MULTIPROTOCOL_MONITOR.Tags: entity-id

MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A

dt.entity.external_synthetic_test

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A

monitor.name

string

experimentalThe name of the monitor.

Monitor name

dt.synthetic.step.id

string

experimentalThe identifier of the monitor step.

HTTP_CHECK_STEP-5349B98E1CD87352

dt.entity.synthetic_test_step

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST_STEP.Tags: entity-id

SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

dt.entity.http_check_step

string

resource stableAn 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 stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

step.name

string

experimentalThe name of the step.

Step name

step.sequence_number

long

experimentalThe sequence number of the step (numbered from 0).

0

dt.synthetic.monitored_entity_ids

array

experimentalIDs of monitored entities.

APPLICATION-EA7C4B59F27D43EB

primary_tags.__key__

string

experimentalUser-defined primary grail tags, __key__ prefixed with primary_tags.. The value is a string.

tag-value; value

dt.security_context

string

resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: permission

Browser Monitor Step fields

AttributeTypeDescriptionExamples

step.sequence_number

long

stableThe 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

AttributeTypeDescriptionExamples

belongs_to

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: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

The following base fields are used for all entities.

AttributeTypeDescriptionExamples

id

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.

<type>-017198AD253CBD63

id_classic

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 id field instead, which is the Smartscape ID.

<type>-017198AD253CBD63

name

string

stableThe entity name.

localhost; easyTravel; product-catalog

type

string

stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity.

TYPE_A

tags

record

stableA 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

stableThe lifetime of the entity. This is a record with two nested fields: start and end, which represent the time when the entity was first and last observed, respectively. Each time an entity is updated, the end time is updated to the current time.

{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }

references

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.

{ references[runs_on.host] : [HOST-C251A1173C2B4B39,HOST-0E9038C7C4409D69], references[runs_on.container] : [CONTAINER-68A08967EF4F675B] }

dt.security_context

string[]

resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: permission

[]

Synthetic monitor interface fields

AttributeTypeDescriptionExamples

enabled

boolean

experimentalIndicates whether the synthetic monitor is enabled.

true; false

created_by

string

experimentalThe 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

experimentalThe timestamp of the last failed execution of the synthetic monitor.

2026-03-24T13:20:11.933000000+01:00

last_successful_execution_timestamp

timestamp

experimentalThe timestamp of the last successful execution of the synthetic monitor.

2026-03-24T13:24:08.247000000+01:00

last_modification_source

string

experimentalThe source of the last modification of the synthetic monitor, such as "system" or "rest".

system; webui

last_modified_by

string

experimentalThe identifier of the user or system that last modified the synthetic monitor.

tomasz.lis@dynatrace.com; SyntheticModificationHelper

last_modification_timestamp

timestamp

experimentalThe timestamp of the last modification of the synthetic monitor.

2026-01-30T11:33:24.770000000+01:00

frequency

long

experimentalThe frequency of the synthetic monitor executions, expressed in minutes.

5; 10; 15

deleted

boolean

experimentalIndicates whether the synthetic monitor is deleted.

true; false

Synthetic primary tags fields

The following fields are common for all synthetic events.

AttributeTypeDescriptionExamples

dt.synthetic.monitor.id

string

experimentalThe identifier of the monitor.

HTTP_CHECK-6349B98E1CD87352

dt.entity.synthetic_test

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST.Tags: entity-id

SYNTHETIC_TEST-A140F3B85BCCBD1A

dt.entity.http_check

string

resource stableAn entity ID of an entity of type HTTP_CHECK.Tags: entity-id

HTTP_CHECK-A140F3B85BCCBD1A

dt.entity.multiprotocol_monitor

string

resource stableAn entity ID of an entity of type MULTIPROTOCOL_MONITOR.Tags: entity-id

MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A

dt.entity.external_synthetic_test

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A

monitor.name

string

experimentalThe name of the monitor.

Monitor name

dt.synthetic.step.id

string

experimentalThe identifier of the monitor step.

HTTP_CHECK_STEP-5349B98E1CD87352

dt.entity.synthetic_test_step

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST_STEP.Tags: entity-id

SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

dt.entity.http_check_step

string

resource stableAn 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 stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

step.name

string

experimentalThe name of the step.

Step name

step.sequence_number

long

experimentalThe sequence number of the step (numbered from 0).

0

dt.synthetic.monitored_entity_ids

array

experimentalIDs of monitored entities.

APPLICATION-EA7C4B59F27D43EB

primary_tags.__key__

string

experimentalUser-defined primary grail tags, __key__ prefixed with primary_tags.. The value is a string.

tag-value; value

dt.security_context

string

resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: permission

HTTP Monitor fields

AttributeTypeDescriptionExamples

http_monitor.type

string

experimentalThe 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

AttributeTypeDescriptionExamples

contains

record

stableRelationship field that contains all contains-relationships as nested fields.Opposite direction: belongs_toRelationships:smartscapeId dt.smartscape.http_monitor_step

is_assigned_to

record

experimentalDefines 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

experimentalDefines 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

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:smartscapeId dt.smartscape.synthetic_location

updates

record

experimentalSimilar 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

stableSimilar to is_attached_to but in the opposite direction. Examples: EC2 Instance uses DHCP options, Auto Scaling Group uses EC2 Launch TemplateRelationships: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

The following base fields are used for all entities.

AttributeTypeDescriptionExamples

id

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.

<type>-017198AD253CBD63

id_classic

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 id field instead, which is the Smartscape ID.

<type>-017198AD253CBD63

name

string

stableThe entity name.

localhost; easyTravel; product-catalog

type

string

stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity.

TYPE_A

tags

record

stableA 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

stableThe lifetime of the entity. This is a record with two nested fields: start and end, which represent the time when the entity was first and last observed, respectively. Each time an entity is updated, the end time is updated to the current time.

{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }

references

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.

{ references[runs_on.host] : [HOST-C251A1173C2B4B39,HOST-0E9038C7C4409D69], references[runs_on.container] : [CONTAINER-68A08967EF4F675B] }

dt.security_context

string[]

resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: permission

[]

Synthetic primary tags fields

The following fields are common for all synthetic events.

AttributeTypeDescriptionExamples

dt.synthetic.monitor.id

string

experimentalThe identifier of the monitor.

HTTP_CHECK-6349B98E1CD87352

dt.entity.synthetic_test

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST.Tags: entity-id

SYNTHETIC_TEST-A140F3B85BCCBD1A

dt.entity.http_check

string

resource stableAn entity ID of an entity of type HTTP_CHECK.Tags: entity-id

HTTP_CHECK-A140F3B85BCCBD1A

dt.entity.multiprotocol_monitor

string

resource stableAn entity ID of an entity of type MULTIPROTOCOL_MONITOR.Tags: entity-id

MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A

dt.entity.external_synthetic_test

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A

monitor.name

string

experimentalThe name of the monitor.

Monitor name

dt.synthetic.step.id

string

experimentalThe identifier of the monitor step.

HTTP_CHECK_STEP-5349B98E1CD87352

dt.entity.synthetic_test_step

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST_STEP.Tags: entity-id

SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

dt.entity.http_check_step

string

resource stableAn 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 stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

step.name

string

experimentalThe name of the step.

Step name

step.sequence_number

long

experimentalThe sequence number of the step (numbered from 0).

0

dt.synthetic.monitored_entity_ids

array

experimentalIDs of monitored entities.

APPLICATION-EA7C4B59F27D43EB

primary_tags.__key__

string

experimentalUser-defined primary grail tags, __key__ prefixed with primary_tags.. The value is a string.

tag-value; value

dt.security_context

string

resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: permission

HTTP Monitor Step fields

AttributeTypeDescriptionExamples

step.url

string

experimentalThe 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

stableThe 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

AttributeTypeDescriptionExamples

belongs_to

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: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

The following base fields are used for all entities.

AttributeTypeDescriptionExamples

id

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.

<type>-017198AD253CBD63

id_classic

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 id field instead, which is the Smartscape ID.

<type>-017198AD253CBD63

name

string

stableThe entity name.

localhost; easyTravel; product-catalog

type

string

stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity.

TYPE_A

tags

record

stableA 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

stableThe lifetime of the entity. This is a record with two nested fields: start and end, which represent the time when the entity was first and last observed, respectively. Each time an entity is updated, the end time is updated to the current time.

{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }

references

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.

{ references[runs_on.host] : [HOST-C251A1173C2B4B39,HOST-0E9038C7C4409D69], references[runs_on.container] : [CONTAINER-68A08967EF4F675B] }

dt.security_context

string[]

resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: permission

[]

Synthetic location interface fields

AttributeTypeDescriptionExamples

location_type

string

experimentalThe type of the synthetic location, such as "PUBLIC" or "PRIVATE".

PUBLIC; PRIVATE

stage

string

experimentalThe current stage of the synthetic location.

COMING_SOON; BETA

deployment_type

string

experimentalThe deployment type of the synthetic location, such as "KUBERNETES".

STANDARD; KUBERNETES

modification_timestamp

timestamp

experimentalThe timestamp of the last modification of the synthetic location.

2026-03-25T00:23:33.006000000+01:00

browser.autoupdate

boolean

experimentalIndicates whether browser autoupdate is enabled.

true; false

cloud.provider

string

resource stableName of the cloud provider.

Amazon EC2; Azure; Alibaba; Google cloud

geo.continent.name

string

resource stableEnglish name of the continent.

North America

geo.country.name

string

resource stableEnglish name of the country.

Canada

geo.region.name

string

resource stableEnglish name of the region.

Quebec

geo.city.name

string

resource stableEnglish name of the city.

Montreal

geo.country.iso_code

string

resource experimentalThe two-letter country code. The format complies with ISO 3166-1 alpha-2.

CA; GB

geo.region.iso_code

string

resource experimentalISO 3166-2 region code. In case a country has multiple subdivision categories, the field contains the subdivision category preferred by Dynatrace.

CA-QC; GB-CAM

geo.location.latitude

double

resource experimentalThe approximate latitude. The format complies with WGS 84.Tags: sensitive-user-events

45.505918

geo.location.longitude

double

resource experimentalThe 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.

ValueDescription

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

The following base fields are used for all entities.

AttributeTypeDescriptionExamples

id

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.

<type>-017198AD253CBD63

id_classic

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 id field instead, which is the Smartscape ID.

<type>-017198AD253CBD63

name

string

stableThe entity name.

localhost; easyTravel; product-catalog

type

string

stableThe entity type. UPPER_SNAKE_CASE string that represents the type of the entity.

TYPE_A

tags

record

stableA 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

stableThe lifetime of the entity. This is a record with two nested fields: start and end, which represent the time when the entity was first and last observed, respectively. Each time an entity is updated, the end time is updated to the current time.

{ start: 2022-07-06T13:36:00.808Z, end: 2024-04-11T06:56:01.204Z }

references

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.

{ references[runs_on.host] : [HOST-C251A1173C2B4B39,HOST-0E9038C7C4409D69], references[runs_on.container] : [CONTAINER-68A08967EF4F675B] }

dt.security_context

string[]

resource stableThe security contexts associated with the entity. For Smartscape entities, this field is always an array.Tags: permission

[]

Synthetic monitor interface fields

AttributeTypeDescriptionExamples

enabled

boolean

experimentalIndicates whether the synthetic monitor is enabled.

true; false

created_by

string

experimentalThe 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

experimentalThe timestamp of the last failed execution of the synthetic monitor.

2026-03-24T13:20:11.933000000+01:00

last_successful_execution_timestamp

timestamp

experimentalThe timestamp of the last successful execution of the synthetic monitor.

2026-03-24T13:24:08.247000000+01:00

last_modification_source

string

experimentalThe source of the last modification of the synthetic monitor, such as "system" or "rest".

system; webui

last_modified_by

string

experimentalThe identifier of the user or system that last modified the synthetic monitor.

tomasz.lis@dynatrace.com; SyntheticModificationHelper

last_modification_timestamp

timestamp

experimentalThe timestamp of the last modification of the synthetic monitor.

2026-01-30T11:33:24.770000000+01:00

frequency

long

experimentalThe frequency of the synthetic monitor executions, expressed in minutes.

5; 10; 15

deleted

boolean

experimentalIndicates whether the synthetic monitor is deleted.

true; false

Synthetic primary tags fields

The following fields are common for all synthetic events.

AttributeTypeDescriptionExamples

dt.synthetic.monitor.id

string

experimentalThe identifier of the monitor.

HTTP_CHECK-6349B98E1CD87352

dt.entity.synthetic_test

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST.Tags: entity-id

SYNTHETIC_TEST-A140F3B85BCCBD1A

dt.entity.http_check

string

resource stableAn entity ID of an entity of type HTTP_CHECK.Tags: entity-id

HTTP_CHECK-A140F3B85BCCBD1A

dt.entity.multiprotocol_monitor

string

resource stableAn entity ID of an entity of type MULTIPROTOCOL_MONITOR.Tags: entity-id

MULTIPROTOCOL_MONITOR-A140F3B85BCCBD1A

dt.entity.external_synthetic_test

string

resource stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST-A140F3B85BCCBD1A

monitor.name

string

experimentalThe name of the monitor.

Monitor name

dt.synthetic.step.id

string

experimentalThe identifier of the monitor step.

HTTP_CHECK_STEP-5349B98E1CD87352

dt.entity.synthetic_test_step

string

resource stableAn entity ID of an entity of type SYNTHETIC_TEST_STEP.Tags: entity-id

SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

dt.entity.http_check_step

string

resource stableAn 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 stableAn entity ID of an entity of type EXTERNAL_SYNTHETIC_TEST_STEP.Tags: entity-id

EXTERNAL_SYNTHETIC_TEST_STEP-A140F3B85BCCBD1A

step.name

string

experimentalThe name of the step.

Step name

step.sequence_number

long

experimentalThe sequence number of the step (numbered from 0).

0

dt.synthetic.monitored_entity_ids

array

experimentalIDs of monitored entities.

APPLICATION-EA7C4B59F27D43EB

primary_tags.__key__

string

experimentalUser-defined primary grail tags, __key__ prefixed with primary_tags.. The value is a string.

tag-value; value

dt.security_context

string

resource stableThe security context is used in access permissions to limit the visibility. Learn more about the Dynatrace permission modelTags: permission

Synthetic network availability monitor fields

AttributeTypeDescriptionExamples

network_monitor.type

string

experimentalThe 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

AttributeTypeDescriptionExamples

monitors

record

experimentalDefines 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

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:smartscapeId dt.smartscape.synthetic_location