You've already forked opentelemetry-go
mirror of
https://github.com/open-telemetry/opentelemetry-go.git
synced 2025-08-10 22:31:50 +02:00
1fd38f400b
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [go.opentelemetry.io/collector/pdata](https://redirect.github.com/open-telemetry/opentelemetry-collector) | `v1.28.1` -> `v1.29.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- > [!WARNING] > Some dependencies could not be looked up. Check the Dependency Dashboard for more information. --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/pdata)</summary> ### [`v1.29.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1290v01230) ##### 🛑 Breaking changes 🛑 - `service/telemetry`: Mark `telemetry.disableAddressFieldForInternalTelemetry` as beta, usage of deprecated service::telemetry::address are ignored ([#​25115](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/25115)) To restore the previous behavior disable `telemetry.disableAddressFieldForInternalTelemetry` feature gate. - `exporterbatch`: Remove deprecated fields `min_size_items` and `max_size_items` from batch config. ([#​12684](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12684)) ##### 🚩 Deprecations 🚩 - `otlpexporter`: Mark BatcherConfig as deprecated, use `sending_queue::batch` instead ([#​12726](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12726)) - `exporterhelper`: Deprecate `blocking` in favor of `block_on_overflow`. ([#​12710](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12710)) - `exporterhelper`: Deprecate configuring exporter batching separately. Use `sending_queue::batch` instead. ([#​12772](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12772)) Moving the batching configuration to `sending_queue::batch` requires setting `sending_queue::sizer` to `items` which means that `sending_queue::queue_size` needs to be also increased by the average batch size number (roughly x5000 for the default batching configuration). See https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/exporterhelper#configuration ##### 💡 Enhancements 💡 - `exporterhelper`: Add support to configure batching in the sending queue. ([#​12746](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12746)) - `exporterhelper`: Add support for wait_for_result, remove disabled_queue ([#​12742](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12742)) This has a side effect for users of the experimental BatchConfig with the queue disabled, since not this is | uses only NumCPU() consumers. - `exporterhelper`: Allow exporter memory queue to use different type of sizers. ([#​12708](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12708)) - `service`: Add "telemetry.newPipelineTelemetry" feature gate to inject component-identifying attributes in internal telemetry ([#​12217](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12217)) With the feature gate enabled, all internal telemetry (metrics/traces/logs) will include some of the following instrumentation scope attributes: - `otelcol.component.kind` - `otelcol.component.id` - `otelcol.pipeline.id` - `otelcol.signal` - `otelcol.signal.output` These attributes are defined in the [Pipeline Component Telemetry RFC](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/component-universal-telemetry.md#attributes), and identify the component instance from which the telemetry originates. They are added automatically without changes to component code. These attributes were already included in internal logs as regular log attributes, starting from v0.120.0. For consistency with other signals, they have been switched to scope attributes (with the exception of logs emitted to standard output), and are now enabled by the feature gate. Please make sure that the exporter / backend endpoint you use has support for instrumentation scope attributes before using this feature. If the internal telemetry is exported to another Collector, a transform processor could be used to turn them into other kinds of attributes if necessary. - `exporterhelper`: Enable support to do batching using `bytes` sizer ([#​12751](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12751)) - `service`: Add config key to set metric views used for internal telemetry ([#​10769](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/10769)) The `service::telemetry::metrics::views` config key can now be used to explicitly set the list of metric views used for internal telemetry, mirroring `meter_provider::views` in the SDK config. This can be used to disable specific internal metrics, among other uses. This key will cause an error if used alongside other features which would normally implicitly create views, such as: - not setting `service::telemetry::metrics::level` to `detailed`; - enabling the `telemetry.disableHighCardinalityMetrics` feature flag. ##### 🧰 Bug fixes 🧰 - `exporterhelper`: Fix order of starting between queue and batch. ([#​12705](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12705)) <!-- previous-version --> </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR is behind base branch, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/open-telemetry/opentelemetry-go). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS4yMDcuMSIsInVwZGF0ZWRJblZlciI6IjM5LjIwNy4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJTa2lwIENoYW5nZWxvZyIsImRlcGVuZGVuY2llcyJdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
OpenTelemetry-Go
OpenTelemetry-Go is the Go implementation of OpenTelemetry. 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 | Beta1 |
Progress and status specific to this repository is tracked in our project boards and milestones.
Project versioning information and stability guarantees can be found in the versioning documentation.
Compatibility
OpenTelemetry-Go ensures compatibility with the current supported versions of the Go language:
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.24 | amd64 |
| Ubuntu | 1.23 | amd64 |
| Ubuntu | 1.24 | 386 |
| Ubuntu | 1.23 | 386 |
| Ubuntu | 1.24 | arm64 |
| Ubuntu | 1.23 | arm64 |
| macOS 13 | 1.24 | amd64 |
| macOS 13 | 1.23 | amd64 |
| macOS | 1.24 | arm64 |
| macOS | 1.23 | arm64 |
| Windows | 1.24 | amd64 |
| Windows | 1.23 | amd64 |
| Windows | 1.24 | 386 |
| Windows | 1.23 | 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.
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 otel package. The 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.
All officially supported exporters for the OpenTelemetry project are contained in the exporters directory.
| Exporter | Logs | Metrics | Traces |
|---|---|---|---|
| OTLP | ✓ | ✓ | ✓ |
| Prometheus | ✓ | ||
| stdout | ✓ | ✓ | ✓ |
| Zipkin | ✓ |
Contributing
See the contributing documentation.