OpenTracing + Lightstep
Open source instrumentation and APIs for distributed tracing
Own Your Data
Switch to and from any other OpenTracing-compatible tracing visualization and analysis solution without changing your instrumentation.
Integrate with virtually anything — proxies, service meshes, and common languages and frameworks, such as Java, Flask, Ruby, C#, Go, and Swift.
Lightstep’s unique Satellite Architecture collects 100% of your tracing data — including data from mobile apps, web clients, and serverless — offering end-to-end visibility into every aspect of your application.
Aggregate, analyze, and visualize thousands of traces in order to answer specific, high-value questions about the health of your services or system.
Quickly identify the services, dependencies, and teams responsible for slowness, errors, or other issues that cross service boundaries.
Know which optimization efforts will improve availability and performance, and where cycles would otherwise be wasted. Analyze how performance changes over time — whether it’s a SQL query or all microservice requests for a customer.
What is OpenTracing?
OpenTracing is a standard for vendor-neutral APIs and instrumentation for distributed tracing. OpenTracing allows developers of application code, OSS packages, and OSS services to instrument their own code without binding to any particular tracing vendor. The OpenTracing standard was created by the OSS community, including LightStep CEO and Co-Founder Ben Sigelman.
How Does OpenTracing Relate to OpenTelemetry?
OpenTracing has helped those adopting microservices and serverless more easily – and portably – instrument their software for distributed tracing. OpenCensus (a Google-founded OSS project) shared similar goals with different emphases, as well as a broader effort to standardize metrics and logging. OpenTracing and OpenCensus are merging to form OpenTelemetry, which will be backwards compatible with OpenTracing.
OpenTracing is a Cloud Native Computing Foundation Project.