Overview

Code Origins captures the exact locations in your codebase where APM spans are created. When enabled, it automatically adds file path, line number, and function name to each span, making it easier to:

• Debug performance issues
• Understand code execution flow
• Identify performance bottlenecks

In Trace Explorer, select a span to see Code Origin details on the Overview tab:

Getting started

Prerequisites

• Datadog APM is configured to capture spans.
• Source Code Integration is enabled (recommended for code previews).
• Your service meets the compatibility requirements.

Compatibility requirements

Enable Code Origins

Run your service with the following environment variable:

export DD_CODE_ORIGIN_FOR_SPANS_ENABLED=true

Using Code Origins

In the Trace Explorer

1. Navigate to the Trace Explorer.

2. Click on any trace to view its details.

3. In the span details panel, look for the “Code Origin” section.

4. Optionally, click on source code variables to add them as attributes to future spans with Dynamic Instrumentation.

In your IDE

1. Set up your Datadog IDE Integration.

   • Supported IDEs: IntelliJ, VS Code
   • Supported Languages: Java, Python

2. View RED metrics (Requests, Errors, and Duration) as inline annotations above your endpoint methods.

Troubleshooting

If Code Origin information is missing:

1. Verify Code Origins is enabled in your tracing library configuration.
2. Confirm that your service meets all compatibility requirements.
   • In particular, check whether your service’s language and framework support Code Origins.
3. Filter for spans that include Code Origins using the query @_dd.code_origin.type:* in the Trace Explorer.
4. Enable Source Code Integration to see code previews in the APM Trace side panel.

Further Reading

추가 유용한 문서, 링크 및 기사:

Learn about APM terms and conceptsDOCUMENTATION Learn how to set up APM tracing with your applicationDOCUMENTATION Learn more about services in DatadogDOCUMENTATION Dive into your resource performance and tracesDOCUMENTATION Learn how to add custom spans with Dynamic InstrumentationDOCUMENTATION