lightstep-tracer-go | The Lightstep distributed tracing library for Go
kandi X-RAY | lightstep-tracer-go Summary
kandi X-RAY | lightstep-tracer-go Summary
The LightStep distributed tracing library for Go.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- CreateTracer creates a new tracer
- newSpan returns a new span .
- Measure returns metrics for the process .
- Main entry point
- newGrpcCollectorClient returns a new gRPCCollectorClient .
- testBody evaluates the request body and returns the amount of time between the body .
- newHTTPCollectorClient returns a new httpCollectorClient .
- NewExporter returns a new Exporter .
- doWork is used to run the number of workers
- getLabels returns a list of key - value pairs
lightstep-tracer-go Key Features
lightstep-tracer-go Examples and Code Snippets
Community Discussions
Trending Discussions on lightstep-tracer-go
QUESTION
Background
I have a java server that is making an RPC call to a go server. The java rpc client and go rpc server are instrumented with lightstep. Everything about the trace looks normal except for where in the lightstep UI, the go rpc server span is placed.
The java span has ts 1493929521325 which is right before the request is sent to the go server. The go rpc server has 2 timestamps: 1493929521326 is when it received the request and started the span, 1493929521336 is after it responded and finished the span.
Problem
I would expect the UI to have the go span horizontally to the immediate right of the java span. Instead, it is far to the right.
The only possible cause I can think of is an incompatibility between v0.10.1 which java code is using and v0.9.1 which go is using. Is this a possibility? Do you have any thoughts on a possible cause?
The go code is essentially:
...ANSWER
Answered 2017-Jun-13 at 20:47[Disclaimer: I work at LightStep]
Sorry you're having trouble getting Java and Go to play well together. I suspect this is caused by time-correction being enabled in Java but not being used in Go.
You can disable time correction in Java using the withClockSkewCorrection(boolean clockCorrection)
option to turn off clockCorrection when passing in options to the LightStep tracer
Here is the updated README and a link to the option code
If you contact us via the [Support] button in LightStep, we should be able to get you sorted out. Please send us a note so that we can confirm that this is solved for you.
We'll start monitoring SO more carefully so that we catch these things earlier.
Thanks and happy tracing!
Will
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install lightstep-tracer-go
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page