-
Notifications
You must be signed in to change notification settings - Fork 328
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
store in TraceLocal useful data to diagnose errors #6
Comments
dpsoft
changed the title
Include request URI in the TraceContext if available
store in TraceLocal useful data to diagnose errors
Nov 30, 2014
ivantopo
pushed a commit
that referenced
this issue
Mar 7, 2020
* Context Propagation Throught Kanela instrumentation for `ExecutorService(submit|execute|invokeAll|invokeAny)` * JMH Instrumentation Benchmark module
ivantopo
pushed a commit
that referenced
this issue
Mar 7, 2020
* Context Propagation Throught Kanela instrumentation for ExecutorService(submit|execute|invokeAll|invokeAny)` * JMH Instrumentation Benchmark module * remove akka.dispatch package from instrumentation * * Introduce Runnable|Callable module * * Disable All Intrumentations by default * Kanela instrumentation + update to kamon 1.2.0-M1 (#9) * update to kamon-core 1.2.0-M1, latest kamon-sbt-umbrella and sbt 1.2.6
ivantopo
added a commit
that referenced
this issue
Mar 9, 2020
= scala: Support for cross building for Scala 2.10, 2.11, and 2.12.
ivantopo
pushed a commit
that referenced
this issue
Mar 9, 2020
ivantopo
pushed a commit
that referenced
this issue
Mar 29, 2020
Drop null metric tags, keep null values, temporary until Kamon#518 is…
ivantopo
added a commit
that referenced
this issue
Mar 29, 2020
add support for DoubleSizeIdentifier
ivantopo
pushed a commit
that referenced
this issue
Mar 31, 2020
ivantopo
added a commit
that referenced
this issue
Mar 31, 2020
ivantopo
added a commit
that referenced
this issue
Mar 31, 2020
Kamon 1.1 support for kamon-graphite
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
some additional diagnostic data should be available when logging errors, specifically when doing HTTP the request URI might be a very useful information, probably putting it in a TraceLocal variable would be the best way to go.
The text was updated successfully, but these errors were encountered: