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
7a63439b15
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.25.0` -> `v1.27.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/) | --- ### Release Notes <details> <summary>open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/pdata)</summary> ### [`v1.27.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1270v01210) ##### 🛑 Breaking changes 🛑 - `confighttp`: Make the client config options `max_idle_conns`, `max_idle_conns_per_host`, `max_conns_per_host`, and `idle_conn_timeout` integers ([#​9478](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/9478)) All four options can be set to `0` where they were previously set to `null` ##### 🚩 Deprecations 🚩 - `exporterhelper`: Deprecate `min_size_items` and `max_size_items` in favor of `min_size` and `max_size`. ([#​12486](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12486)) ##### 💡 Enhancements 💡 - `mdatagen`: Add `converter` and `provider` module classes ([#​12467](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12467)) - `pipeline`: output pipeline name with signal as signal\[/name] format in logs. ([#​12410](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12410)) - `memorylimiter`: Add support to configure min GC intervals for soft and hard limits. ([#​12450](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12450)) - `otlpexporter`: Update the stability level for logs, it has been as stable as traces and metrics for some time. ([#​12423](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12423)) - `service`: Create a new subcommand to dump the initial configuration after resolving/merging. ([#​11479](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/11479)) To use the `print-initial-config` subcommand, invoke the Collector with the subcommand and corresponding feature gate: `otelcol print-initial-config --feature-gates=otelcol.printInitialConfig --config=config.yaml`. Note that the feature gate enabling this flag is currently in alpha stability, and the subcommand may be changed in the future. - `memorylimiterprocessor`: Add support for profiles. ([#​12453](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12453)) - `otelcol`: Converters are now available in the `components` command. ([#​11900](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/11900), [#​12385](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12385)) - `component`: Mark module as stable ([#​9376](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/9376)) - `confmap`: Surface YAML parsing errors when they happen at the top-level. ([#​12180](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12180)) This adds context to some instances of the error "retrieved value (type=string) cannot be used as a Conf", which typically happens because of invalid YAML documents - `pprofile`: Add LinkIndex attribute to the generated Sample type ([#​12485](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12485)) - `exporterhelper`: Stabilize exporter.UsePullingBasedExporterQueueBatcher and remove old batch sender ([#​12425](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12425)) - `mdatagen`: Update metadata schema with new fields without enforcing them ([#​12359](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12359)) ##### 🧰 Bug fixes 🧰 - `service`: Fix crash at startup when converting from v0.2.0 to v0.3.0 ([#​12438](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12438)) - `service`: fix bug in parsing service::telemetry configuration ([#​12437](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12437)) - `exporterhelper`: Fix bug where the error logged when conversion of data fails is always nil ([#​12510](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12510)) - `mdatagen`: Adds back missing import for filter when emitting resource attributes ([#​12455](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12455)) ### [`v1.26.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1260v01200) ##### 🛑 Breaking changes 🛑 - `all`: Added support for go1.24, bumped minimum version to 1.23 ([#​12370](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12370)) - `mdatagen`: Removing deprecated generated funcs and a few test funcs as well. ([#​12304](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12304)) - `service`: Align component logger attributes with those defined in RFC ([#​12217](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12217)) See [Pipeline Component Telemetry RFC](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/main/docs/rfcs/component-universal-telemetry.md#attributes) ##### 💡 Enhancements 💡 - `otlpreceiver`: Update stability for logs ([#​12335](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12335)) - `exporterhelper`: Implement sync disabled queue used when batching is enabled. ([#​12245](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12245)) - `exporterhelper`: Enable the new pull-based batcher in exporterhelper ([#​12291](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12291)) - `exporterhelper`: Update queue size after the element is done exported ([#​12399](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12399)) After this change the active queue size will include elements in the process of being exported. - `otelcol`: Add featuregate command to display information about available features ([#​11998](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/11998)) The featuregate command allows users to view detailed information about feature gates including their status, stage, and description. ##### 🧰 Bug fixes 🧰 - `memorylimiter`: Logger no longer attributes to single signal, pipeline, or component. ([#​12217](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12217)) - `otlpreceiver`: Logger no longer attributes to random signal when receiving multiple signals. ([#​12217](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12217)) - `exporterhelper`: Fix undefined behavior access to request after send to next component. This causes random memory access. ([#​12281](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12281)) - `exporterhelper`: Fix default batcher to correctly call all done callbacks exactly once ([#​12247](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12247)) - `otlpreceiver`: Fix OTLP http receiver to correctly set Retry-After ([#​12367](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12367)) - `otlphttpexporter`: Fix parsing logic for Retry-After in OTLP http protocol. ([#​12366](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12366)) The value of Retry-After field can be either an HTTP-date or delay-seconds and the current logic only parsed delay-seconds. - `cmd/builder`: Ensure unique aliases for modules with same suffix ([#​12201](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12201)) </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:eyJjcmVhdGVkSW5WZXIiOiIzOS4xNjcuMSIsInVwZGF0ZWRJblZlciI6IjM5LjE4NS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJTa2lwIENoYW5nZWxvZyIsImRlcGVuZGVuY2llcyJdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com> Co-authored-by: dmathieu <42@dmathieu.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.