This Splunk OpenTelemetry Collector release includes changes from the opentelemetry-collector v0.136.0
and the opentelemetry-collector-contrib v0.136.0 releases where appropriate.
🛑 Breaking changes 🛑
- (Contrib)
countconnector
: Upgrade profiles proto to 1.8.0 (#42526) - (Contrib)
internal/kafka
: Disable Kafka client metrics (#42662)
We disable publishing Kafka client metrics to brokers, since they were not
added intentionally and may lead to log spam when the broker does not really
support metrics. We may make this configurable in the future. - (Contrib)
pkg/ottl
: Upgrade profiles proto to 1.8.0 (#42526)
See proto changelog. - (Contrib)
transformprocessor
: Upgrade profiles proto to 1.8.0 (#42526)
💡 Enhancements 💡
- (Splunk)
dotnet-agent
: Update the Splunk Distribution of OpenTelemetry .NET to version 1.11.0 (#6773)
This updates the Zero-code instrumentation for .NET deployed with the
Splunk Distribution of the OpenTelemetry Collector. This version drops support
for .NET 6 which reached end-of-life in November 2024. - (Splunk)
javaagent
: Update Splunk Distribution of OpenTelemetry Java to version 2.20.1 (#6781) - (Core)
debugexporter
: add support for batching (#13791)
The default queue size is 1 - (Core)
configtls
: Add early validation for TLS server configurations to fail fast when certificates are missing instead of failing at runtime. (#13130, #13245) - (Contrib)
prometheusremotewritereceiver
: Adds support to accept METRIC_TYPE_UNSPECIFIED as gauge type (#41840) - (Contrib)
exporter/awss3
: Add S3PartitionTimezone config value to be able to change the timezone used for time-based partitioning (#42319) - (Contrib)
processor/k8sattributesprocessor
: Add support for k8s.cronjob.uid attribute in k8sattributesprocessor (#42557) - (Contrib)
processor/resourcedetection
: Add support for linode cloud in resourcedetectionprocessor (#42543) - (Contrib)
processor/resourcedetection
: Add support for Scaleway host image attributes in the resourcedetectionprocessor (#42682) - (Contrib)
processor/resourcedetection
: Add support for Vultr cloud provider in the resourcedetectionprocessor (#42569) - (Contrib)
spanmetricsconnector
: Supports adding thecollector.instance.id
attribute to data points generated by the spanmetrics connector. (#40400)
This feature currently in alpha stage, user should enable it by feature-gate--feature-gates=+connector.spanmetrics.includeCollectorInstanceID
- (Contrib)
processor/resourcedetection
: Add support for Scaleway cloud provider in the resourcedetectionprocessor (#42664) - (Contrib)
exporter/awss3exporter
: adds configuration field 's3_base_prefix' to be able to set a base path for all S3 file uploads (#42661) - (Contrib)
journaldreceiver
: Enable reading from all journals, including remote ones. A new optionmerge
is added to the configuration. (#39188) - (Contrib)
kafkametricsreceiver
: Implement client reset for recoverable errors in Sarama calls (#41363)
This change implements client reset functionality to address recoverable errors in Sarama calls, such as connection resets and EOF errors. When a recoverable error is encountered, the client is reset, enabling the scraper to reconnect and resume metric collection seamlessly. - (Contrib)
tailsamplingprocessor
: Set atailsampling.cached_decision
attribute on traces that were sampled by the decision cache. (#42535) - (Contrib)
postgresqlreceiver
: Including execution time metric for currently running queries in query samples. (#42429)
The duration for currently running queries is calculated using the query_start time available in pg_stat_activity table. - (Contrib)
receiver/k8scluster
: Add experimental metric for container status reason (#32457) - (Contrib)
countconnector
: Updates the countconnector metric timestamps to use earliest timestamp from batch as start timestamp and latest as timestamp, instead of using timestamp from metric creation time. (#40573)
🧰 Bug fixes 🧰
- (Core)
otelcol
: Fix a potential deadlock during collector shutdown. (#13740) - (Core)
otlpexporter
: fix the validation of unix socket endpoints (#13826) - (Contrib)
receiver/snowflake, receiver/sqlquery
: Fix panic on startup caused by gosnowflakev1.16.0
(#42605)
The solution was to downgrade the dependency version tov1.15.0
.
For more information, refer to the upstream gosnowflake issue - (Contrib)
kafkaexporter
: Fix bug where Kafka exporter ignoredauth.tls
configuration syntax. (#42754) - (Contrib)
extension/storage
: Fix 'recreate' rename file only on panic (#41802)- This recovers from a panic when the bbolt db is corrupted and renames the file when a panic occurs.
- This changes the
recreate
behavior to not rename the file upon every start of the collector.
- (Contrib)
exporter/loadbalancing
: Drop resources if the service routing key does not exist (#41550) - (Contrib)
processor/redaction
: Support redaction of scope level atrributes (#42659) - (Contrib)
splunkenterprisereceiver
: Fix a typo from a previous PR implementing the search artifact size metrics, which has caused errors from parsing empty strings. (#42615) - (Contrib)
signalfxexporter
: Only validate the root_path of the collector ifsync_host_metadata
is enabled. (#42688) - (Contrib)
signalfxexporter
: Add HostID resource attribute to Histogram data in OTLP format (#42905)
Docker Image Manifests:
- Linux (amd64, arm64, ppc64le) and Windows (2019 amd64, 2022 amd64):
quay.io/signalfx/splunk-otel-collector:0.136.0
- digest:
sha256:5f35529ebdf97ee0f0de862e9c70b2c62d0fbe44bef964da4044b0248f5c94fb
- Windows (2019 amd64, 2022 amd64):
quay.io/signalfx/splunk-otel-collector-windows:0.136.0
- digest:
sha256:a50194df684f53d4f79ceb3e7c51f7de3ef076c0ae465e2870907d3c77e2e919