Dynatrace Extends Root Cause Analysis to OpenTelemetry Services

Dynatrace says its Causal AI can now extend root-cause analysis across OpenTelemetry-instrumented services, monitored frontends, and databases. The company is combining telemetry pipelines, unified data, and dependency context to help teams investigate incidents and provide structured information to AI workflows.
- Dynatrace says Causal AI now analyzes OpenTelemetry-instrumented services.
- The analysis covers frontends, OpenTelemetry services, and databases.
- The OTel-Native Telemetry Pipeline can filter, mask, enrich, and route telemetry.
- Grail and Smartscape preserve data and dependency context for investigations.
- Root-cause information can provide structured context for AI workflows.
Managing OpenTelemetry data at scale
OpenTelemetry gives organizations flexibility in how they collect telemetry, but Dynatrace says that value depends on how effectively teams manage the resulting data and turn it into reliable answers. The company says this is increasingly important as AI becomes part of software delivery and operations, because both teams and AI agents need context around telemetry to understand what happened and decide what to do next.
Dynatrace's OTel-Native Telemetry Pipeline is designed to help organizations control what they collect, how they process it, and where they send it. According to Dynatrace, telemetry pipelines can filter, mask, enrich, and route data before analysis. These controls can help reduce unnecessary volume, protect sensitive information, and preserve important signals. Centralized collector management is intended to apply those policies consistently across environments, while helping organizations manage cost and compliance needs.
Connecting signals to identify the source of an incident
Dynatrace says OpenTelemetry data can be brought together in its Grail data lakehouse, making logs, metrics, and traces accessible for analysis across telemetry types. The company also uses Smartscape topology to map how services connect and what they depend on. Preserving those relationships helps teams understand how an issue moves through an environment and where it began.
Dynatrace Causal AI, part of Dynatrace Intelligence, now applies root-cause analysis across OpenTelemetry services, frontends, and databases. When several services in a chain degrade together, their anomalies are merged into a single Problem that identifies the root cause, rather than leaving teams with separate problems for each affected service.
The analysis can follow a path from a monitored web or mobile frontend through OpenTelemetry services to the databases they call. This includes cloud databases and databases monitored with a Dynatrace extension. Dynatrace says Causal AI follows Smartscape topology on Grail data and uses the actual relationships between affected components to determine where a problem originates. An OpenTelemetry service can be identified as the root cause, as can a monitored and alerting database instance.
Structured context for agentic AI workflows
Dynatrace says root-cause analysis can give AI workflows structured information about an incident's impact, origin, and causal relationships. That context could support remediation, resilience testing, or software delivery by helping an agent decide which actions to take and evaluate the results.
The company describes the resulting information as including the observed impact, an identified root cause, and the causal path. It also cautions that agent behavior, recommendations, and actions depend on the agent implementation, permissions, and available data.
For users, Dynatrace presents the OpenTelemetry integration as a way to reduce alert noise, speed root-cause identification, and spend less time triaging affected services. The company directs users to its getting started guide for connecting applications and configuring telemetry ingestion. It also offers a free trial and invites questions through the Dynatrace Community.


