1
0
mirror of https://github.com/open-telemetry/opentelemetry-go.git synced 2025-01-10 00:29:12 +02:00
OpenTelemetry Go API and SDK https://opentelemetry.io/
Go to file
dependabot[bot] fa741472e7
Bump google.golang.org/api from 0.31.0 to 0.32.0 in /exporters/trace/jaeger (#1188)
* Bump google.golang.org/api in /exporters/trace/jaeger

Bumps [google.golang.org/api](https://github.com/googleapis/google-api-go-client) from 0.31.0 to 0.32.0.
- [Release notes](https://github.com/googleapis/google-api-go-client/releases)
- [Changelog](https://github.com/googleapis/google-api-go-client/blob/master/CHANGES.md)
- [Commits](https://github.com/googleapis/google-api-go-client/compare/v0.31.0...v0.32.0)

Signed-off-by: dependabot[bot] <support@github.com>

* Auto-fix go.sum changes in dependent modules

Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: dependabot[bot] <dependabot[bot]@users.noreply.github.com>
Co-authored-by: Anthony Mirabella <a9@aneurysm9.com>
2020-09-21 12:06:05 -04:00
.circleci Export coverage report to codecov (#995) 2020-08-24 09:43:29 -07:00
.github Allow up to 0.5% coverage change before failing build (#1162) 2020-09-10 12:49:08 -07:00
api Move api/unit to top level (#1185) 2020-09-20 13:54:21 -04:00
bridge/opentracing Ensure exported interfaces have named method parameters (#1172) 2020-09-16 09:09:45 -07:00
codes Add the missing vanity import path directive (#1157) 2020-09-10 06:29:21 -04:00
example Bump google.golang.org/api from 0.31.0 to 0.32.0 in /exporters/trace/jaeger (#1188) 2020-09-21 12:06:05 -04:00
exporters Bump google.golang.org/api from 0.31.0 to 0.32.0 in /exporters/trace/jaeger (#1188) 2020-09-21 12:06:05 -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 Ensure exported interfaces have named method parameters (#1172) 2020-09-16 09:09:45 -07:00
propagators Unexport NoopXXX trace types (#1134) 2020-09-08 20:43:35 -04:00
sdk Add ForceFlush() method to SpanProcessor interface (#1166) 2020-09-20 13:35:44 -04:00
semconv Add more semantic conventions for k8s as resource attributes (#1167) 2020-09-11 14:46:24 -07:00
unit Move api/unit to top level (#1185) 2020-09-20 13:54:21 -04: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
CHANGELOG.md Move api/unit to top level (#1185) 2020-09-20 13:54:21 -04:00
CODEOWNERS Add @XSAM as project approver (#1110) 2020-08-28 17:05:48 -04:00
CONTRIBUTING.md Ensure exported interfaces have named method parameters (#1172) 2020-09-16 09:09:45 -07:00
doc.go Merge otel into one file and add package doc (#1176) 2020-09-14 19:35:21 -04:00
get_main_pkgs.sh
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
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 Merge otel into one file and add package doc (#1176) 2020-09-14 19:35:21 -04:00
pre_release.sh
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

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.