Try it free

NAM monitor metrics in Classic

  • Dynatrace Classic
  • Explanation
  • 12-min read

Metrics and dimensions

Dimensions (all network availability monitors)

NameTypeDescriptionExample value

dt.entity.multiprotocol_monitor

string

Monitor ID (monitored entity ID)

MULTIPROTOCOL_MONITOR-3F6C9D500287BBAF

dt.entity.synthetic_location

string

Synthetic location ID (monitored entity ID)

SYNTHETIC_LOCATION-A4F834D72840EFC1

dt.entity.host

string

If available, monitored entity ID for target

HOST-024C103F7F86A290

dt.maintenance_window_ids

array

UUIDs of maintenance windows

c715d677-eb1b-3e1b-8dbc-db06cad5b8eb

dt.synthetic.monitored_entity_ids

array

IDs of monitored entities

APPLICATION-EA7C4B59F27D43EB

dt.security_context

string

The security context is used in access permissions to limit the visibility

mySecurityContext

step.id

numeric

Step sequential ID

1

request.id

numeric

Request sequential ID

2

request.type

string

Type of request

icmp, tcp

request.target_address

string

Address of target entity

54.171.216.19

result.state

string

Result state of monitor execution

SUCCESS, FAIL

result.status.message

string

Execution status

HEALTHY, CONSTRAINT_VIOLATED

result.status.code

numeric

Numeric representation of the execution status

0, 1401

interpolated

boolean

Information whether monitor availability was interpolated

false

multi_protocol.step.id

numeric

Step sequential ID (deprecated, use step.id)

1

multi_protocol.request.id

numeric

Request sequential ID (deprecated, use request.id)

2

multi_protocol.request.type

string

Type of request (deprecated, use request.type)

icmp, tcp

multi_protocol.request.target_address

string

Address of target entity (deprecated, use request.target_address)

54.171.216.19

multi_protocol.result.state

string

Result state of monitor execution (deprecated, use result.state)

SUCCESS

multi_protocol.result.status

string

Execution status (deprecated, use result.status.message)

HEALTHY, CONSTRAINT_VIOLATED

multi_protocol.result.status.code

numeric

Numeric representation of the execution status (deprecated, use result.status.code)

0, 1401

Monitor metrics (all network availability monitors)

NameTypeDimensionsDescription

builtin:synthetic.multiProtocol.availability

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.synthetic.monitored_entity_ids``dt.security_context``interpolated

Availability calculated based on the execution status of visits- 100% for code=0: HEALTHY, SCRIPT_FINISH, SKIPPED- 0% for error status codes such as 1401 - CONSTRAINT_VIOLATED

builtin:synthetic.multiProtocol.executionTime

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.synthetic.monitored_entity_ids``dt.security_context

Duration between start and end time of visit execution (in milliseconds)Metric available only if visit execution took place; both start time and end time must be available.

builtin:synthetic.multiProtocol.executions

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.synthetic.monitored_entity_ids``dt.security_context``dt.maintenance_window_ids``result.state``result.status.code``result.status.message``multi_protocol.result.state (deprecated, use result.state)multi_protocol.result.status.code(deprecated, use result.status.code)multi_protocol.result.status (deprecated, use result.status.message)

Number of monitor executions in time

builtin:synthetic.multiProtocol.successRate

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.synthetic.monitored_entity_ids``dt.security_context

Ratio of executed steps that didn't fail (successes + skips) to all executed stepsWe take into account steps that were actually executed rather than steps intended to be executed. For example, with 2 successful steps, 1 failed step, and 8 not started, the ratio is 2/3, or 66.67%.

Step metrics (all network availability monitors)

NameTypeDimensionsDescription

builtin:synthetic.multiProtocol.step.availability

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.synthetic.monitored_entity_ids``dt.security_context``step.id``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.type (deprecated, use request.type)

Availability calculated based on the execution status of steps- 100% for code=0: HEALTHY, SCRIPT_FINISH, SKIPPED- 0% for error status codes such as 1401 - CONSTRAINT_VIOLATED

builtin:synthetic.multiProtocol.step.executionTime

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.synthetic.monitored_entity_ids``dt.security_context``step.id``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.type (deprecated, use request.type)

Duration between start and end time of step execution (in milliseconds)Metric available only if step execution took place, with a well-defined end time; therefore, it's not available for skipped steps.

builtin:synthetic.multiProtocol.step.executions

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.synthetic.monitored_entity_ids``dt.security_context``step.id``request.type``result.state``result.status.code``result.status.message``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.type (deprecated, use request.type)multi_protocol.result.state (deprecated, use result.state)multi_protocol.result.status (deprecated, use result.status.message)multi_protocol.result.status.code(deprecated, use result.status.code)

Number of step executions in time

builtin:synthetic.multiProtocol.step.successRate

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.synthetic.monitored_entity_ids``dt.security_context``step.id``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.type (deprecated, use request.type)

Ratio of executed requests that didn't fail to all executed requests.If a step doesn't have executed requests (because nothing matches its definition in a monitor configuration), we return the value 100%.For example, with 2 successful requests and 1 failed request, the ratio is 2/3, or 66.67%.

Request metrics (all network availability monitors)

NameTypeDimensionsDescription

builtin:synthetic.multiProtocol.request.availability

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.entity.host (only for monitors with filter defined)dt.synthetic.monitored_entity_ids``dt.security_context``step.id``request.id``request.target.address``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.id (deprecated, use request.id)multi_protocol.request.target_address (deprecated, use request.target.address)multi_protocol.request.type (deprecated, use request.type)

Availability calculated based on the execution status of requests- 100% for code=0: HEALTHY, SCRIPT_FINISH, SKIPPED- 0% for error status codes such as 1401 - CONSTRAINT_VIOLATED

builtin:synthetic.multiProtocol.request.executions

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.entity.host (only for monitors with filter defined)dt.synthetic.monitored_entity_ids``dt.security_context``step.id``request.id``request.target.address``request.type``result.state``result.status.code``result.status.message``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.id (deprecated, use request.id)multi_protocol.request.target_address (deprecated, use request.target.address)multi_protocol.request.type (deprecated, use request.type)multi_protocol.result.state (deprecated, use result.state)multi_protocol.result.status (deprecated, use result.status.message)multi_protocol.result.status.code(deprecated, use result.status.code)

Number of request executions in time

ICMP monitor metrics

NameTypeDimensionsDescription

builtin:synthetic.multiProtocol.icmp.successRate

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.entity.host (only for monitors with filter defined)dt.security_context``step.id``request.id``request.target.address``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.id (deprecated, use request.id)multi_protocol.request.target_address (deprecated, use request.target.address)multi_protocol.request.type (deprecated, use request.type)

Ratio of received packets to sent packetsDoesn't take into account the configured number of packets to be sent.For example, out of 10 packets to be sent, if 5 were sent and 4 were received, the ratio is 4/5, or 80.00%.

builtin:synthetic.multiProtocol.icmp.packetsSent

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.entity.host (only for monitors with filter defined)dt.security_context``step.id``request.id``request.target.address``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.id (deprecated, use request.id)multi_protocol.request.target_address (deprecated, use request.target.address)multi_protocol.request.type (deprecated, use request.type)

Total number of packets sent

builtin:synthetic.multiProtocol.icmp.packetsReceived

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.entity.host (only for monitors with filter defined)dt.security_context``step.id``request.id``request.target.address``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.id (deprecated, use request.id)multi_protocol.request.target_address (deprecated, use request.target.address)multi_protocol.request.type (deprecated, use request.type)

Number of packets that were returned successfully

builtin:synthetic.multiProtocol.icmp.roundTripTime

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.entity.host (only for monitors with filter defined)dt.security_context``step.id``request.id``request.target.address``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.id (deprecated, use request.id)multi_protocol.request.target_address (deprecated, use request.target.address)multi_protocol.request.type (deprecated, use request.type)

Round-Trip Time for received packets

builtin:synthetic.multiProtocol.icmp.requestExecutionTime

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.entity.host (only for monitors with filter defined)dt.security_context``step.id``request.id``request.target.address``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.id (deprecated, use request.id)multi_protocol.request.target_address (deprecated, use request.target.address)multi_protocol.request.type (deprecated, use request.type)

Duration between start and end time of request handling (in milliseconds)This metric is always provided, even if actual request execution did not take place (for example, because of exceptions or timeouts).Diagnostic metric—allows for validation of external ping process execution time.

TCP monitor dimensions

NameTypeDescriptionExample value

request.tcp_port_number

string

TCP request port number, as provided in monitor configuration

665

multi_protocol.request.tcp_port_number

string

TCP request port number, as provided in monitor configuration (deprecated, use request.tcp_port_number)

665

TCP monitor metrics

NameTypeDimensionsDescription

builtin:synthetic.multiProtocol.tcp.connectionTime

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.entity.host (only for monitors with filter defined)dt.security_context``step.id``request.id``request.target.address``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.id (deprecated, use request.id)multi_protocol.request.target_address (deprecated, use request.target.address)multi_protocol.request.type (deprecated, use request.type)request.tcp_port_number``multi_protocol.request.tcp_port_number (deprecated, use: request.tcp_port_number)

Duration between start time (socket creation and connection) and end time (when confection is successfully established) in millisecondsMetric available only if request execution took place (with no exceptions or timeouts), with a well-defined end time

DNS monitor dimensions

NameTypeDescriptionExample value

request.dns_record_type

string

DNS record type to be queried by request, as provided in configuration

A, AAAA, CNAME

multi_protocol.request.dns_record_type

string

DNS record type to be queried by request, as provided in configuration (deprecated, use request.dns_record_type)

A, AAAA, CNAME

DNS monitor metrics

NameTypeDimensionsDescription

builtin:synthetic.multiProtocol.dns.resolutionTime

numeric

dt.entity.multiprotocol_monitor``dt.entity.synthetic_location``dt.entity.host (only for monitors with filter defined)dt.security_context``step.id``request.id``request.target.address``request.type``multi_protocol.step.id (deprecated, use step.id)multi_protocol.request.id (deprecated, use request.id)multi_protocol.request.target_address (deprecated, use request.target.address)multi_protocol.request.type (deprecated, use request.type)request.dns_record_type``multi_protocol.request.dns_record_type (deprecated, use: request.dns_record_type)

Duration between start and end time of the request to the DNS server, in millisecondsMetric available only if request execution took place (with no exceptions or timeouts), with a well-defined end time

Execution statuses

All network availability monitors

Code / messageExampleDescription

0 HEALTHY

-

All is well.

-1 UNEXPECTED_ERROR

Resource saturation

Unexpected problem that's usually related to monitor's execution components.

1401 CONSTRAINT_VIOLATED

-

Constraint conditions that were defined in monitor's configuration were not met.

1604 VALIDATION_ERROR

-

Improper monitor configuration detected.

12013 UNKNOWN_HOST

Error in the hostname

IP address of the host cannot be determined. Possible causes:- Invalid hostname- DNS server unreachable- DNS cache issues- Firewall or proxy interference

12033 Execution timeout

Server operates slowly.

Timeout of request execution. Possible causes:- Network issues- Slow or unresponsive server or service- Connection blocked by firewall rules- Timeout is too small.

TCP monitor execution statuses

Code / messageExampleDescription

22000 TCP socket connection error

Service is not listening on a specified port.

This status means that the host was identified and available but the TCP connection could not be established or was unexpectedly closed. Additional explanation for the exact exception is provided. The status is used if a java.net.SocketException is thrown during the connection attempt. Possible causes:- Service is not listening on the specified port.- Service reached resource or connection limit.- Service became unavailable during the socket connection process.

Related tags
Digital ExperienceSynthetic ClassicSynthetic Classic