This Splunk OpenTelemetry Collector release includes changes from the opentelemetry-collector v0.143.0
and the opentelemetry-collector-contrib v0.143.0 releases where appropriate.
🛑 Breaking changes 🛑
- (Contrib)
receiver/prometheus: Remove deprecateduse_start_time_metricandstart_time_metric_regexconfiguration options. (#44180)
Theuse_start_time_metricandstart_time_metric_regexconfiguration options have been removed after being deprecated in v0.142.0.
Users who have these options set in their configuration will experience collector startup failures after upgrading.
To migrate, remove these configuration options and use themetricstarttimeprocessor instead for equivalent functionality.
💡 Enhancements 💡
- (Splunk)
packaging: Update Splunk OpenTelemetry .NET agent to v1.12.0 (#7032) - (Splunk)
packaging: Update Splunk OpenTelemetry Java agent to v2.23.0 (#7031) - (Splunk)
packaging: Update Splunk OpenTelemetry Node.js agent to v4.3.0 (#7048) - (Contrib)
pkg/ottl: AddBoolfunction for converting values to boolean (#44770) - (Contrib)
receiver/awscloudwatch: Add support for filtering log groups by account ID. (#38391) - (Contrib)
receiver/awscontainerinsightreceiver: Component type name renamed fromawscontainerinsightreceivertoawscontainerinsight, controlled by feature gatereceiver.awscontainerinsightreceiver.useNewTypeName. (#44052)
When the feature gate is enabled, the receiver uses the new type nameawscontainerinsightinstead ofawscontainerinsightreceiver.
To enable the new type name, use:--feature-gates=+receiver.awscontainerinsightreceiver.useNewTypeName. - (Contrib)
receiver/filelog: gzip files are auto detected based on their header (#39682) - (Contrib)
receiver/oracledb: Add stored procedure information to logs for top queries and query samples. (#44764)
Thedb.server.top_queryevent now includesoracledb.procedure_id,oracledb.procedure_name, andoracledb.procedure_typeattributes.
Thedb.server.query_sampleevent now includesoracledb.procedure_id,oracledb.procedure_name, andoracledb.procedure_typeattributes. - (Contrib)
receiver/postgresql: Addedservice.instance.idresource attribute for metrics and logs (#43907)
service.instance.idis enabled by default. - (Contrib)
receiver/postgresql: Add trace propagation support (#44868)
Whenpostgresql.application_namecontains a valid W3Ctraceparent, emitteddb.server.query_samplelogs includetrace_idandspan_idfor correlation. - (Contrib)
receiver/prometheus: Addreceiver.prometheusreceiver.RemoveReportExtraScrapeMetricsConfigfeature gate to disable thereport_extra_scrape_metricsconfig option. (#44181)
When enabled, thereport_extra_scrape_metricsconfiguration option is ignored, and extra scrape metrics are
controlled solely by thereceiver.prometheusreceiver.EnableReportExtraScrapeMetricsfeature gate.
This mimics Prometheus behavior where extra scrape metrics are controlled by a feature flag. - (Contrib)
receiver/windowseventlog: Improved performance of the Windows Event Log Receiver (#43195)
Previously, the Windows Event Log Receiver could only process events up to 100 messages per second with default settings.
This was because the receiver would read at mostmax_readsmessages within each configuredpoll_interval, even if
additional events were already available.
This restriction has been removed. Thepoll_intervalparameter behaves as described in the documentation:
Thepoll_intervalparameter now only takes effect after all current events have been read.
For users who prefer the previous behavior, a new configuration option,max_events_per_poll, has been introduced. - (Contrib)
receiver/windowseventlog: Add parsing for Version and Correlation event fields. (#45018)
🧰 Bug fixes 🧰
- (Contrib)
connector/count: Basic config should emit default metrics (#41769) - (Contrib)
exporter/kafka: Wrap non-retriable errors from franzgo with consumererror::permanent (#44918) - (Contrib)
exporter/loadbalancing: Fix k8s resolver parsing so loadbalancing exporter works with service FQDNs (#44472) - (Contrib)
receiver/azureeventhub: Make storage of new azeventhub library backward compatible and fix checkpoint starting at earliest when storage is enabled (#44461) - (Contrib)
receiver/fluentforward: Ensure all established connections are properly closed on shutdown in the fluentforward receiver. The shutdown process now reliably closes all active connections. (#44433)- Fixes shutdown behavior so that all existing connections are closed cleanly.
- Adds tests to verify proper connection closure.
- (Contrib)
receiver/kafka: Fix deprecated field migration logic for metrics, traces, and profiles topic configuration (#45215)
Fixed bug where deprecatedtopicandexclude_topicfields for metrics, traces, and profiles
were incorrectly checking logs configuration instead of their respective signal type's configuration.
This prevented proper migration from deprecated fields unless logs.topics was empty.
Also fixed validation error message typo for traces.exclude_topic and corrected profiles validation
to check ExcludeTopic fields instead of Topic fields. - (Contrib)
receiver/sqlserver: Collect query metrics for long running queries (#44984) - (Contrib)
receiver/tcpcheck: Fix the unit of thetcpcheck.errormetric fromerrortoerrors(#45092)
Docker Image Manifests:
- Linux (amd64, arm64, ppc64le) and Windows (2019 amd64, 2022 amd64):
quay.io/signalfx/splunk-otel-collector:0.143.0- digest:
sha256:a401f831737c8f53d5bc5288ce22b8a0141bc39e2d8b9b6cdd0aa7437850776c