From 48c72d3f0e9f8285a1e2741ad2664967dc5efa67 Mon Sep 17 00:00:00 2001 From: Gianluca Bortoli Date: Fri, 9 Jan 2026 11:02:24 +0100 Subject: [PATCH] Clarify complete trace requirement for ET on APM --- content/en/tracing/error_tracking/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/tracing/error_tracking/_index.md b/content/en/tracing/error_tracking/_index.md index d5e60158f5d..eb92b71c639 100644 --- a/content/en/tracing/error_tracking/_index.md +++ b/content/en/tracing/error_tracking/_index.md @@ -36,7 +36,7 @@ To get started with configuring your repository, see the [Source Code Integratio ## Use span attributes to track error spans -The Datadog tracers collect errors through integrations and the manual instrumentation of your backend services' source code. An error span must contain the `error.stack`, `error.message`, and `error.type` [span attributes][1] to be tracked. If an error is reported multiple times within a service, only the top-most error is kept. +The Datadog tracers collect errors through integrations and the manual instrumentation of your backend services' source code. An error span must contain the `error.stack`, `error.message`, and `error.type` [span attributes][1] and belong to a complete trace to be tracked. If an error is reported multiple times within a service, only the top-most error is kept. {{< img src="tracing/error_tracking/flamegraph_with_errors.png" alt="Flame graph with errors" style="width:100%;" >}}