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.

Sign up for GitHub

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

Jump to bottom

Create XRayInstrument #34

Open

9 tasks

pokryfka opened this issue Jul 30, 2020 · 0 comments

Labels

Owner

pokryfka commented Jul 30, 2020 •

edited

Loading

PoC implemented in #16

TODO:

map HTTP Span attributes to XRay segment HTTP, depends on Add OT semantic convention extensions to SpanAttribute slashmo/gsoc-swift-tracing#65
Record exceptions, depends on Add error recording API to Span slashmo/gsoc-swift-tracing#90
log SpanEvent timestamp and attributes
log SpanLink
implement forceFlush and shutdown, depends on Add forceFlush to trace instruments slashmo/gsoc-swift-tracing#85, see Extend recorder API to let shutdown it gracefully #21
update InstrumentationSystem bootstrap in AWSXRayInstrumentExample , depends on Polish instrument initialization and lookups slashmo/gsoc-swift-tracing#86
add example of instrumenting HTTP client (remove BetterHTTPClient), depends on Record HTTP requests made by AsyncHTTPClient slashmo/gsoc-swift-tracing#95
add example of passing baggage in NIO channel, depends on Share BaggageContext across multiple NIO handlers slashmo/gsoc-swift-tracing#48
document usage in README

The text was updated successfully, but these errors were encountered:

pokryfka added the enhancement label

pokryfka mentioned this issue

XRayInstrument should map HTTP Span attributes to XRay segment HTTP #22

Open

pokryfka added this to the v0.6.0 milestone

pokryfka removed this from the v0.8.0 milestone

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