module/apmot: initial tracer implementation #173
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement an OpenTracing tracer on top of the
core API. Root spans create transactions, and
child spans create spans or transactions,
depending on whether or not the parent is
remote.
Neither baggage nor logging are supported,
nor is the binary propagation format. We use
the (draft) W3C Trace-Context, for which there
is not yet a binary format.
There is a bug in the span context which we
cannot fix until spans are top-level objects,
which will happen with the v2 API. We will
revisit this when the v2 API is supported. The
bug is unlikely to affect anyone, since it will
only occur if you attempt to use span context
after the span has been finished/ended.
In line with the Elastic APM Java agent's
implementation, we support several custom tags: