Datadog Avg Latency Check
Datadog APM average latency check validates the average latency of a service using Datadog APM metrics. The target service and environment are supplied at runtime via probe variables, allowing this probe to be reused across services.
Infrastructure type
Kubernetes
Use cases
Datadog Avg Latency Check probe helps you:
Verify mean latency stays within budget during chaos
Monitor average response time after fault injection
Validate latency stability across experiment phases
Compare baseline and post-chaos average latency
Overview
This probe queries Datadog APM for the latency_avg stat of the target service, converts seconds to milliseconds using the formula avgLatency*1000, and compares the mean aggregated value against your threshold.
Probe type
APM Probe (Datadog)
Prerequisites
Kubernetes chaos infrastructure with Harness Delegate
A configured Datadog connector
Datadog APM instrumented on the target service
Probe variable
SERVICE_NAMEset at experiment runtime
Probe properties
Comparator
float
<=
300
The probe passes when the mean average latency (in milliseconds) is less than or equal to the comparator value.
Datadog APM probe inputs
connectorID
Identifier of the Datadog connector
Required at runtime
durationInMin
Look-back window in minutes
10
queryType
Datadog query API version
v2
queries[0].name
Query alias used in the formula
avgLatency
queries[0].dataSource
Metric source type
apm_metrics
queries[0].params.env
Datadog APM environment
<+probe.variables.ENV>
queries[0].params.service
Datadog APM service name
<+probe.variables.SERVICE_NAME>
queries[0].params.stat
APM latency stat
latency_avg
formula
Converts seconds to milliseconds
avgLatency*1000
aggregation
Aggregation over the time window
mean
Probe variables
SERVICE_NAME
Datadog APM service name
Yes
ENV
Datadog APM environment tag
No
Configurable inputs
CONNECTOR_ID
Datadog connector identifier
Yes
-
DURATION_IN_MIN
Look-back window in minutes
No
10
COMPARATOR_VALUE
Average latency threshold in milliseconds
Yes
300
Run properties
timeout
Maximum time to wait for the probe to complete
String
30s
interval
Time between probe executions
String
5s
attempt
Number of retry attempts before marking as failed
Integer
1
pollingInterval
Time between retry attempts
String
30s
initialDelay
Initial delay before starting the probe
String
1s
stopOnFailure
Stop the experiment if the probe fails
Boolean
false
verbosity
Log verbosity level
String
debug
Probe definition
You can define this probe in your chaos experiment as follows:
Next steps
Go to Datadog P95 Latency Check to validate p95 latency.
Go to Datadog APM Probe Templates to browse all Datadog probe templates.
Last updated
Was this helpful?