Skip to content

ddtrace: add option to force SpanID#392

Merged
willgittoes-dd merged 2 commits into
v1from
willgittoes-dd/span-id-option
Jan 31, 2019
Merged

ddtrace: add option to force SpanID#392
willgittoes-dd merged 2 commits into
v1from
willgittoes-dd/span-id-option

Conversation

@willgittoes-dd

Copy link
Copy Markdown
Contributor

Use-case: I have a tracing "surrogate". I can't directly do tracing from the target application, so I have to build (I prefer in Golang) a surrogate that will create spans using information from the target application. That target still chooses the span/trace IDs, so that it can put them in headers. However the target cannot receive information from the tracer, so the tracer cannot be the one to choose the IDs. So therefore the tracing surrogate must create spans with IDs that are pre-decided by the target application.

@willgittoes-dd
willgittoes-dd force-pushed the willgittoes-dd/span-id-option branch 2 times, most recently from ef80980 to 0a106f3 Compare January 31, 2019 01:30
@willgittoes-dd
willgittoes-dd force-pushed the willgittoes-dd/span-id-option branch from 0a106f3 to af959d6 Compare January 31, 2019 02:33
@gbbr gbbr changed the title Add option to force SpanID ddtrace: add option to force SpanID Jan 31, 2019
@gbbr
gbbr requested a review from palazzem January 31, 2019 07:57
@gbbr gbbr modified the milestones: next, 1.10.0 Jan 31, 2019
@willgittoes-dd
willgittoes-dd merged commit 76f75b4 into v1 Jan 31, 2019
@willgittoes-dd
willgittoes-dd deleted the willgittoes-dd/span-id-option branch January 31, 2019 22:29
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.

3 participants