forgejo-federation/vendor/go.opentelemetry.io/otel
2021-02-28 18:08:33 -05:00
..
codes go1.16 (#14783) 2021-02-28 18:08:33 -05:00
internal
label
metric go1.16 (#14783) 2021-02-28 18:08:33 -05:00
propagation
trace go1.16 (#14783) 2021-02-28 18:08:33 -05:00
unit
.gitignore go1.16 (#14783) 2021-02-28 18:08:33 -05:00
.gitmodules
.golangci.yml
CHANGELOG.md go1.16 (#14783) 2021-02-28 18:08:33 -05:00
CODEOWNERS go1.16 (#14783) 2021-02-28 18:08:33 -05:00
CONTRIBUTING.md go1.16 (#14783) 2021-02-28 18:08:33 -05:00
doc.go
error_handler.go
get_main_pkgs.sh
go.mod go1.16 (#14783) 2021-02-28 18:08:33 -05:00
go.sum go1.16 (#14783) 2021-02-28 18:08:33 -05:00
handler.go
LICENSE
Makefile go1.16 (#14783) 2021-02-28 18:08:33 -05:00
Makefile.protos go1.16 (#14783) 2021-02-28 18:08:33 -05:00
pre_release.sh go1.16 (#14783) 2021-02-28 18:08:33 -05:00
propagation.go
README.md go1.16 (#14783) 2021-02-28 18:08:33 -05:00
RELEASING.md go1.16 (#14783) 2021-02-28 18:08:33 -05:00
tag.sh
trace.go go1.16 (#14783) 2021-02-28 18:08:33 -05:00
verify_examples.sh
version.go go1.16 (#14783) 2021-02-28 18:08:33 -05:00
VERSIONING.md

OpenTelemetry-Go

CI PkgGoDev Go Report Card Gitter

The Go OpenTelemetry implementation.

Project Status

Warning: this project is currently in a pre-GA phase. Backwards incompatible changes may be introduced in subsequent minor version releases as we work to track the evolving OpenTelemetry specification and user feedback.

Our progress towards a GA release candidate is tracked in this project board. This release candidate will follow semantic versioning and will be released with a major version greater than zero.

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.

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.

You can find officially supported exporters here and in the companion contrib repository. Additionally, there are many vendor specific or 3rd party exporters for OpenTelemetry. These exporters are broken down by trace and metric support.

Contributing

See the contributing documentation.