Failed Spans
dynatrace_failed_spansGroup error spans by service, span, and pod to triage failures and compare latency versus errors after service health checks flag issues.
Instructions
Error spans grouped by service/span/pod. Use after service_health shows failures or for latency vs error triage.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "dynatrace_failed_spans"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | End: now or ISO-8601 | |
| from | No | Start: now-30m or ISO-8601 | |
| limit | No | ||
| around | No | Pivot timestamp for a window | |
| window | No | Half-window around pivot, e.g. 2m | |
| endDate | No | Calendar end YYYY-MM-DD (UTC day) | |
| service | No | Service name substring | |
| namespace | No | Kubernetes namespace (k8s.namespace.name). Discover with dynatrace_list_namespaces. | |
| startDate | No | Calendar start YYYY-MM-DD (UTC day) | |
| connection | No | Named connection from env (default, optional stage/prod aliases, or a DYNATRACE_CONNECTIONS key) | |
| allowLongRange | No | Allow ranges longer than the default cap |