You've already forked opentelemetry-go
mirror of
https://github.com/open-telemetry/opentelemetry-go.git
synced 2025-11-29 23:07:45 +02:00
5002ee39c7
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [go.opentelemetry.io/collector/pdata](https://redirect.github.com/open-telemetry/opentelemetry-collector) | `v1.36.1` -> `v1.37.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.37.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1370v01310) ##### 🛑 Breaking changes 🛑 - `confighttp`: Move `confighttp.framedSnappy` feature gate to beta. ([#​10584](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/10584)) ##### 💡 Enhancements 💡 - `exporter/debug`: Move to alpha stability except profiles ([#​13487](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13487)) - `exporterhelper`: Enable `exporter.PersistRequestContext` feature gate by default. ([#​13437](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13437)) Request context is now preserved by default when using persistent queues. Note that Auth extensions context is not propagated through the persistent queue. - `pdata`: Use pdatagen to generate marshalJSON without using gogo proto jsonpb. ([#​13450](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13450)) - `otlpreceiver`: Remove usage of gogo proto which uses reflect.Value.MethodByName. Removes one source of disabling DCE. ([#​12747](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12747)) - `exporterhelper`: Fix metrics split logic to consider metrics description into the size. ([#​13418](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13418)) - `service`: New pipeline instrumentation now differentiates internal failures from downstream errors ([#​13234](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13234)) With the telemetry.newPipelineTelemetry feature gate enabled, the "received" and "produced" metrics related to a component now distinguish between two types of errors: - "outcome = failure" indicates that the component returned an internal error; - "outcome = refused" indicates that the component successfully emitted data, but returned an error coming from a downstream component processing that data. - `pdata`: Remove usage of text/template from pdata, improves DCE. ([#​12747](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12747)) - `architecture`: New Tier 3 platform riscv64 allowing the collector to be built and distributed for this platform. ([#​13462](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13462)) ##### 🧰 Bug fixes 🧰 - `exporterhelper`: Prevents the exporter for being stuck when telemetry data is bigger than batch.max\_size ([#​12893](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12893)) - `mdatagen`: Fix import paths for mdatagen component ([#​13069](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13069)) - `otlpreceiver`: Error handler correctly fallbacks to content type ([#​13414](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13414)) - `pdata/pprofiles`: Fix profiles JSON unmarshal logic for originalPayload. The bytes have to be base64 encoded. ([#​13483](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13483)) - `xpdata`: Fix unmarshaling JSON for entities, add e2e tests to avoid this in the future. ([#​13480](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13480)) - `service`: Downgrade dependency of prometheus exporter in OTel Go SDK ([#​13429](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13429)) This fixes the bug where collector's internal metrics are emitted with an unexpected suffix in their names when users configure the service::telemetry::metrics::readers with Prometheus - `service`: Revert Default internal metrics config now enables `otel_scope_` labels ([#​12939](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12939), [#​13344](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13344)) Reverting change temporarily due to prometheus exporter downgrade. This unfortunately re-introduces the bug that instrumentation scope attributes cause errors in Prometheus exporter. Se[http://github.com/open-telemetry/opentelemetry-collector/issues/12939](http://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12939)39 for details. - `builder`: Remove undocumented handling of `DIST_*` environment variables replacements ([#​13335](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/13335)) <!-- 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 becomes conflicted, 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:eyJjcmVhdGVkSW5WZXIiOiI0MS40My41IiwidXBkYXRlZEluVmVyIjoiNDEuNDMuNSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiU2tpcCBDaGFuZ2Vsb2ciLCJkZXBlbmRlbmNpZXMiXX0=--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>