What this mapping covers
This directory maps documented capabilities to Correlation concepts, signals, and investigation patterns. It is a reference to specific connections rather than a ranking of vendors. OpenTelemetry provides instrumentation and context; storage, query interfaces, incident grouping, and profiling integrations have different requirements.
Check the connection before relying on it
- Confirm the required signals are collected and retained for the same interval.
- Align service, environment, resource identity, and identifier formats.
- Verify the link with a known operation and an unaffected comparison.
- Check the linked product documentation for runtime support and plan requirements.
| Tool or integration | Related topic | Documented role |
|---|---|---|
| Datadog | Deployment Correlation | Deployment tracking compares service performance across deployed versions. |
| Datadog | Root Cause Analysis | Version comparisons supply evidence for a release-related hypothesis. |
| Datadog | Logs | Trace ID injection connects application logs with APM traces. |
| Datadog | Trace to Logs | Trace ID injection connects application logs with APM traces. |
| Datadog | Deployments to Error Rate | Version-based service views support release comparisons. |
| Datadog | Infrastructure to Applications | Consistent env, service, and version tags connect supported telemetry views. |
| Datadog APM and Database Monitoring | Service to Database | Supported integrations associate APM and database observations using configured propagation; service and full trace modes have different scope. |
| Datadog RUM and APM | User Session to Backend Trace | Configured browser request tracing links selected RUM resource events with backend APM traces; header propagation, allowed destinations, CORS, and sampling affect coverage. |
| Grafana | Event Correlation | Dashboard annotations overlay events on metric charts. |
| Grafana | Deployment Correlation | Release annotations provide a timeline for manual comparison. |
| Grafana | Events | Annotations display events alongside metric time series. |
| Grafana | Deployments to Error Rate | Annotations display events alongside metric time series. |
| Grafana Pyroscope | Trace to Profiles | Profile types and span-profile support vary by runtime; CPU samples must be interpreted separately from elapsed time. |
| Grafana Tempo | Traces | A configured processor derives observed service edges from recorded spans. |
| Grafana Tempo | Services to Dependencies | A configured processor derives observed service edges from recorded spans. |
| Grafana with Prometheus and Tempo | Metric Correlation | Exemplars link selected metric observations to traces when enabled. |
| Grafana with Prometheus and Tempo | Metrics | Configured exemplars provide selected metric-to-trace links. |
| Grafana with Prometheus and Tempo | Metrics to Traces | Configured exemplars provide selected metric-to-trace links. |
| Grafana with Tempo and Loki | Log Correlation | Configured links connect spans and matching log queries. |
| Grafana with Tempo and Loki | Trace Correlation | Span-to-log links add error details to a trace investigation. |
| Grafana with Tempo and Loki | Root Cause Analysis | Linked logs and spans support manual investigation; they do not prove causation. |
| Grafana with Tempo and Loki | Logs | Configured span links query related log records. |
| Grafana with Tempo and Loki | Trace to Logs | Configured span links query related log records. |
| Grafana with Tempo and Pyroscope | Profiles | Trace-to-profile navigation requires profiling, tracing, and a supported span profiling bridge. |
| Grafana with Tempo and Pyroscope | Trace to Profiles | Configured trace-to-profile links use profiling and tracing instrumentation with a supported span profiling bridge. |
| OpenTelemetry | Correlation IDs | Propagates trace context; applications can use the trace ID to connect records. |
| OpenTelemetry | Log Correlation | Log records can carry trace and span IDs. |
| OpenTelemetry | Trace Correlation | Propagated context connects spans across services. |
| OpenTelemetry | Context Propagation | Propagator APIs inject and extract context across supported boundaries. |
| OpenTelemetry | Logs | Log records can include trace and span identifiers. |
| OpenTelemetry | Traces | Propagated trace context relates spans across instrumented boundaries. |
| OpenTelemetry | Trace to Logs | Log records can include trace and span identifiers. |
| OpenTelemetry | Infrastructure to Applications | Resource attributes identify the service and runtime producing telemetry. |
| OpenTelemetry | Service to Database | Database client conventions describe target and query attributes; available fields depend on instrumentation. |
| OpenTelemetry | Queue Producer to Consumer | Messaging conventions describe producer and consumer associations, including span links. These conventions are evolving; verify the version and behavior emitted by the chosen library. |
| PagerDuty | Alert Correlation | Intelligent Alert Grouping associates related incoming alerts with incidents when configured. |
| PagerDuty | Alerts | Configured alert grouping associates related notifications with incidents. |
| PagerDuty | Alerts to Incidents | Configured alert grouping associates related notifications with incidents. |
| PagerDuty | Alerts to Incidents | Alert records remain associated with incidents and can be moved when grouping needs correction. |