build(deps): Upgrade otelcollector to v0.150.0#1539
Open
azure-monitor-assistant[bot] wants to merge 1 commit intomainfrom
Open
build(deps): Upgrade otelcollector to v0.150.0#1539azure-monitor-assistant[bot] wants to merge 1 commit intomainfrom
azure-monitor-assistant[bot] wants to merge 1 commit intomainfrom
Conversation
Contributor
Author
View build errors |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR upgrades the otelcollector to the latest version available for the opentelemetry-collector and opentelemetry-operator.
It was automatically generated by the GitHub Actions workflow.
The summary of the OSS changelog is below:
Prometheusreceiver Changes
v0.148.0 to v0.150.0
Generated on: 2026-04-28 07:50:17
v0.149.0
receiver/prometheus: Remove the deprecatedreport_extra_scrape_metricsreceiver configuration option and obsolete extra scrape metric feature gates. (#44181)report_extra_scrape_metricsis no longer accepted inprometheusreceiverconfiguration. Control extra scrape metrics through the PromConfig.ScrapeConfigs.ExtraScrapeMetrics setting instead.receiver/prometheus: Add support for reading instrumentation scope attributes fromotel_scope_<attribute-name>labels while feature-gating deprecation ofotel_scope_info. (#41502) Scope attributes are always extracted fromotel_scope_<attribute-name>labels on metrics. Thereceiver.prometheusreceiver.IgnoreScopeInfoMetricfeature gate (alpha, disabled by default) controls only whether the legacyotel_scope_infometric is ignored for scope attribute extraction. When the gate is disabled, both mechanisms coexist to support migration. See the specification change for motivation: prometheus: handle schema URL and scope attributes open-telemetry/opentelemetry-specification#4505receiver/prometheus_remote_write: Count target_info samples in PRW response stats (#47108)Summary
Target-allocator Changes
v0.148.0 to v0.150.0
Generated on: 2026-04-28 07:50:39
0.149.0
auto-instrumentation, opamp, target allocator: Fix Env slice aliasing in Apache HTTPD, Nginx, OpAMP Bridge, and Target Allocator container builders when the spec slice has spare backing-array capacity (#4954)Summary