JarCastinglightstep-tracer-java
The LightStep distributed tracing library for the standard Java runtime environment.
Getting started: JRE
The JRE library is hosted on Maven Central.
Note: Starting from version 0.30.0, lightstep-tracer-java-common and lightstep-tracer-java artifacts use the same major/minor version, only differing in the patch part.
Maven
<dependency>
<groupId>com.lightstep.tracer</groupId>
<artifactId>lightstep-tracer-jre</artifactId>
<version> VERSION </version>
</dependency>
<dependency>
<groupId>com.lightstep.tracer</groupId>
<artifactId>tracer-okhttp</artifactId>
<version> VERSION </version>
</dependency>
<dependency>
<groupId>org.slf4j</groupId>
<artifactId>slf4j-simple</artifactId>
<version>1.7.25</version>
</dependency>
- Be sure to replace
VERSIONwith the current version of the library. ForTRACER-GRPC-VERSIONyou can refer to lightstep-tracer-common which containstracer-grpc(andtracer-okhttp). - LightStep libraries use provided scope for grpc-netty, netty-tcnative-boringssl-static and slf4j. In other words, LightStep tracer libraries will rely on whichever gRPC/Netty/sl4j version is currently available (i.e. pulled in at runtime) to avoid conflicting with existing versions within your project
Gradle
In most cases, modifying your build.gradle with the below is all that is required:
repositories {
mavenCentral() // OR jcenter()
}
dependencies {
compile 'com.lightstep.tracer:lightstep-tracer-jre:VERSION'
compile 'com.lightstep.tracer:tracer-okhttp:VERSION'
compile 'org.slf4j:slf4j-simple:1.7.25'
}
- Be sure to replace
VERSIONwith the current version of the library - The artifact is published to both
jcenter()andmavenCentral(). Use whichever you prefer.
Initializing the LightStep Tracer
// Important the OpenTracing interfaces
import io.opentracing.Span;
import io.opentracing.Tracer;
// ...
// Initialize the OpenTracing Tracer with LightStep's implementation
Tracer tracer = new com.lightstep.tracer.jre.JRETracer(
new com.lightstep.tracer.shared.Options.OptionsBuilder()
.withAccessToken("{your_access_token}")
.build()
);
// Start and finish a Span
Span span = tracer.buildSpan("my_span").start();
this.doSomeWorkHere();
span.finish();
API Documentation
Tracing instrumentation should use the OpenTracing APIs to stay portable and in sync with the standard:
For reference, the generated LightStep documentation is also available:
Options
Setting a custom component name
To set the name used in the LightStep UI for this instance of the Tracer, call withComponentName() on the OptionsBuilder object:
options = new com.lightstep.tracer.shared.Options.OptionsBuilder()
.withAccessToken("{your_access_token}")
.withComponentName("your_custom_name")
.build();
Disabling the reporting loop
By default, the Java library does a report of any buffered data on a fairly regular interval. To disable this behavior and rely only on explicit calls to flush() to report data, initialize with:
options = new com.lightstep.tracer.shared.Options.OptionsBuilder()
.withAccessToken("{your_access_token}")
.withDisableReportingLoop(true)
.build();
To then manually flush by using the LightStep tracer object directly:
// Flush any buffered tracing data
((com.lightstep.tracer.jre.JRETracer)tracer).flush();
Flushing the report at exit
In order to send a final flush of the data prior to exit, clients should manually flush by using the LightStep tracer object as described above.
Disabling default clock correction
By default, the Java library performs clock correction based on timestamp information provided in the spans. To disable this behavior, initialize with:
options = new com.lightstep.tracer.shared.Options.OptionsBuilder()
.withAccessToken("{your_access_token}")
.withClockSkewCorrection(false)
.build();
Advanced Option: Transport and Serialization Protocols
By following the above configuration, the tracer will send information to LightStep using HTTP and Protocol Buffers which is the recommended configuration. If there are no specific transport protocol needs you have, there is no need to change this default.
There are two options for transport protocols:
- Protocol Buffers over HTTP using OkHttp - The recommended and default solution.
- Protocol Buffers over GRPC - This is a more advanced solution that might be desirable if you already have gRPC networking configured.
You can configure the tracer to support gRPC by replacing com.lightstep.tracer:tracer-okhttp with com.lightstep.tracer:tracer-grpc when including the tracer dependency and including a grpc dependency. i.e.
Maven
<dependency>
<groupId>com.lightstep.tracer</groupId>
<artifactId>lightstep-tracer-jre</artifactId>
<version> VERSION </version>
</dependency>
<dependency>
<groupId>com.lightstep.tracer</groupId>
<artifactId>tracer-grpc</artifactId>
<version> VERSION </version>
</dependency>
<dependency>
<groupId>io.grpc</groupId>
<artifactId>grpc-netty</artifactId>
<version>1.23.0</version>
</dependency>
<dependency>
<groupId>io.netty</groupId>
<artifactId>netty-tcnative-boringssl-static</artifactId>
<version>2.0.25.Final</version>
</dependency>
Gradle
repositories {
mavenCentral() // OR jcenter()
}
dependencies {
compile 'com.lightstep.tracer:lightstep-tracer-jre:VERSION'
compile 'com.lightstep.tracer:tracer-grpc:VERSION'
compile 'io.grpc:grpc-netty:1.23.0'
compile 'io.netty:netty-tcnative-boringssl-static:2.0.25.Final'
}
Development info
See DEV.md for information on contributing to this instrumentation library.
