1
0
mirror of https://github.com/open-telemetry/opentelemetry-go.git synced 2025-01-05 22:54:18 +02:00
OpenTelemetry Go API and SDK https://opentelemetry.io/
Go to file
2020-09-10 00:53:27 -04:00
.circleci Export coverage report to codecov (#995) 2020-08-24 09:43:29 -07:00
.github Move tools package under internal (#1141) 2020-09-09 09:14:03 -07:00
api Rename CorrelationContext to Baggage (#1142) 2020-09-09 14:13:37 -04:00
bridge/opentracing Rename CorrelationContext to Baggage (#1142) 2020-09-09 14:13:37 -04:00
codes Remove google.golang.org/grpc/codes dependency from API by adding an equivalent codes package (#1046) 2020-08-10 09:17:09 -07:00
example Rename CorrelationContext to Baggage (#1142) 2020-09-09 14:13:37 -04:00
exporters Bump google.golang.org/grpc from 1.31.1 to 1.32.0 in /sdk (#1145) 2020-09-09 13:25:27 -04:00
internal Bump github.com/golangci/golangci-lint from 1.30.0 to 1.31.0 in /internal/tools (#1152) 2020-09-09 12:49:55 -04:00
label Unify api/label and api/kv in new label package (#1060) 2020-08-17 20:25:03 -07:00
propagators Unexport NoopXXX trace types (#1134) 2020-09-08 20:43:35 -04:00
sdk Bump google.golang.org/grpc from 1.31.1 to 1.32.0 in /sdk (#1145) 2020-09-09 13:25:27 -04:00
semconv Unify api/label and api/kv in new label package (#1060) 2020-08-17 20:25:03 -07:00
.gitignore Import open-telemetry/opentelemetry-proto submodule and generate protobuf bindings locally (#942) 2020-07-16 13:59:14 -07:00
.gitmodules Move OTLP to the OTLP exporter (#1050) 2020-08-10 19:55:52 -07:00
.golangci.yml Remove nolint and update misspell to ignore cancelled 2020-05-29 11:11:19 -07:00
CHANGELOG.md Rename CorrelationContext to Baggage (#1142) 2020-09-09 14:13:37 -04:00
CODEOWNERS Add @XSAM as project approver (#1110) 2020-08-28 17:05:48 -04:00
CONTRIBUTING.md Document make test for testing (#1154) 2020-09-10 00:53:27 -04:00
doc.go Alias api/global types, functions to root 2020-05-03 16:01:15 +08:00
error_handler.go Remove the oterror package (#1026) 2020-08-05 10:31:42 -07:00
get_main_pkgs.sh Update License header for all source files (#586) 2020-03-23 22:41:10 -07:00
go.mod Bump github.com/google/go-cmp from 0.5.1 to 0.5.2 (#1093) 2020-08-26 11:39:41 -07:00
go.sum Bump github.com/google/go-cmp from 0.5.1 to 0.5.2 (#1093) 2020-08-26 11:39:41 -07:00
LICENSE Initial commit 2019-05-16 12:05:27 -07:00
Makefile Move tools package under internal (#1141) 2020-09-09 09:14:03 -07:00
Makefile.proto Move OTLP to the OTLP exporter (#1050) 2020-08-10 19:55:52 -07:00
otel.go rm api/global alias functions 2020-05-07 00:41:11 +08:00
pre_release.sh fix pre_release.sh to update version in sdk/opentelemetry.go (#607) 2020-03-31 12:02:56 -07:00
README.md Update README.md (#1106) 2020-08-27 12:14:37 -07:00
RELEASING.md Add reminder to release contrib after this repo (#1030) 2020-08-05 09:01:00 -07:00
tag.sh Move tools package under internal (#1141) 2020-09-09 09:14:03 -07:00
verify_examples.sh Clean up tools (#762) 2020-05-26 11:35:34 -07:00

OpenTelemetry-Go

Circle CI Docs Go Report Card Gitter

The Go OpenTelemetry implementation.

Getting Started

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.

Project Status

Project boards and 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.

Contributing

See the contributing documentation.