NAM monitor metrics

Metrics and dimensions

Dimensions (all network availability monitors)

Name
Type
Description
Example value
multi_protocol.request.type
string
Type of request
icmp, tcp
multi_protocol.request.target_address
string
Address of target entity
54.171.216.19
dt.entity.host
string
If available, monitored entity ID for target
HOST-024C103F7F86A290
dt.entity.synthetic_location
string
Synthetic location ID (monitored entity ID)
SYNTHETIC_LOCATION-A4F834D72840EFC1
dt.entity.multiprotocol_monitor
string
Monitor ID (monitored entity ID)
MULTIPROTOCOL_MONITOR-3F6C9D500287BBAF
multi_protocol.step.id
numeric
Step sequential ID
1

Monitor metrics (all network availability monitors)

Name
Type
Dimensions
Description
builtin:synthetic.multiProtocol.executionTime
numeric
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
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.successRate
numeric
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
Ratio of executed steps that didn't fail (successes + skips) to all executed steps
We 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%.
builtin:synthetic.multiProtocol.availability
numeric
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
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.executions
numeric
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.result.status
multi_protocol.result.status.code
state
Number of monitor executions in time

Step metrics (all network availability monitors)

Name
Type
Dimensions
Description
builtin:synthetic.multiProtocol.step.executionTime
numeric
multi_protocol.request.type
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
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.successRate
numeric
multi_protocol.request.type
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
Ratio of executed requests that didn't fail (successes + skips) to all executed requests
If a step was skipped (by any of its preceding steps), it doesn't have a success rate; we treat it as if it wasn't executed.
If a step doesn't have executed requests (because its pre-execution script failed or issued SCRIPT_FINISH), we return the value 0% (for failures) or 100% (for finished).
For example, with 2 successful, 1 failed, and 4 skipped requests, the ratio is 6/7, or 85.71%.
builtin:synthetic.multiProtocol.step.availability
numeric
multi_protocol.request.type
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
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.executions
numeric
multi_protocol.request.type
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
multi_protocol.result.status
multi_protocol.result.status.code
state
Number of step executions in time

Request metrics (all network availability monitors)

Name
Type
Dimensions
Description
builtin:synthetic.multiProtocol.request.availability
numeric
multi_protocol.request.type
multi_protocol.request.target_address
dt.entity.host (only for monitors with filter defined)
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
multi_protocol.request.id
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
multi_protocol.request.type
multi_protocol.request.target_address
dt.entity.host (only for monitors with filter defined)
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
multi_protocol.request.id
multi_protocol.result.status
multi_protocol.result.status.code
state
Number of request executions in time

ICMP monitor metrics

Name
Type
Dimensions
Description
builtin:synthetic.multiProtocol.icmp.successRate
numeric
multi_protocol.request.type
multi_protocol.request.target_address
dt.entity.host (only for monitors with filter defined)
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
multi_protocol.request.id
Ratio of received packets to sent packets
Doesn'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
multi_protocol.request.type
multi_protocol.request.target_address
dt.entity.host (only for monitors with filter defined)
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
multi_protocol.request.id
Total number of packets sent
builtin:synthetic.multiProtocol.icmp.packetsReceived
numeric
multi_protocol.request.type
multi_protocol.request.target_address
dt.entity.host (only for monitors with filter defined)
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
multi_protocol.request.id
Number of packets that were returned successfully
builtin:synthetic.multiProtocol.icmp.roundTripTime
numeric
multi_protocol.request.type
multi_protocol.request.target_address
dt.entity.host (only for monitors with filter defined)
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
multi_protocol.request.id
Round-Trip Time for received packets
builtin:synthetic.multiProtocol.icmp.requestExecutionTime
numeric
multi_protocol.request.type
multi_protocol.request.target_address
dt.entity.host (only for monitors with filter defined)
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
multi_protocol.request.id
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

Name
Type
Description
Example value
multi_protocol.request.tcp_port_number
string
TCP request port number, as provided in monitor configuration
665

TCP monitor metrics

Name
Type
Dimensions
Description
builtin:synthetic.multiProtocol.tcp.connectionTime
numeric
multi_protocol.request.type
multi_protocol.request.target_address
dt.entity.host (only for monitors with filter defined)
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
multi_protocol.request.id
multi_protocol.request.tcp_port_number
Duration between start time (socket creation and connection) and end time (when confection is successfully established) in milliseconds
Metric available only if request execution took place (with no exceptions or timeouts), with a well-defined end time

DNS monitor dimensions

Name
Type
Description
Example value
multi_protocol.request.dns_record_type
string
DNS record type to be queried by request, as provided in configuration
A, AAAA, CNAME

DNS monitor metrics

Name
Type
Dimensions
Description
builtin:synthetic.multiProtocol.dns.resolutionTime
numeric
multi_protocol.request.type
multi_protocol.request.target_address
dt.entity.host (only for monitors with filter defined)
dt.entity.synthetic_location
dt.entity.multiprotocol_monitor
multi_protocol.step.id
multi_protocol.request.id
Duration between start and end time of the request to the DNS server, in milliseconds
Metric 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 / message
Example
Description
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 / message
Example
Description
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.