mirror of
https://github.com/open-telemetry/opentelemetry-go.git
synced 2025-02-11 13:38:37 +02:00
5661ff0ded
This release includes the first beta release of the OpenTelemetry Logs Bridge API and SDK for Go. ### Added - Add example for `go.opentelemetry.io/otel/exporters/stdout/stdoutlog`. (#5242) - Add `RecordFactory` in `go.opentelemetry.io/otel/sdk/log/logtest` to facilitate testing exporter and processor implementations. (#5258) - Add `RecordFactory` in `go.opentelemetry.io/otel/log/logtest` to facilitate testing bridge implementations. (#5263) - The count of dropped records from the `BatchProcessor` in `go.opentelemetry.io/otel/sdk/log` is logged. (#5276) - Add metrics in the `otel-collector` example. (#5283) - Add the synchronous gauge instrument to `go.opentelemetry.io/otel/metric`. (#5304) - An `int64` or `float64` synchronous gauge instrument can now be created from a `Meter`. - All implementations of the API (`go.opentelemetry.io/otel/metric/noop`, `go.opentelemetry.io/otel/sdk/metric`) are updated to support this instrument. - Add logs to `go.opentelemetry.io/otel/example/dice`. (#5349) ### Changed - The `Shutdown` method of `Exporter` in `go.opentelemetry.io/otel/exporters/stdout/stdouttrace` ignores the context cancellation and always returns `nil`. (#5189) - The `ForceFlush` and `Shutdown` methods of the exporter returned by `New` in `go.opentelemetry.io/otel/exporters/stdout/stdoutmetric` ignore the context cancellation and always return `nil`. (#5189) - Apply the value length limits to `Record` attributes in `go.opentelemetry.io/otel/sdk/log`. (#5230) - De-duplicate map attributes added to a `Record` in `go.opentelemetry.io/otel/sdk/log`. (#5230) - `go.opentelemetry.io/otel/exporters/stdout/stdoutlog` won't print timestamps when `WithoutTimestamps` option is set. (#5241) - The `go.opentelemetry.io/otel/exporters/stdout/stdoutlog` exporter won't print `AttributeValueLengthLimit` and `AttributeCountLimit` fields now, instead it prints the `DroppedAttributes` field. (#5272) - Improved performance in the `Stringer` implementation of `go.opentelemetry.io/otel/baggage.Member` by reducing the number of allocations. (#5286) - Set the start time for last-value aggregates in `go.opentelemetry.io/otel/sdk/metric`. (#5305) - The `Span` in `go.opentelemetry.io/otel/sdk/trace` will record links without span context if either non-empty `TraceState` or attributes are provided. (#5315) - Upgrade all dependencies of `go.opentelemetry.io/otel/semconv/v1.24.0` to `go.opentelemetry.io/otel/semconv/v1.25.0`. (#5374) ### Fixed - Comparison of unordered maps for `go.opentelemetry.io/otel/log.KeyValue` and `go.opentelemetry.io/otel/log.Value`. (#5306) - Fix the empty output of `go.opentelemetry.io/otel/log.Value` in `go.opentelemetry.io/otel/exporters/stdout/stdoutlog`. (#5311) - Split the behavior of `Recorder` in `go.opentelemetry.io/otel/log/logtest` so it behaves as a `LoggerProvider` only. (#5365) - Fix wrong package name of the error message when parsing endpoint URL in `go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp`. (#5371) - Identify the `Logger` returned from the global `LoggerProvider` in `go.opentelemetry.io/otel/log/global` with its schema URL. (#5375)
110 lines
5.0 KiB
Markdown
110 lines
5.0 KiB
Markdown
# OpenTelemetry-Go
|
|
|
|
[](https://github.com/open-telemetry/opentelemetry-go/actions?query=workflow%3Aci+branch%3Amain)
|
|
[](https://app.codecov.io/gh/open-telemetry/opentelemetry-go?branch=main)
|
|
[](https://pkg.go.dev/go.opentelemetry.io/otel)
|
|
[](https://goreportcard.com/report/go.opentelemetry.io/otel)
|
|
[](https://cloud-native.slack.com/archives/C01NPAXACKT)
|
|
|
|
OpenTelemetry-Go is the [Go](https://golang.org/) implementation of [OpenTelemetry](https://opentelemetry.io/).
|
|
It provides a set of APIs to directly measure performance and behavior of your software and send this data to observability platforms.
|
|
|
|
## Project Status
|
|
|
|
| Signal | Status |
|
|
|---------|--------------------|
|
|
| Traces | Stable |
|
|
| Metrics | Stable |
|
|
| Logs | Beta[^1] |
|
|
|
|
Progress and status specific to this repository is tracked in our
|
|
[project boards](https://github.com/open-telemetry/opentelemetry-go/projects)
|
|
and
|
|
[milestones](https://github.com/open-telemetry/opentelemetry-go/milestones).
|
|
|
|
Project versioning information and stability guarantees can be found in the
|
|
[versioning documentation](VERSIONING.md).
|
|
|
|
[^1]: https://github.com/orgs/open-telemetry/projects/43
|
|
|
|
### Compatibility
|
|
|
|
OpenTelemetry-Go ensures compatibility with the current supported versions of
|
|
the [Go language](https://golang.org/doc/devel/release#policy):
|
|
|
|
> Each major Go release is supported until there are two newer major releases.
|
|
> For example, Go 1.5 was supported until the Go 1.7 release, and Go 1.6 was supported until the Go 1.8 release.
|
|
|
|
For versions of Go that are no longer supported upstream, opentelemetry-go will
|
|
stop ensuring compatibility with these versions in the following manner:
|
|
|
|
- A minor release of opentelemetry-go will be made to add support for the new
|
|
supported release of Go.
|
|
- The following minor release of opentelemetry-go will remove compatibility
|
|
testing for the oldest (now archived upstream) version of Go. This, and
|
|
future, releases of opentelemetry-go may include features only supported by
|
|
the currently supported versions of Go.
|
|
|
|
Currently, this project supports the following environments.
|
|
|
|
| OS | Go Version | Architecture |
|
|
|---------|------------|--------------|
|
|
| Ubuntu | 1.22 | amd64 |
|
|
| Ubuntu | 1.21 | amd64 |
|
|
| Ubuntu | 1.22 | 386 |
|
|
| Ubuntu | 1.21 | 386 |
|
|
| Linux | 1.22 | arm64 |
|
|
| Linux | 1.21 | arm64 |
|
|
| MacOS | 1.22 | amd64 |
|
|
| MacOS | 1.21 | amd64 |
|
|
| Windows | 1.22 | amd64 |
|
|
| Windows | 1.21 | amd64 |
|
|
| Windows | 1.22 | 386 |
|
|
| Windows | 1.21 | 386 |
|
|
|
|
While this project should work for other systems, no compatibility guarantees
|
|
are made for those systems currently.
|
|
|
|
## Getting Started
|
|
|
|
You can find a getting started guide on [opentelemetry.io](https://opentelemetry.io/docs/languages/go/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](https://github.com/open-telemetry/opentelemetry-go-contrib/tree/main/instrumentation).
|
|
|
|
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 otel](https://pkg.go.dev/go.opentelemetry.io/otel)
|
|
package. The included [examples](./example/) 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.
|
|
|
|
All officially supported exporters for the OpenTelemetry project are contained in the [exporters directory](./exporters).
|
|
|
|
| Exporter | Logs | Metrics | Traces |
|
|
|---------------------------------------|:----:|:-------:|:------:|
|
|
| [OTLP](./exporters/otlp/) | ✓ | ✓ | ✓ |
|
|
| [Prometheus](./exporters/prometheus/) | | ✓ | |
|
|
| [stdout](./exporters/stdout/) | ✓ | ✓ | ✓ |
|
|
| [Zipkin](./exporters/zipkin/) | | | ✓ |
|
|
|
|
## Contributing
|
|
|
|
See the [contributing documentation](CONTRIBUTING.md).
|