Skip to content

Add troubleshooting guide for trace context propagation in OpenTelemetry#4724

Closed
alexandra5000 wants to merge 6 commits intoelastic:mainfrom
alexandra5000:trace-propagation
Closed

Add troubleshooting guide for trace context propagation in OpenTelemetry#4724
alexandra5000 wants to merge 6 commits intoelastic:mainfrom
alexandra5000:trace-propagation

Conversation

@alexandra5000
Copy link
Contributor

@alexandra5000 alexandra5000 commented Jan 21, 2026

Summary

This PR introduces a new troubleshooting page focused on trace context header propagation issues when using OpenTelemetry with Elastic APM agents. It includes symptoms, causes, supported mixing patterns, and best practices to ensure proper trace continuity.

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No
  1. If you answered "Yes" to the previous question, please specify the tool(s) and model(s) used (e.g., Google Gemini, OpenAI ChatGPT-4, etc.).

Tool(s) and model(s) used: Claude Sonnet 4.5 via Cursor

@github-actions

This comment was marked as outdated.

@github-actions
Copy link
Contributor

github-actions bot commented Jan 21, 2026

@alexandra5000 alexandra5000 marked this pull request as ready for review January 28, 2026 14:29
@alexandra5000 alexandra5000 requested review from a team as code owners January 28, 2026 14:29
* Parent–child relationships between spans are missing when traffic crosses between:

* OpenTelemetry-instrumented services and Elastic {{product.apm}} agents.
* New and very old Elastic {{product.apm}} agents in the same call chain.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* New and very old Elastic {{product.apm}} agents in the same call chain.
* Different versions of {{product.apm}} agents in the same call chain.


Propagation problems typically occur when:

* Very old Elastic {{apm-agent}} versions (pre‑W3C) are still present.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* Very old Elastic {{apm-agent}} versions (pre‑W3C) are still present.
* Old Elastic {{apm-agent}} versions (pre‑W3C) are still present.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Or "Deprecated"

Comment on lines +98 to +107
| Agent | Minimum version |
| -------- | --------------- |
| Java | 1.14.0 |
| .NET | 1.3.0 |
| Node.js | 3.4.0 |
| Python | 5.4.0 |
| Go | 1.6.0 |
| Ruby | 3.5.0 |
| PHP | 1.0.0 |
| RUM (JS) | 5.0.0 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These are APM Agents or EDOT SDKs? We might want to clarify this, "Agent" is not specific enough.

@alexandra5000
Copy link
Contributor Author

Hey @theletterf, like I mentioned on Slack, seems like I unwittingly dragged an older commit into this branch. Let's stop for now while I undo whatever it is that has happened here - this is a very old draft unfit for review 😉

@github-actions
Copy link
Contributor

github-actions bot commented Feb 1, 2026

Vale Linting Results

Summary: 2 warnings, 1 suggestion found

⚠️ Warnings (2)
File Line Rule Message
troubleshoot/ingest/opentelemetry/edot-sdks/trace-context-propagation.md 30 Elastic.DontUse Don't use 'very'.
troubleshoot/ingest/opentelemetry/edot-sdks/trace-context-propagation.md 48 Elastic.DontUse Don't use 'Very'.
💡 Suggestions (1)
File Line Rule Message
troubleshoot/ingest/opentelemetry/edot-sdks/trace-context-propagation.md 164 Elastic.WordChoice Consider using 'deactivate, deselect, hide, turn off' instead of 'disable', unless the term is in the UI.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@alexandra5000
Copy link
Contributor Author

alexandra5000 commented Feb 1, 2026

Closing this PR to have a clean history. I applied Fabri's comments along with some other improvements on a new PR here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants