-
Notifications
You must be signed in to change notification settings - Fork 151
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
Add support for activity tracing #603
Conversation
Codecov Report
@@ Coverage Diff @@
## master #603 +/- ##
==========================================
+ Coverage 89.89% 90.22% +0.32%
==========================================
Files 55 59 +4
Lines 4630 4868 +238
==========================================
+ Hits 4162 4392 +230
- Misses 468 476 +8
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It all looks good, I left a few nits. The only thing I feel strongly about is that we should allow uppercase inbound hex simply because A. the standard says implementers must accept upper case hex and B. the reverse hex decoding array you have defined already to accommodates uppercase letters.
5fbebac
to
910ce9c
Compare
This adds
traceparent
andtracestate
properties to JSON-RPC request messages to carry an activity across the wire for end-to-end activity tracing.This allows a set of structured log files to be aggregated with a viewer like Microsoft's Service Trace Viewer to produce a cross process/machine view like this (where the green boxes are from the RPC client and the yellow boxes are from the RPC server):
There are a variety of other views this tool offers. The
ActivityTracing_IntegrationTest
test produces the log files that led to the above screenshot.Closes #470