2019-08-05 22:58:24 +02:00
|
|
|
# OpenTelemetry-Go
|
|
|
|
|
|
2019-07-03 16:43:54 +02:00
|
|
|
[](https://circleci.com/gh/open-telemetry/opentelemetry-go)
|
2020-03-30 21:40:38 +02:00
|
|
|
[](https://pkg.go.dev/go.opentelemetry.io/otel)
|
2019-11-01 20:40:29 +02:00
|
|
|
[](https://goreportcard.com/report/go.opentelemetry.io/otel)
|
2019-11-01 06:56:25 +02:00
|
|
|
[](https://gitter.im/open-telemetry/opentelemetry-go?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge)
|
2019-07-03 01:22:54 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
The Go [OpenTelemetry](https://opentelemetry.io/) implementation.
|
2019-06-14 20:37:05 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
## Getting Started
|
2019-10-02 07:43:06 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
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.
|
2019-10-02 07:43:06 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
### Instrumentation
|
2019-10-02 07:43:06 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
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](https://github.com/open-telemetry/opentelemetry-go-contrib/tree/master/instrumentation).
|
2019-10-02 07:43:06 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
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](https://pkg.go.dev/go.opentelemetry.io/otel/api)
|
|
|
|
|
package. The included [examples](./example/) are a good way to see some
|
|
|
|
|
practical uses of this process.
|
2020-03-12 18:52:12 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
### Export
|
2019-10-02 07:43:06 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
Now that your application is instrumented to collect telemetry, it needs an
|
|
|
|
|
export pipeline to send that telemetry to an observability platform.
|
2019-10-02 07:43:06 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
You can find officially supported exporters [here](./exporters/) and in the
|
|
|
|
|
companion [contrib
|
|
|
|
|
repository](https://github.com/open-telemetry/opentelemetry-go-contrib/tree/master/exporters/metric).
|
|
|
|
|
Additionally, there are many vendor specific or 3rd party exporters for
|
|
|
|
|
OpenTelemetry. These exporters are broken down by
|
|
|
|
|
[trace](https://pkg.go.dev/go.opentelemetry.io/otel/sdk/export/trace?tab=importedby)
|
|
|
|
|
and
|
|
|
|
|
[metric](https://pkg.go.dev/go.opentelemetry.io/otel/sdk/export/metric?tab=importedby)
|
|
|
|
|
support.
|
2020-03-12 18:52:12 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
## Project Status
|
2019-10-02 07:43:06 +02:00
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
[Project boards](https://github.com/open-telemetry/opentelemetry-go/projects)
|
|
|
|
|
and [milestones](https://github.com/open-telemetry/opentelemetry-go/milestones)
|
|
|
|
|
can be found at the respective links. We try to keep these accurate and should
|
|
|
|
|
be the best place to go for answers on project status.
|
2020-04-02 19:58:09 +02:00
|
|
|
|
2019-10-01 18:16:45 +02:00
|
|
|
## Contributing
|
|
|
|
|
|
2020-08-27 21:14:37 +02:00
|
|
|
See the [contributing documentation](CONTRIBUTING.md).
|
