tree: dea8a5dfd26222f8864204fb638303482f22566d [path history] [tgz]
  1. attribute/
  2. baggage/
  3. codes/
  4. exporters/
  5. internal/
  6. metric/
  7. propagation/
  8. sdk/
  9. semconv/
  10. trace/
  11. .gitattributes
  12. .gitignore
  13. .gitmodules
  14. .golangci.yml
  15. .markdown-link.json
  16. .markdownlint.yaml
  17. CHANGELOG.md
  18. CODEOWNERS
  19. CONTRIBUTING.md
  20. doc.go
  21. error_handler.go
  22. get_main_pkgs.sh
  23. handler.go
  24. internal_logging.go
  25. LICENSE
  26. Makefile
  27. propagation.go
  28. README.md
  29. RELEASING.md
  30. trace.go
  31. verify_examples.sh
  32. version.go
  33. VERSIONING.md
  34. versions.yaml
vendor/go.opentelemetry.io/otel/README.md

OpenTelemetry-Go

CI codecov.io PkgGoDev Go Report Card Slack

OpenTelemetry-Go is the Go implementation of OpenTelemetry. It provides a set of APIs to directly measure performance and behavior of your software and send this data to observability platforms.

Project Status

SignalStatusProject
TracesStableN/A
MetricsAlphaN/A
LogsFrozen [1]N/A
  • [1]: The Logs signal development is halted for this project while we develop both Traces and Metrics. No Logs Pull Requests are currently being accepted.

Progress and status specific to this repository is tracked in our local project boards and milestones.

Project versioning information and stability guarantees can be found in the versioning documentation.

Compatibility

OpenTelemetry-Go attempts to track the current supported versions of the Go language. The release schedule after a new minor version of go is as follows:

  • The first release or one month, which ever is sooner, will add build steps for the new go version.
  • The first release after three months will remove support for the oldest go version.

This project is tested on the following systems.

OSGo VersionArchitecture
Ubuntu1.17amd64
Ubuntu1.16amd64
Ubuntu1.17386
Ubuntu1.16386
MacOS1.17amd64
MacOS1.16amd64
Windows1.17amd64
Windows1.16amd64
Windows1.17386
Windows1.16386

While this project should work for other systems, no compatibility guarantees are made for those systems currently.

Getting Started

You can find a getting started guide on opentelemetry.io.

OpenTelemetry's goal is to provide a single set of APIs to capture distributed traces and metrics from your application and send them to an observability platform. This project allows you to do just that for applications written in Go. There are two steps to this process: instrument your application, and configure an exporter.

Instrumentation

To start capturing distributed traces and metric events from your application it first needs to be instrumented. The easiest way to do this is by using an instrumentation library for your code. Be sure to check out the officially supported instrumentation libraries.

If you need to extend the telemetry an instrumentation library provides or want to build your own instrumentation for your application directly you will need to use the go.opentelemetry.io/otel/api package. The included examples are a good way to see some practical uses of this process.

Export

Now that your application is instrumented to collect telemetry, it needs an export pipeline to send that telemetry to an observability platform.

All officially supported exporters for the OpenTelemetry project are contained in the exporters directory.

ExporterMetricsTraces
Jaeger
OTLP
Prometheus
stdout
Zipkin

Additionally, OpenTelemetry community supported exporters can be found in the contrib repository.

Contributing

See the contributing documentation.