b4b461d050
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.30.0` -> `v1.31.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.31.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1310v01250) ##### 🛑 Breaking changes 🛑 - `service`: Lowercase values for 'otelcol.component.kind' attributes. ([#​12865](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12865)) - `service`: Restrict the `telemetry.newPipelineTelemetry` feature gate to metrics. ([#​12856](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12856), [#​12933](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12933)) The "off" state of this feature gate introduced a regression, where the Collector's internal logs were missing component attributes. See issue [#​12870](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12870) for more details on this bug. On the other hand, the "on" state introduced an issue with the Collector's default internal metrics, because the Prometheus exporter does not currently support instrumentation scope attributes. To solve both of these issues, this change turns on the new scope attributes for logs and traces by default regardless of the feature gate. However, the new scope attributes for metrics stay locked behind the feature gate, and will remain off by default until the Prometheus exporter is updated to support scope attributes. Please understand that enabling the `telemetry.newPipelineTelemetry` feature gate may break the export of Collector metrics through, depending on your configuration. Having a `batch` processor in multiple pipelines is a known trigger for this. This comes with a breaking change, where internal logs exported through OTLP will now use instrumentation scope attributes to identify the source component instead of log attributes. This does not affect the Collector's stderr output. See the changelog for v0.123.0 for a more detailed description of the gate's effects. ##### 💡 Enhancements 💡 - `mdatagen`: Add support for attributes for telemetry configuration in metadata. ([#​12919](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12919)) - `configmiddleware`: Add extensionmiddleware interface. ([#​12603](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12603), [#​9591](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/9591)) - `configgrpc`: Add gRPC middleware support. ([#​12603](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12603), [#​9591](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/9591)) - `confighttp`: Add HTTP middleware support. ([#​12603](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12603), [#​9591](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/9591), [#​7441](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/7441)) - `configmiddleware`: Add configmiddleware struct. ([#​12603](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12603), [#​9591](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/9591)) ##### 🧰 Bug fixes 🧰 - `exporterhelper`: Do not ignore the `num_consumers` setting when batching is enabled. ([#​12244](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12244)) - `exporterhelper`: Reject elements larger than the queue capacity ([#​12847](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12847)) - `mdatagen`: Add time and plog package imports ([#​12907](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12907)) - `confmap`: Maintain nil values when marshaling or unmarshaling nil slices ([#​11882](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/11882)) Previously, nil slices were converted to empty lists, which are semantically different than a nil slice. This change makes this conversion more consistent when encoding or decoding config, and these values are now maintained. <!-- 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:eyJjcmVhdGVkSW5WZXIiOiIzOS4yNTcuMyIsInVwZGF0ZWRJblZlciI6IjM5LjI1Ny4zIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJTa2lwIENoYW5nZWxvZyIsImRlcGVuZGVuY2llcyJdfQ==--> 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.