You've already forked opentelemetry-go
mirror of
https://github.com/open-telemetry/opentelemetry-go.git
synced 2025-09-16 09:26:25 +02:00
83403d339c
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [go.opentelemetry.io/collector/pdata](https://redirect.github.com/open-telemetry/opentelemetry-collector) | `v1.38.0` -> `v1.40.0` | [](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.40.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1400v01340) ##### 💡 Enhancements 💡 - `pdata`: Add custom grpc/encoding that replaces proto and calls into the custom marshal/unmarshal logic in pdata. ([#​13631](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13631)) This change should not affect other gRPC calls since it fallbacks to the default grpc/proto encoding if requests are not pdata/otlp requests. - `pdata`: Avoid copying the pcommon.Map when same origin ([#​13731](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13731)) This is a very large improvement if using OTTL with map functions since it will avoid a map copy. - `exporterhelper`: Respect `num_consumers` when batching and partitioning are enabled. ([#​13607](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13607)) ##### 🧰 Bug fixes 🧰 - `pdata`: Correctly parse OTLP payloads containing non-packed repeated primitive fields ([#​13727](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13727), [#​13730](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13730)) This bug prevented the Collector from ingesting most Histogram, ExponentialHistogram, and Profile payloads. <!-- previous-version --> ### [`v1.39.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1390v01330) ##### 🛑 Breaking changes 🛑 - `all`: Increase minimum Go version to 1.24 ([#​13627](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13627)) ##### 💡 Enhancements 💡 - `otlphttpexporter`: Add `profiles_endpoint` configuration option to allow custom endpoint for profiles data export ([#​13504](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13504)) The `profiles_endpoint` configuration follows the same pattern as `traces_endpoint`, `metrics_endpoint`, and `logs_endpoint`. When specified, profiles data will be sent to the custom URL instead of the default `{endpoint}/v1development/profiles`. - `pdata`: Add support for local memory pooling for data objects. ([#​13678](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13678)) This is still an early experimental (alpha) feature. Do not recommended to be used production. To enable use "--featuregate=+pdata.useProtoPooling" - `pdata`: Optimize CopyTo messages to avoid any copy when same source and destination ([#​13680](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13680)) - `receiverhelper`: New feature flag to make receiverhelper distinguish internal vs. downstream errors using new `otelcol_receiver_failed_x` and `otelcol_receiver_requests` metrics ([#​12207](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12207), [#​12802](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12802)) This is a breaking change for the semantics of the otelcol\_receiver\_refused\_metric\_points, otelcol\_receiver\_refused\_log\_records and otelcol\_receiver\_refused\_spans metrics. These new metrics and semantics are enabled through the `receiverhelper.newReceiverMetrics` feature gate. - `debugexporter`: Add support for entity references in debug exporter output ([#​13324](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13324)) - `pdata`: Fix unnecessary allocation of a new state when adding new values to pcommon.Map ([#​13634](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13634)) - `service`: Implement refcounting for pipeline data owned memory. ([#​13631](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13631)) This feature is protected by `--featuregate=+pdata.useProtoPooling`. - `service`: Add a debug-level log message when a consumer returns an error. ([#​13357](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13357)) - `xpdata`: Optimize xpdata/context for persistent queue when only one value for key ([#​13636](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13636)) - `otlpreceiver`: Log the listening addresses of the receiver, rather than the configured endpoints. ([#​13654](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13654)) - `pdata`: Use the newly added proto marshaler/unmarshaler for the official proto Marshaler/Unmarshaler ([#​13637](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13637)) If any problems observed with this consider to disable the featuregate `--feature-gates=-pdata.useCustomProtoEncoding` <!-- cspell:ignore MLKEM mlkem --> - `configtls`: Enable X25519MLKEM768 as per draft-ietf-tls-ecdhe-mlkem ([#​13670](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13670)) ##### 🧰 Bug fixes 🧰 - `exporterhelper`: Prevent uncontrolled goroutines in batcher due to a incorrect worker pool behaviour. ([#​13689](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13689)) - `service`: Ensure the insecure configuration is accounted for when normalizing the endpoint. ([#​13691](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13691)) - `configoptional`: Allow validating nested types ([#​13579](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13579)) `configoptional.Optional` now implements `xconfmap.Validator` - `batchprocessor`: Fix UB in batch processor when trying to read bytes size after adding request to pipeline ([#​13698](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13698)) This bug only happens id detailed metrics are enabled and also an async (sending queue enabled) exporter that mutates data is configure. <!-- 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:eyJjcmVhdGVkSW5WZXIiOiI0MS45MS4xIiwidXBkYXRlZEluVmVyIjoiNDEuOTEuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiU2tpcCBDaGFuZ2Vsb2ciLCJkZXBlbmRlbmNpZXMiXX0=--> 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.25 | amd64 |
| Ubuntu | 1.24 | amd64 |
| Ubuntu | 1.25 | 386 |
| Ubuntu | 1.24 | 386 |
| Ubuntu | 1.25 | arm64 |
| Ubuntu | 1.24 | arm64 |
| macOS 13 | 1.25 | amd64 |
| macOS 13 | 1.24 | amd64 |
| macOS | 1.25 | arm64 |
| macOS | 1.24 | arm64 |
| Windows | 1.25 | amd64 |
| Windows | 1.24 | amd64 |
| Windows | 1.25 | 386 |
| Windows | 1.24 | 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.