search

honeycombio / opentelemetry-collector-configs

Honeycomb Metrics-flavored OpenTelemetry Collector configuration
Apache License 2.0
7 stars 4 forks source link

maint(deps): bump go.opentelemetry.io/collector/consumer from 0.73.0 to 0.82.0 in /timestampprocessor #99

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 1 year ago

Bumps go.opentelemetry.io/collector/consumer from 0.73.0 to 0.82.0.

Release notes

Sourced from go.opentelemetry.io/collector/consumer's releases.

cmd/builder/v0.82.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.82.0

v0.82.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.82.0

🛑 Breaking changes 🛑

  • service: Enable configuration of collector telemetry through prometheus reader (#7641) These options are still experimental. To enable them, users must enable both telemetry.useOtelForInternalMetrics and telemetry.useOtelWithSDKConfigurationForInternalTelemetry feature gates. This change updates metric_readers to readers to align with the configuration working group.

  • service: Remove experimental metric_readers.args and metric_reader.type config options. (#7641) These options were experimental and did not have any effect on the configuration of the collector's telemetry. The change aligns the configuration with the latest iteration of the configuration json schema, which may still change in the future.

💡 Enhancements 💡

  • service: Add support for exporting internal metrics to the console (#7641) Internal collector metrics can now be exported to the console using the otel-go stdout exporter.

  • service: Add support for interval and timeout configuration in periodic reader (#7641)

  • service: Add support for span processor configuration for internal traces (#8106) These options are still experimental. To enable them, users must enable both telemetry.useOtelForInternalMetrics and telemetry.useOtelWithSDKConfigurationForInternalTelemetry feature gates.

  • service: Add support for OTLP export for internal metrics (#7641) Internal collector metrics can now be exported via OTLP using the otel-go otlpgrpc and otlphttp exporters.

  • scraperhelper: Adding optional timeout field to scrapers (#7951)

  • otlpreceiver: Add http url paths per signal config options to otlpreceiver (#7511)

  • otlphttpexporter: Add support for trailing slash in endpoint URL (#8084) URLs like http://localhost:4318/ will now be treated as if they were http://localhost:4318

🧰 Bug fixes 🧰

  • connector: Fix connector validation (#7892) Validation of connectors was too aggressive such that a connector that was used in any combination of unsupported roles would fail. Instead, validation should pass as long as each use of the connector has a supported corresponding use.

cmd/builder/v0.81.0

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.81.0

v0.81.0

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/consumer's changelog.

v1.0.0-rcv0014/v0.82.0

🛑 Breaking changes 🛑

  • service: Enable configuration of collector telemetry through prometheus reader (#7641) These options are still experimental. To enable them, users must enable both telemetry.useOtelForInternalMetrics and telemetry.useOtelWithSDKConfigurationForInternalTelemetry feature gates. This change updates metric_readers to readers to align with the configuration working group.

  • service: Remove experimental metric_readers.args and metric_reader.type config options. (#7641) These options were experimental and did not have any effect on the configuration of the collector's telemetry. The change aligns the configuration with the latest iteration of the configuration json schema, which may still change in the future.

💡 Enhancements 💡

  • service: Add support for exporting internal metrics to the console (#7641) Internal collector metrics can now be exported to the console using the otel-go stdout exporter.

  • service: Add support for interval and timeout configuration in periodic reader (#7641)

  • service: Add support for span processor configuration for internal traces (#8106) These options are still experimental. To enable them, users must enable both telemetry.useOtelForInternalMetrics and telemetry.useOtelWithSDKConfigurationForInternalTelemetry feature gates.

  • service: Add support for OTLP export for internal metrics (#7641) Internal collector metrics can now be exported via OTLP using the otel-go otlpgrpc and otlphttp exporters.

  • scraperhelper: Adding optional timeout field to scrapers (#7951)

  • otlpreceiver: Add http url paths per signal config options to otlpreceiver (#7511)

  • otlphttpexporter: Add support for trailing slash in endpoint URL (#8084) URLs like http://localhost:4318/ will now be treated as if they were http://localhost:4318

🧰 Bug fixes 🧰

  • connector: Fix connector validation (#7892) Validation of connectors was too aggressive such that a connector that was used in any combination of unsupported roles would fail. Instead, validation should pass as long as each use of the connector has a supported corresponding use.

v0.81.0

🛑 Breaking changes 🛑

  • service: Remove 'service.connectors' featuregate (#7952)

💡 Enhancements 💡

... (truncated)

Commits


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 11 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.