d98ad1042c
* Remove quotes from UnmarshalJSON Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com> * Update CHANGELOG.md Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com> * Fix issue number in CHANGELOG.md * Fix 'Code.UnmarshalJSON' to work with valid json only Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com> * Extend test data for TestCodeUnmarshalJSONErrorInvalidData Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com> * Delete useless cond, extend test data Signed-off-by: Daniil Rutskiy <dstdfx@gmail.com> |
||
|---|---|---|
| .circleci | ||
| .github | ||
| bridge/opentracing | ||
| codes | ||
| example | ||
| exporters | ||
| global | ||
| internal | ||
| label | ||
| oteltest | ||
| propagators | ||
| registry | ||
| sdk | ||
| semconv | ||
| unit | ||
| .gitignore | ||
| .gitmodules | ||
| .golangci.yml | ||
| alignment_test.go | ||
| baggage_test.go | ||
| baggage.go | ||
| CHANGELOG.md | ||
| CODEOWNERS | ||
| config_test.go | ||
| config.go | ||
| CONTRIBUTING.md | ||
| doc.go | ||
| error_handler.go | ||
| get_main_pkgs.sh | ||
| go.mod | ||
| go.sum | ||
| instrumentkind_string.go | ||
| LICENSE | ||
| Makefile | ||
| Makefile.proto | ||
| metric_instrument.go | ||
| metric_noop.go | ||
| metric_sdkapi.go | ||
| metric_test.go | ||
| metric.go | ||
| number_test.go | ||
| number.go | ||
| numberkind_string.go | ||
| pre_release.sh | ||
| propagation_test.go | ||
| propagation.go | ||
| README.md | ||
| RELEASING.md | ||
| tag.sh | ||
| trace_noop_test.go | ||
| trace_noop.go | ||
| trace_test.go | ||
| trace.go | ||
| verify_examples.sh | ||
OpenTelemetry-Go
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
This project is currently in a pre-GA phase. Our progress towards a GA release candidate is tracked in this project board.
Progress and status specific to this repository is tracked in our local 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.