Bump the otel group with 7 updates

[dependabot]

Bumps the otel group with 7 updates:

Package	From	To
go.opentelemetry.io/collector/component	1.36.0	1.36.1
go.opentelemetry.io/collector/component/componenttest	0.130.0	0.130.1
go.opentelemetry.io/collector/config/configcompression	1.36.0	1.36.1
go.opentelemetry.io/collector/config/confighttp	0.130.0	0.130.1
go.opentelemetry.io/collector/confmap	1.36.0	1.36.1
go.opentelemetry.io/collector/confmap/xconfmap	0.130.0	0.130.1
go.opentelemetry.io/collector/pdata	1.36.0	1.36.1

Updates go.opentelemetry.io/collector/component from 1.36.0 to 1.36.1

Release notes

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

v1.36.1/v0.130.1

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

End User Changelog

🧰 Bug fixes 🧰

• service: Fixes bug where internal metrics are emitted with an unexpected suffix in their names when users configure service::telemetry::metrics::readers with Prometheus. (#13449) See more details on open-telemetry/opentelemetry-go#7039

API Changelog

v1.36.0/v0.130.0

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

End User Changelog

❗ Known Issues ❗

• Due to a bug in the internal telemetry Prometheus exporter, if you are configuring an internal telemetry Prometheus exporter, the collector's internal metrics will be emitted with an unexpected suffix in its name. For example, the metric otelcol_exporter_sent_spans__spans__total instead of otelcol_exporter_sent_spans_total. The workaround is to manually configure without_units: true in your internal telemetry Prometheus exporter config

  service:
    telemetry:
      metrics:
        readers:
          - pull:
              exporter:
                prometheus:
                  host: 0.0.0.0
                  port: 8888
                  without_units: true

  If you are using the collector's default internal telemetry Prometheus exporter for exporting internal metrics you are unaffected.

This issue has been fixed in v0.130.1. If you are using the Collector builder, please use the builder v0.130.1 to fix this issue.

🛑 Breaking changes 🛑

• exporter/otlp: Remove deprecated batcher config from OTLP, use queuebatch (#13339)

💡 Enhancements 💡

• exporterhelper: Enable items and bytes sizers for persistent queue (#12881)
• exporterhelper: Refactor persistent storage size backup to always record it. (#12890)
• exporterhelper: Add support to configure a different Sizer for the batcher than the queue (#13313)

... (truncated)

Changelog

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

v1.36.1/v0.130.1

No API-only changes in this release.

Commits

• d588ee2 [chore] Prepare release v0.130.1/v1.36.1 (#13441)
• df6428d [service] Bump otel-go Prometheus module to v0.59.1 (#13449)
• b23a7c9 Revert "Downgrade otel-go" (#13443)
• d82267d Downgrade otel-go (#13429)
• See full diff in compare view

Updates go.opentelemetry.io/collector/component/componenttest from 0.130.0 to 0.130.1

Changelog

Sourced from go.opentelemetry.io/collector/component/componenttest's changelog.

v1.36.1/v0.130.1

No API-only changes in this release.

Commits

• d588ee2 [chore] Prepare release v0.130.1/v1.36.1 (#13441)
• df6428d [service] Bump otel-go Prometheus module to v0.59.1 (#13449)
• b23a7c9 Revert "Downgrade otel-go" (#13443)
• d82267d Downgrade otel-go (#13429)
• See full diff in compare view

Updates go.opentelemetry.io/collector/config/configcompression from 1.36.0 to 1.36.1

Release notes

Sourced from go.opentelemetry.io/collector/config/configcompression's releases.

v1.36.1/v0.130.1

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

End User Changelog

🧰 Bug fixes 🧰

• service: Fixes bug where internal metrics are emitted with an unexpected suffix in their names when users configure service::telemetry::metrics::readers with Prometheus. (#13449) See more details on open-telemetry/opentelemetry-go#7039

API Changelog

v1.36.0/v0.130.0

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

End User Changelog

❗ Known Issues ❗

• Due to a bug in the internal telemetry Prometheus exporter, if you are configuring an internal telemetry Prometheus exporter, the collector's internal metrics will be emitted with an unexpected suffix in its name. For example, the metric otelcol_exporter_sent_spans__spans__total instead of otelcol_exporter_sent_spans_total. The workaround is to manually configure without_units: true in your internal telemetry Prometheus exporter config

  service:
    telemetry:
      metrics:
        readers:
          - pull:
              exporter:
                prometheus:
                  host: 0.0.0.0
                  port: 8888
                  without_units: true

  If you are using the collector's default internal telemetry Prometheus exporter for exporting internal metrics you are unaffected.

This issue has been fixed in v0.130.1. If you are using the Collector builder, please use the builder v0.130.1 to fix this issue.

🛑 Breaking changes 🛑

• exporter/otlp: Remove deprecated batcher config from OTLP, use queuebatch (#13339)

💡 Enhancements 💡

• exporterhelper: Enable items and bytes sizers for persistent queue (#12881)
• exporterhelper: Refactor persistent storage size backup to always record it. (#12890)
• exporterhelper: Add support to configure a different Sizer for the batcher than the queue (#13313)

... (truncated)

Changelog

Sourced from go.opentelemetry.io/collector/config/configcompression's changelog.

v1.36.1/v0.130.1

No API-only changes in this release.

Commits

• d588ee2 [chore] Prepare release v0.130.1/v1.36.1 (#13441)
• df6428d [service] Bump otel-go Prometheus module to v0.59.1 (#13449)
• b23a7c9 Revert "Downgrade otel-go" (#13443)
• d82267d Downgrade otel-go (#13429)
• See full diff in compare view

Updates go.opentelemetry.io/collector/config/confighttp from 0.130.0 to 0.130.1

Changelog

Sourced from go.opentelemetry.io/collector/config/confighttp's changelog.

v1.36.1/v0.130.1

No API-only changes in this release.

Commits

• d588ee2 [chore] Prepare release v0.130.1/v1.36.1 (#13441)
• df6428d [service] Bump otel-go Prometheus module to v0.59.1 (#13449)
• b23a7c9 Revert "Downgrade otel-go" (#13443)
• d82267d Downgrade otel-go (#13429)
• See full diff in compare view

Updates go.opentelemetry.io/collector/confmap from 1.36.0 to 1.36.1

Release notes

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

v1.36.1/v0.130.1

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

End User Changelog

🧰 Bug fixes 🧰

• service: Fixes bug where internal metrics are emitted with an unexpected suffix in their names when users configure service::telemetry::metrics::readers with Prometheus. (#13449) See more details on open-telemetry/opentelemetry-go#7039

API Changelog

v1.36.0/v0.130.0

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

End User Changelog

❗ Known Issues ❗

• Due to a bug in the internal telemetry Prometheus exporter, if you are configuring an internal telemetry Prometheus exporter, the collector's internal metrics will be emitted with an unexpected suffix in its name. For example, the metric otelcol_exporter_sent_spans__spans__total instead of otelcol_exporter_sent_spans_total. The workaround is to manually configure without_units: true in your internal telemetry Prometheus exporter config

  service:
    telemetry:
      metrics:
        readers:
          - pull:
              exporter:
                prometheus:
                  host: 0.0.0.0
                  port: 8888
                  without_units: true

  If you are using the collector's default internal telemetry Prometheus exporter for exporting internal metrics you are unaffected.

This issue has been fixed in v0.130.1. If you are using the Collector builder, please use the builder v0.130.1 to fix this issue.

🛑 Breaking changes 🛑

• exporter/otlp: Remove deprecated batcher config from OTLP, use queuebatch (#13339)

💡 Enhancements 💡

• exporterhelper: Enable items and bytes sizers for persistent queue (#12881)
• exporterhelper: Refactor persistent storage size backup to always record it. (#12890)
• exporterhelper: Add support to configure a different Sizer for the batcher than the queue (#13313)

... (truncated)

Changelog

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

v1.36.1/v0.130.1

No API-only changes in this release.

Commits

• d588ee2 [chore] Prepare release v0.130.1/v1.36.1 (#13441)
• df6428d [service] Bump otel-go Prometheus module to v0.59.1 (#13449)
• b23a7c9 Revert "Downgrade otel-go" (#13443)
• d82267d Downgrade otel-go (#13429)
• See full diff in compare view

Updates go.opentelemetry.io/collector/confmap/xconfmap from 0.130.0 to 0.130.1

Changelog

Sourced from go.opentelemetry.io/collector/confmap/xconfmap's changelog.

v1.36.1/v0.130.1

No API-only changes in this release.

Commits

• d588ee2 [chore] Prepare release v0.130.1/v1.36.1 (#13441)
• df6428d [service] Bump otel-go Prometheus module to v0.59.1 (#13449)
• b23a7c9 Revert "Downgrade otel-go" (#13443)
• d82267d Downgrade otel-go (#13429)
• See full diff in compare view

Updates go.opentelemetry.io/collector/pdata from 1.36.0 to 1.36.1

Release notes

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

v1.36.1/v0.130.1

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

End User Changelog

🧰 Bug fixes 🧰

• service: Fixes bug where internal metrics are emitted with an unexpected suffix in their names when users configure service::telemetry::metrics::readers with Prometheus. (#13449) See more details on open-telemetry/opentelemetry-go#7039

API Changelog

v1.36.0/v0.130.0

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

End User Changelog

❗ Known Issues ❗

• Due to a bug in the internal telemetry Prometheus exporter, if you are configuring an internal telemetry Prometheus exporter, the collector's internal metrics will be emitted with an unexpected suffix in its name. For example, the metric otelcol_exporter_sent_spans__spans__total instead of otelcol_exporter_sent_spans_total. The workaround is to manually configure without_units: true in your internal telemetry Prometheus exporter config

  service:
    telemetry:
      metrics:
        readers:
          - pull:
              exporter:
                prometheus:
                  host: 0.0.0.0
                  port: 8888
                  without_units: true

  If you are using the collector's default internal telemetry Prometheus exporter for exporting internal metrics you are unaffected.

This issue has been fixed in v0.130.1. If you are using the Collector builder, please use the builder v0.130.1 to fix this issue.

🛑 Breaking changes 🛑

• exporter/otlp: Remove deprecated batcher config from OTLP, use queuebatch (#13339)

💡 Enhancements 💡

• exporterhelper: Enable items and bytes sizers for persistent queue (#12881)
• exporterhelper: Refactor persistent storage size backup to always record it. (#12890)
• exporterhelper: Add support to configure a different Sizer for the batcher than the queue (#13313)

... (truncated)

Changelog

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

v1.36.1/v0.130.1

No API-only changes in this release.

Commits

• d588ee2 [chore] Prepare release v0.130.1/v1.36.1 (#13441)
• df6428d [service] Bump otel-go Prometheus module to v0.59.1 (#13449)
• b23a7c9 Revert "Downgrade otel-go" (#13443)
• d82267d Downgrade otel-go (#13429)
• See full diff in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions