Skip to content

Moved Code Origins content under /tracing parent instead of /guide #29065

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
May 1, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion config/_default/menus/main.en.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -3806,7 +3806,7 @@ menu:
parent: trace_explorer
weight: 606
- name: Code Origins for Spans
url: tracing/guide/code_origins
url: tracing/code_origins
parent: tracing
identifier: tracing_code_origins
weight: 7
Expand Down
Original file line number Diff line number Diff line change
@@ -1,6 +1,8 @@
---
title: Code Origins for Spans
description: "Learn how to use Code Origins to understand where your spans originate in your codebase"
aliases:
- /tracing/guide/code_origins/
further_reading:
- link: "/tracing/glossary/"
tag: "Documentation"
Expand Down Expand Up @@ -35,7 +37,7 @@ Code Origins captures the exact locations in your codebase where APM spans are c
- Identify performance bottlenecks

In Trace Explorer, select a span to see Code Origin details on the Overview tab:
{{< img src="tracing/guide/code_origins/code_origin_details_spotlight.png" alt="Code Origin Details" style="width:100%;">}}
{{< img src="tracing/code_origins/code_origin_details_spotlight.png" alt="Code Origin Details" style="width:100%;">}}


## Getting started
Expand Down Expand Up @@ -74,7 +76,7 @@ export DD_CODE_ORIGIN_FOR_SPANS_ENABLED=true

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

{{< img src="tracing/guide/code_origins/code_origin_add_span_tag_spotlight.png" alt="Code Origin - Add span tag with Dynamic Instrumentation" style="width:100%;">}}
{{< img src="tracing/code_origins/code_origin_add_span_tag_spotlight.png" alt="Code Origin - Add span tag with Dynamic Instrumentation" style="width:100%;">}}

### In your IDE

Expand All @@ -83,7 +85,7 @@ export DD_CODE_ORIGIN_FOR_SPANS_ENABLED=true
- Supported Languages: Java, Python
2. View RED metrics (Requests, Errors, and Duration) as inline annotations above your endpoint methods.

{{< img src="tracing/guide/code_origins/code_origin_ide_details.png" alt="Code Origin Details in IDE" style="width:100%;">}}
{{< img src="tracing/code_origins/code_origin_ide_details.png" alt="Code Origin Details in IDE" style="width:100%;">}}

## Troubleshooting

Expand Down
2 changes: 1 addition & 1 deletion content/en/tracing/guide/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,5 +83,5 @@ These tutorials walk you through setting up a sample multi-service application w
{{< nextlink href="/tracing/guide/aws_payload_tagging/" >}}Capture requests and responses from AWS services automatically{{< /nextlink >}}
{{< nextlink href="/tracing/guide/service_overrides/" >}}Service Overrides{{< /nextlink >}}
{{< nextlink href="/tracing/guide/injectors/" >}}Understanding injector behavior with Single Step Instrumentation{{< /nextlink >}}
{{< nextlink href="/tracing/guide/code_origins/" >}}Code Origins for Spans{{< /nextlink >}}
{{< nextlink href="/tracing/code_origins/" >}}Code Origins for Spans{{< /nextlink >}}
{{< /whatsnext >}}
Loading