This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.134.0.
🛑 Breaking changes 🛑
instrumentation
: Reduce Java and .Net auto-instrumentation resource attributes (#2006)
This change limits the resource attributes added to the telemetry data emitted by Java and .Net instrumentation libraries to the attributes generated by theContainer
andEnvironment
resource providers.
To enable additional resource providers, updatevalues.yaml
environment variableOTEL_JAVA_ENABLED_RESOURCE_PROVIDERS
for Java, or setOTEL_DOTNET_AUTO_{DETECTOR}_RESOURCE_DETECTOR_ENABLED
for .Net.
For more information see: https://github.com/signalfx/splunk-otel-collector-chart/blob/main/docs/auto-instrumentation-install.md#4-Resource-Attributeschart
: Remove deprecatedimage.fluentd.initContainer
configuration option. (#1995)
This option was deprecated in version 0.38.0. The same splunk/fluentd-hec image is now used in init containers.chart
: Remove deprecatedextraAttributes.podLabels
configuration option. (#1994)
This option was deprecated in version 0.38.0 in favor ofextraAttributes.fromLabels
.
See migration guide: https://github.com/signalfx/splunk-otel-collector-chart/blob/main/UPGRADING.md#0371-to-0380
💡 Enhancements 💡
clusterReceiver
: Enable k8s.container.status.last_terminated_reason resource attribute for container metrics (#1968)agent
: Update prometheus receiver configuration for CoreDNS in OpenShift to use secure endpoint and service account token (#2009)- This aligns with OpenShift's default CoreDNS daemonset setup with kube-rbac-proxy which doesn't expose metrics over HTTP.
operator
: Bump java to v2.19.0 in helm-charts/splunk-otel-collector/values.yaml (#1991)Target Allocator
: Update version tov0.132.0
(#2019)
Please review the configtargetAllocator.config.collector_namespace
introduced in this version which is set to the release namespace by default.
🧰 Bug fixes 🧰
agent
: Introducing:logsCollection.containers.multilineConfigs.maxNumOfLinesToCombine
.
This new field allows to specify max number of lines which will be combined in log entry for multiline log configuration.
In some cases, multiline logs with more than 1000 lines were split into multiple events.
(#2012)chart
: Fix per-pod configuration of 'metricsIndex' and 'sourcetype' config for Splunk Platform metrics via annotations (#1977)