We hold regular meetings. See details at community page.
OpenTelemetry is the merging of OpenCensus and OpenTracing into one project.
This project contains the following top level components:
- OpenTelemetry API:
- tracing api includes
Tracer
,Span
andSpanContext
. - baggage api defines a collection of entries in the form of key-value pairs of data that can be propagated to provide contextual information.
- context api defines the in-process and inter-process propagation layer.
- metrics api.
- tracing api includes
- extensions define additional API extensions, which are not part of the core API.
- sdk define the reference implementation complying to the OpenTelemetry API.
- sdk extensions define additional SDK extensions, which are not part of the core SDK.
- OpenTracing shim defines a bridge layer from OpenTracing to the OpenTelemetry API.
- examples on how to use the APIs, SDK, and standard exporters.
We would love to hear from the larger community: please provide feedback proactively.
Both API and SDK extensions consist of various additional components which are excluded from the core artifacts to keep them from growing too large. We still aim to provide the same level of quality and guarantee for them as for the core components. Please don't hesitate to use them if you find them useful.
Please refer to the contribution guide on how to setup and contribute!
Please refer to the quick start guide on how use the OpenTelemetry API.
Published releases are available on maven central.
<dependencies>
<dependency>
<groupId>io.opentelemetry</groupId>
<artifactId>opentelemetry-api</artifactId>
<version>0.9.1</version>
</dependency>
</dependencies>
dependencies {
implementation('io.opentelemetry:opentelemetry-api:0.9.1')
}
Snapshots based out the master
branch are available for opentelemetry-api
, opentelemetry-sdk
and the rest of the artifacts:
<repositories>
<repository>
<id>oss.sonatype.org-snapshot</id>
<url>https://oss.jfrog.org/artifactory/oss-snapshot-local</url>
</repository>
</repositories>
<dependencies>
<dependency>
<groupId>io.opentelemetry</groupId>
<artifactId>opentelemetry-api</artifactId>
<version>0.10.0-SNAPSHOT</version>
</dependency>
</dependencies>
repositories {
maven { url 'https://oss.jfrog.org/artifactory/oss-snapshot-local' }
}
dependencies {
implementation('io.opentelemetry:opentelemetry-api:0.10.0-SNAPSHOT')
}
Libraries will usually only need opentelemetry-api
, while applications
may want to use opentelemetry-sdk
.
OpenTelemetry Java is under active development. Releases aren't guaranteed to conform to a specific version of the specification. Future releases will not attempt to maintain backwards compatibility with previous releases.
Check out information about the latest release.
This is a current feature status list:
Component | Version |
---|---|
Tracing API | v0.9.1 |
Tracing SDK | v0.9.1 |
Metrics API | v0.9.1 |
Metrics SDK | v0.9.1 |
OTLP Exporter | v0.9.1 |
Jaeger Trace Exporter | v0.9.1 |
Zipkin Trace Exporter | v0.9.1 |
Prometheus Metrics Exporter | v0.9.1 |
Context Propagation | v0.9.1 |
OpenTracing Bridge | v0.9.1 |
OpenCensus Bridge | N/A |
See the project milestones for details on upcoming releases. The dates and features described in issues and milestones are estimates, and subject to change.
We plan to merge projects and pave the path for future improvements as a unified community of tracing vendors, users and library authors who wants apps be managed better. We are open to feedback and suggestions from all of you!
See CONTRIBUTING.md
Approvers (@open-telemetry/java-approvers):
- Armin Ruech, Dynatrace
- Pavol Loffay, RedHat
- Tyler Benson, DataDog
- Giovanni Liva, Dynatrace
Find more about the approver role in community repository.
Maintainers (@open-telemetry/java-maintainers):
- Bogdan Drutu, Splunk
- Carlos Alberto, LightStep
- John Watson, Splunk
- Anuraag Agrawal, AWS
Find more about the maintainer role in community repository.