ymotongpoo / opentelemetry-collector-extra

This project is a sample of OpenTelemetry Collector receiver and exporter to Discord
Apache License 2.0
2 stars 0 forks source link

fix(deps): update module go.opentelemetry.io/collector/receiver to v0.90.0 #30

Closed renovate[bot] closed 7 months ago

renovate[bot] commented 7 months ago

Mend Renovate logo banner

This PR contains the following updates:

Package Type Update Change
go.opentelemetry.io/collector/receiver require minor v0.89.0 -> v0.90.0

Release Notes

open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector/receiver) ### [`v0.90.0`](https://togithub.com/open-telemetry/opentelemetry-collector/blob/HEAD/CHANGELOG.md#v100v0900) [Compare Source](https://togithub.com/open-telemetry/opentelemetry-collector/compare/v0.89.0...v0.90.0) ##### 🛑 Breaking changes 🛑 - `service`: To remain backwards compatible w/ the metrics generated today, otel generated metrics will be generated without the `_total` suffix ([#​7454](https://togithub.com/open-telemetry/opentelemetry-collector/issues/7454)) - `service`: use WithNamespace instead of WrapRegistererWithPrefix ([#​8988](https://togithub.com/open-telemetry/opentelemetry-collector/issues/8988)) Using this functionality in the otel prom exporter fixes a bug where the target_info was prefixed as otelcol_target_info previously. ##### 💡 Enhancements 💡 - `exporter/debug`: Change default `verbosity` from `normal` to `basic` ([#​8844](https://togithub.com/open-telemetry/opentelemetry-collector/issues/8844)) This change has currently no effect, as `basic` and `normal` verbosity share the same behavior. This might change in the future though, with the `normal` verbosity being more verbose than it currently is (see [https://github.com/open-telemetry/opentelemetry-collector/issues/7806](https://togithub.com/open-telemetry/opentelemetry-collector/issues/7806)). This is why we are changing the default to `basic`, which is expected to stay at the current level of verbosity (one line per batch). - `exporterhelper`: Fix shutdown logic in persistent queue to not require consumers to be closed first ([#​8899](https://togithub.com/open-telemetry/opentelemetry-collector/issues/8899)) - `confighttp`: Support proxy configuration field in all exporters that support confighttp ([#​5761](https://togithub.com/open-telemetry/opentelemetry-collector/issues/5761)) ##### 🧰 Bug fixes 🧰 - `exporterhelper`: Fix invalid write index updates in the persistent queue ([#​8115](https://togithub.com/open-telemetry/opentelemetry-collector/issues/8115))

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.



This PR has been generated by Mend Renovate. View repository job log here.