Skip to content
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

Support Distributed Tracing #1

Closed
2 tasks
philkra opened this issue Oct 7, 2019 · 1 comment · Fixed by #283
Closed
2 tasks

Support Distributed Tracing #1

philkra opened this issue Oct 7, 2019 · 1 comment · Fixed by #283
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@philkra
Copy link
Contributor

philkra commented Oct 7, 2019

Provide support for distributed tracing, in case an http request with the header TRACEPARENT or ELASTIC-APM-TRACEPARENT is issued, use the value that must comply W3C trace context, example.

  • Implement
  • Documentation (including on how manually pass tracing context)
@philkra philkra added the enhancement New feature or request label Oct 7, 2019
@philkra philkra self-assigned this Oct 7, 2019
@SergeyKleyman SergeyKleyman added this to the 1.0 GA milestone Jun 23, 2020
@SergeyKleyman SergeyKleyman added the documentation Improvements or additions to documentation label Jun 23, 2020
@SergeyKleyman SergeyKleyman removed the documentation Improvements or additions to documentation label Jun 23, 2020
@science695
Copy link

Not sure if this should be in its own issue, but is there a possibility of also adding the header to the intercepted curl / guzzle outgoing requests? (In addition to handling when traceparent is in the incoming request headers)

I know the RUM / js agent has a config for allowing certain domains to have the header added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants