You've already forked opentelemetry-go
mirror of
https://github.com/open-telemetry/opentelemetry-go.git
synced 2025-11-27 22:49:15 +02:00
c51818f776
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.27.0` -> `v1.28.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.28.0`](https://redirect.github.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v1280v01220) ##### 🛑 Breaking changes 🛑 - `service`: Batch processor telemetry is no longer emitted at "basic" verbosity level ([#​7890](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/7890)) According to the guidelines, basic-level telemetry should be reserved for core Collector APIs. Components such as the batch processor should emit telemetry starting from the "normal" level (which is also the default level). Migration: If your Collector telemetry was set to `level: basic` and you want to keep seeing batch processor-related metrics, consider switching to `level: normal` instead. ##### 💡 Enhancements 💡 - `service`: Add `service.AllowNoPipelines` feature gate to allow starting the Collector without pipelines. ([#​12613](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12613)) This can be used to start with only extensions. - `mdatagen`: Delete generated_status.go if the component type doesn't require it. ([#​12346](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12346)) - `componenttest`: Improve config struct mapstructure field tag checks ([#​12590](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12590)) `remain` tags and `omitempty` tags without a custom field name will now pass validation. - `service`: include component id/type in start error ([#​10426](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/10426)) - `mdatagen`: Add deprecation date and migration guide fields as part of component metadata ([#​12359](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12359)) - `confmap`: Introduce a new feature flag to allow for merging lists instead of discarding the existing ones. ([#​8394](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/8394), [#​8754](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/8754), [#​10370](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/10370)) You can enable this option via the command line by running following command: otelcol --config=main.yaml --config=extra_config.yaml --feature-gates=-confmap.enableMergeAppendOption - `zpagesextension`: Add expvar handler to zpages extension. ([#​11081](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/11081)) ##### 🧰 Bug fixes 🧰 - `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. - `service`: do not attempt to register process metrics if they are disabled ([#​12098](https://redirect.github.com/open-telemetry/opentelemetry-collector/issues/12098)) <!-- 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> Co-authored-by: Damien Mathieu <42@dmathieu.com>