Update OpenTelemetry Collector (main)#1819
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
added
the
v3.x
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1819 +/- ##
==========================================
- Coverage 85.18% 85.17% -0.02%
==========================================
Files 105 105
Lines 13759 13759
==========================================
- Hits 11721 11719 -2
- Misses 1514 1516 +2
Partials 524 524 see 1 file with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/main-opentelemetry-collector
branch
2 times, most recently
from
July 15, 2026 15:58
db93d21 to
926bb77
Compare
karensantana
approved these changes
Jul 15, 2026
renovate
Bot
force-pushed
the
renovate/main-opentelemetry-collector
branch
11 times, most recently
from
July 17, 2026 10:27
1c0327e to
1fbbec4
Compare
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/main-opentelemetry-collector
branch
from
July 17, 2026 13:09
1fbbec4 to
9ccb81b
Compare
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
1 participant
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 contains the following updates:
v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v1.59.0→v1.62.0v0.152.0→v0.156.0v0.152.0→v0.156.0v1.59.0→v1.62.0v1.53.0→v1.62.0v1.58.0→v1.62.0v1.53.0→v1.62.0v1.53.0→v1.62.0v1.53.0→v1.62.0v0.152.0→v0.156.0v1.59.0→v1.62.0v0.153.0→v0.156.0v1.58.0→v1.62.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v1.58.0→v1.62.0v1.58.0→v1.62.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v1.59.0→v1.62.0v1.59.0→v1.62.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v1.58.0→v1.62.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0v0.152.0→v0.156.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
open-telemetry/opentelemetry-collector-contrib (github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter)
v0.156.0Compare Source
🛑 Breaking changes 🛑
pkg/fileconsumer: Move feature gate filelog.protobufCheckpointEncoding to beta and keep it enabled by default (#49387)receiver/oracledb: Enhanced Oracle SQL query plan details with runtime execution statistics. (#49329)This change requires the collector user to have access to V$SQL_PLAN_STATISTICS_ALL. Existing deployments that only grant access to V$SQL_PLAN
may experience query plan collection failures until the appropriate privileges are granted.
SQL query plan details are now retrieved from V$SQL_PLAN_STATISTICS_ALL instead of V$SQL_PLAN. Since V$SQL_PLAN_STATISTICS_ALL is a superset of V$SQL_PLAN,
this change is backward compatible with respect to the emitted plan detail fields while enabling collection of additional runtime execution statistics,
including OUTPUT_ROWS, LAST_OUTPUT_ROWS, LAST_ELAPSED_TIME, LAST_CR_BUFFER_GETS, LAST_CU_BUFFER_GETS, STARTS, and LAST_STARTS.
🚩 Deprecations 🚩
connector/routing: Deprecate therequestcontext in favor ofotelcol.*OTTL paths. (#44762)The routing connector
requestcontext andrequest["key"]condition syntax are deprecated in favor ofotelcol.client.metadata["key"][0]for HTTP/client metadata andotelcol.grpc.metadata["key"][0]for gRPC metadata.These paths work in all signal contexts and are documented in the OTelCol OTTL context.
A warning is logged when the
requestcontext is still configured.exporter/datadog: Theexporter.datadogexporter.metricremappingdisabledfeature gate no longer has any effect when the serializer exporter path is active (the default). Useexporter.datadogexporter.DisableAllMetricRemappingto disable metric remapping. (#49320)See DataDog/datadog-agent#51232.
receiver/aws_cloudwatch: rename toaws_cloudwatchwith deprecated aliasawscloudwatch(#45339)🚀 New components 🚀
processor/dynamic_sampling: Add dynamic sampling processor for adaptive trace sampling with W3C TraceState rate encoding. (#48898)💡 Enhancements 💡
cmd/opampsupervisor: Make the OpAMP Supervisor logger encoding configurable so it can emit console (plain-text) logs as well as JSON (#47532)connector/routing: Add OTTL context inference support to routing connector. (#38080)The routing connector now supports OTTL context inference, allowing users to write clearer routing conditions using
context-qualified paths. Instead of relying on implicit context resolution, users can explicitly specify which
context's attributes they want to access (e.g.,
resource.attributes["env"]orspan.attributes["http.method"]).Unqualified paths like
attributes["key"]continue to work and default to the resource context for backward compatibility.exporter/alibabacloud_logservice: Addsecurity_token(STS) support alongside AK/SK; preserve ECS role/token-file fallback. (#48624)When
security_tokenis provided in the exporter configuration the SDK isconfigured to use static STS credentials via the provider. The existing
ecs_ram_roleandtoken_file_pathbehavior remains the higher-priorityauthentication method and is unchanged.
exporter/clickhouse: Add experimental support for the profiles signal (#49304)exporter/datadog: Emitotel.datadog_exporter.metrics.running.fargate{task_arn}for AWS ECS Fargate workloads so that each workload has its own metric. (#49042)Host-based workloads continue to use
otel.datadog_exporter.metrics.running{host}unchanged.otel.datadog_exporter.metrics.runningwill no longer be tagged withtask_arn. Fargate workloads will only useotel.datadog_exporter.metrics.running.fargate{task_arn}.exporter/datadog: Fargate workloads now emit a dedicatedotel.datadog_exporter.metrics.running.fargatemetric tagged withtask_arninstead of sharingotel.datadog_exporter.metrics.runningwith host-based workloads. (#49320)Host-based workloads continue to emit
otel.datadog_exporter.metrics.running{host}unchanged.See DataDog/datadog-agent#52203.
exporter/elasticsearch: Support routing from data_stream attributes defined as scope attributes (#49306)extension/azure_auth: Promote the Azure Authenticator extension to beta stability. (#48521)extension/file_storage: Addedmax_sizesupport to the filestorage extension to cap per-component database growth. (#38620)extension/sigv4auth: Add automatic service detection for CloudWatch OTLP metrics endpoint (monitoring..amazonaws.com) (#48738)pkg/translator/pprof: reduce allocations in sample conversion (#49452)processor/transform: Addexemplarcontext support to the transform processor, allowingmetric_statementsto read and modify exemplar fields on metric datapoints. (#49022)receiver/aws_lambda: Add support for AWS configuration overrides for static credentials (#49163)receiver/faro: Emit per-payload counters for ingested Faro logs, measurements, exceptions, and events (#48071)Adds
otelcol_faro_log_ingested_total,otelcol_faro_measurement_ingested_total,otelcol_faro_exception_ingested_total, andotelcol_faro_event_ingested_total. Eachcounter is incremented by the number of entries in the corresponding
payload section after the request body is parsed.
receiver/mongodb: Add Query Sample collection to the MongoDB receiver, emitting adb.server.query_samplelog event for each currently executing operation. (#48573)Samples are collected via
$currentOp, with idle connections and administrative commandsfiltered out. Each event includes obfuscated query text and operation metadata.
The
logssignal is atdevelopmentstability; attribute names may change until OTeldb.server.query_sampleconventions stabilize. Themetricssignal remains atbeta.receiver/oracledb: Addservice.nameandservice.namespaceopt-in resource attributes and allow overriding any resource attribute viaoverride_value. (#47088)receiver/oracledb: Add workload analysis metrics related to scans, enqueue, LOB, parse, sort, cursor, and session activity (#48808)Adds fourteen new opt-in metrics (disabled by default):
oracledb.call.count,oracledb.call.recursive.cpu.timeoracledb.cursor.cache.hits,oracledb.cursor.cache.size,oracledb.cursor.openoracledb.db.timeoracledb.enqueue.operationsoracledb.lob.operationsoracledb.parse.cpu.time,oracledb.parse.elapsed.timeoracledb.scan.count,oracledb.scan.table.rowsoracledb.sort.operations,oracledb.sort.rowsNo new SQL queries are issued; the existing v$sysstat scrape already returns
all required rows, so the receiver adds no additional load on the monitored
Oracle instance.
receiver/oracledb: Add buffer cache and Database Writer (DBWR) metrics (#49061)receiver/oracledb: Add redo log metrics (#49060)receiver/postgresql: Add default service.name and service.namespace resource attributes (#47087)Both attributes default to enabled: false. When enabled, service.name
defaults to unknown_service:postgresql and service.namespace defaults
to an empty string. Additionally, override_value is enabled for all
resource attributes, allowing users to set custom values via
override_value in the collector configuration.
receiver/postgresql: Adds blocking session and lock attributes todb.server.query_sampleevents for PostgreSQL blocking session detection. Blocking attributes are always emitted (empty string / 0 when not blocked). (#49028)New attributes under postgresql.blocking.*: postgresql.blocking.pids, postgresql.blocking.start_time,
postgresql.blocking.wait_duration, postgresql.blocking.lock.mode, postgresql.blocking.lock.type,
postgresql.blocking.lock.relation, postgresql.blocking.transaction.start_time.
postgresql.blocking.pids contains the full array of blocking PIDs from pg_blocking_pids() (e.g. {5121,5122}).
postgresql.blocking.start_time uses pg_locks.waitstart (PostgreSQL 14+) to record when the lock wait began. waitstart is stable for the full duration of the wait — it is set once when the lock wait starts and is not affected by blockers joining or leaving.
postgresql.blocking.transaction.start_time provides a UTC timestamp (RFC3339) from xact_start representing when the transaction started, predating the lock contention itself.
Idle-in-transaction blocker sessions (holding locks without an active request) are captured via pg_blocking_pids subquery in the WHERE clause.
All blocking attributes are always present on every db.server.query_sample event; empty string / 0 values indicate no active blocking.
Requires PostgreSQL 14 or later.
receiver/prometheus: Promotereceiver.prometheusreceiver.IgnoreScopeInfoMetricfeature gate to beta. (#47312)The
otel_scope_infometric is now ignored for scope attribute extraction by default.To temporarily restore the previous behavior, disable the feature gate with
--feature-gates=-receiver.prometheusreceiver.IgnoreScopeInfoMetric.receiver/sqlserver: Add access methods and buffer pool metrics (#49182)Adds the following metrics, all disabled by default:
sqlserver.access.scan.ratesqlserver.extent.operation.ratesqlserver.ghost_record.skipped.ratesqlserver.page.allocation.ratesqlserver.page.compression.ratesqlserver.page.read_ahead.ratesqlserver.scan_point.revalidation.ratesqlserver.worktable.cache.hit_ratioreceiver/syslog: Add support for RFC6587 Octet Counting framing with RFC3164 message format. (#45216)🧰 Bug fixes 🧰
connector/routing: Fix duplicate routing table entry handling to correctly ignore duplicates instead of overwriting the original route (#44762)Previously, when duplicate routing table entries were encountered, the warning message indicated that the duplicate
would be ignored, but in fact the original entry was being overwritten by the duplicate.
This fix ensures that duplicates are properly ignored and the original route's consumer is preserved.
exporter/awsxray: Use local service name for Consumer local root segment names, falling back to resource service name when aws.local.service is absent. (#43432)Consumer spans promoted to X-Ray Segments after #42633 were named
using the span (operation) name instead of the local service name.
The fix mirrors the existing Server span naming behavior.
exporter/datadog: Compress the metric sketches payload with gzip in the legacy metric API client, matching the metric series payload. Previously sketches were sent uncompressed, increasing egress for distribution/histogram metrics. (#49313)exporter/datadog: Fix CPU core count fields (cpu_cores,cpu_logical_processors) missing from host metadata payloads for remote hosts in OTel gateway topologies. (#49320)CPU data arrives via
system.cpu.physical.count/system.cpu.logical.countmetrics and was neverforwarded to the host metadata reporter in the serializer exporter path.
See DataDog/datadog-agent#51893.
exporter/datadog: Fix host metadata collection no longer aborts the entire batch when one resource fails; errors are accumulated and processing continues for remaining resources (#49153)See DataDog/datadog-agent#51893.
exporter/datadog: Metrics from the Podman stats receiver now report the correct Datadog metric origin (opentelemetry_collector_podmanreceiver) instead of falling through toopentelemetry_collector_unknown. (#49320)See DataDog/datadog-agent#52594.
exporter/file: Fix path traversal vulnerability on Windows when using grouping file exporter (#49194)exporter/opensearch: Preserve LogRecord EventName field in all log encoding modes. (#49314)extension/datadog: Skip cloud metadata source provider probe when hostname is already set in config, avoiding spurious GCP metadata server requests on non-GCP hosts. (#49241)pkg/translator/pprof: Wrong conversion of labels from pprof to OTLP profiles (#49449)processor/cumulativetodelta: Align reset detection and dropping on histograms and exponential histograms (#48278)Histograms and exponential histograms where there is a drop in total count or on any bucket counts are now treated as a reset and dropped.
processor/cumulativetodelta: Fix non-deterministic order of valid metric types in error messages for invalidmetric_typesconfig values. (#49120)processor/gen_ai_normalizer: Fix OpenInference message normalization for flattened indexed attributes (#48421)Reconstruct gen_ai.input.messages and gen_ai.output.messages from
OpenInference flattened indexed span attributes
(llm.{input,output}_messages.N.message.*).
processor/k8s_attributes: Fix cache key memory leak in k8sattributesprocessor when a Pod's IP is missing or cleared from the delete event (#48986)When a Pod is deleted, if its IP address is missing or already cleared from the delete event status,
the processor now looks up the cached pod by its UID to retrieve the stored IP and correctly queue
all associated keys for deletion.
processor/resource_detection: Fix Docker resource detection failing to start when optional resource attributes are disabled, including container attributes when the hostname does not match a Docker container name. (#46275)processor/spanpruning: Fix non-deterministic depth of preserved outlier spans by grouping leaves and parents by tree depth, so same-named ancestors at different depths are no longer merged. (#49323)receiver/aws_cloudwatch: Fix logs being skipped when AWS pagination returns an empty page (#48577)receiver/github: Capture the datapoint timestamp per repository instead of once at scrape start, so per-repository metrics carry a timestamp close to when each repository was observed. (#48497)receiver/prometheus: Prometheus API server config/targets stay in sync with Target Allocator changing it if both are enabled. (#48040)Previously, the API server config and targets did not get the updates from the Target Allocator.
receiver/tcp_log: Fix tcp input operator emitting partial log data after a connection read error whenone_log_per_packetis enabled (#49199)Previously, if a TCP connection was reset mid-read while
one_log_per_packetwas set to true, the partial buffer was still processed and emitted as a log
entry. Now the read error causes the message to be discarded instead.
v0.155.0Compare Source
🛑 Breaking changes 🛑
all: Movecmd/schemagento opentelemetry-collector asgo.opentelemetry.io/collector/cmd/schemagen. (#14543)The
schemagenCLI now lives in the opentelemetry-collector repository. Existingmake schemagenandmake generate-schemastargets continue to work — they now invoke the tool viago run go.opentelemetry.io/collector/cmd/schemagen@latest. Override the newSCHEMAGEN_PKGvariableto pin a specific release. Downstream users that previously imported
github.com/open-telemetry/opentelemetry-collector-contrib/cmd/schemagenmust update their import pathto
go.opentelemetry.io/collector/cmd/schemagen.exporter/signalfx: Stop calculating per-corecpu.*metrics disabled by default. (#49247)The default transformations still create aggregate CPU metrics. However, per-core
cpu.*metrics which are disabled by default aren't produced by the default transformations anymore.This change doesn't have any impact unless any of
cpu.*metrics are explicitly enabled with thecpuattribute in signalfx exporter with configuration like this:In that case, the same metrics can be restore by applying the transform processor the following way:
exporter/signalfx: Stop calculatingcpu.utilization_per_coredisabled by default. (#49243)The exporter still creates the aggregate
cpu.utilizationmetric by default. However,cpu.utilization_per_corewhich is disabled by default isn't produced by the default transformations anymore.This change doesn't have any impact unless
cpu.utilization_per_coremetric is explicitly enabled in signalfx exporter with configuration like this:In that case, the same metric can be restore by applying the transform processor the following way:
pkg/fileconsumer: Remove stable gate filelog.decompressFingerprint (#48980)processor/k8s_attributes: Remove deprecated gate k8sattr.labelsAnnotationsSingular.allow (#48977)processor/tail_sampling: Remove stable gate processor.tailsamplingprocessor.disableinvertdecisions (#48976)receiver/datadog: Enhance Datadog logs support (#49102)Logs are now translated to the OpenTelemetry data model instead of being emitted as flat string
attributes: the record timestamp/observed timestamp are set (converting Datadog epoch-milliseconds
to nanoseconds),
statusmaps to the severity number/text,hostname/serviceand knownddtagsare promoted to resource attributes, and
dd.trace_id/dd.span_idpopulateTraceID/SpanIDfortrace correlation (reconstructing full 128-bit trace ids from
_dd.p.tidthe same way spans do).A new
logs::decode_json_messageoption (enabled by default) expands JSON-encoded log messagesforwarded by the Datadog Agent, lifting their reserved fields and attributes into the log record.
receiver/datadog: Enable thereceiver.datadogreceiver.Enable128BitTraceIDfeature gate by default (#49103)The gate is promoted from alpha to beta (on by default), so spans reconstruct full 128-bit trace ids
from
_dd.p.tidand emit OpenTelemetry-native trace ids that correlate with other OpenTelemetryservices. Disable the gate to fall back to 64-bit (zero-padded) trace ids.
receiver/mongodb: Minimum supported MongoDB version is now 4.4. (#49248)MongoDB 4.0 reached end-of-life in April 2022 and is no longer supported by the Go MongoDB driver v2.7.0+,
which raised the minimum required wire protocol version. Users still on MongoDB 4.0 must upgrade to at
least MongoDB 4.4 before upgrading to this version of the receiver.
receiver/oracledb: Setdb.namespaceto database name and addoracle.db.serviceattribute on query sample and top query events. (#48996)On
db.server.query_sampleanddb.server.top_queryevents,db.namespacenow reports the database name instead of the Oracle service
name. The service name moves to the new
oracle.db.serviceattribute.🚩 Deprecations 🚩
connector/service_graph: Deprecate the legacy servicegraph connector latency metric names and millisecond latency unit feature gates, and mark the virtual node feature gate as stable. (#49215)receiver/flink_metrics: Rename receiver type fromflinkmetricstoflink_metrics(#45339)receiver/splunk_enterprise: Rename receiver type fromsplunkenterprisetosplunk_enterprise(#45339)🚀 New components 🚀
processor/cardinality_guardian: Promote the cardinalityguardian processor to alpha stability and include it in the contrib distribution. (#47368)receiver/active_directory_inv: Add Windows Active Directory Inventory receiver for collecting inventory data from Active Directory. (#48733)💡 Enhancements 💡
cmd/opampsupervisor: Allow Supervisor to configure its managed OpAMP extension config to include Collector resource attributes (#48536)connector/routing: Addconnector.routing.defaultErrorModeIgnorefeature gate to change defaulterror_modefrompropagatetoignore(#48418)exporter/awsxray: Migrate http.status_code (v1.25.0) semantic convention to http.response.status_code (v1.40.0) (#45058)exporter/awsxray: Migrate container.image.tag (v1.21.0) semantic convention to container.image.tags (v1.40.0) (#45057)exporter/azure_blob: Add support forgzipandzstdcompression to the Azure Blob Storage exporter. Thecompressionconfig option is now supported and the appropriate file extension is added to blob names. (#45338)This mirrors the compression support added to the Google Cloud Storage exporter in commit
6fd0eb6. Compression is applied to the marshaled data before upload (including append blocks). Tests and documentation updated.exporter/elasticsearch: Extract span events as separate ECS log documents in ECS mapping mode (#49181)In ECS mapping mode, exception span events are routed to
logs-apm.error-*and all otherspan events to
logs-apm.app.<service>-*, with OTel exception attributes mapped totheir correct nested ECS paths (
error.exception.type,error.exception.message,error.stack_trace).exporter/file: Add feature gate for native file-level compression in file exporter (#44077)A new alpha feature gate
exporter.file.nativeCompressionenables native file-level zstd compression.When enabled, the exporter produces standard
.zstfiles that can be decompressed withzstd -d,unlike the legacy per-message compression format which requires custom tooling.
exporter/google_cloud_storage: Adduniverse_domainconfig option to support Sovereign Google Cloud regions. Setting this field passesoption.WithUniverseDomainto the underlying Google API client. (#48924)exporter/google_cloud_storage: Addresource_attrs_to_gcsto partition objects by a resource attribute value. (#49136)When
resource_attrs_to_gcs.prefixis set, the value of the given resource attribute(read from the first resource of each batch) is inserted as a partition path segment
between
bucket.partition.prefixand the time-basedbucket.partition.format, mirroringthe
awss3exporterresource_attrs_to_s3behavior.exporter/googlecloudpubsub: Adduniverse_domainconfig option to support Sovereign Google Cloud regions. Setting this field passesoption.WithUniverseDomainto the underlying Google API client. (#48924)exporter/kafka: Addproducer.max_broker_write_bytesconfig (#47492)The maximum size of a single write to a broker was previously fixed at the underlying
franz-go
Configuration
📅 Schedule: (UTC)
🚦 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.