Skip to content

Conversation

@alexandra5000
Copy link
Contributor

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.

Closes #2359

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
Copy link
Contributor

Vale Linting Results

Summary: 2 warnings, 3 suggestions 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 (3)
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.
troubleshoot/ingest/opentelemetry/edot-sdks/trace-context-propagation.md 181 Elastic.EmDashes Don't put a space before or after a dash.
troubleshoot/ingest/opentelemetry/edot-sdks/trace-context-propagation.md 182 Elastic.EmDashes Don't put a space before or after a dash.

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.

@github-actions
Copy link
Contributor

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.

Trace context propagation issues

1 participant