v0.146.0

This Splunk OpenTelemetry Collector release includes changes from the opentelemetry-collector v0.146.0
and the opentelemetry-collector-contrib v0.146.0 releases where appropriate.

🛑 Breaking changes 🛑

• (Core) all: Increase minimum Go version to 1.25 (#14567)
• (Contrib) all: Increase minimum Go version to 1.25 (#46000)
• (Contrib) processor/k8s_attributes: Introduce semantic conventions compliant feature gate pair for k8sattributes processor (#44693)
  • Added processor.k8sattributes.EmitV1K8sConventions feature gate to enable stable semantic convention attributes (singular form: k8s.<workload>.label.<key> and k8s.<workload>.annotation.<key>)
  • Added processor.k8sattributes.DontEmitV0K8sConventions feature gate to disable legacy non-compliant attributes (plural form: k8s.<workload>.labels.<key> and k8s.<workload>.annotations.<key>)
  • Both feature gates are in alpha stage and disabled by default
  • The processor now validates that legacy attributes cannot be disabled without enabling stable attributes
  • Deprecated k8sattr.labelsAnnotationsSingular.allow feature gate in favor of the new semconv-compliant gates (will be removed in v0.150.0)
  • During migration period, both legacy and stable attributes can coexist when EmitV1K8sConventions is enabled but DontEmitV0K8sConventions is not
• (Contrib) processor/resourcedetection: Promote processor.resourcedetection.propagateerrors feature gate to Stable and is now always enabled (#44609)
• (Contrib) receiver/hostmetrics: process.context_switches will now properly count context switches for all threads. (#36804)
  Previously, only the lead thread's context switches would be counter. We believe this was a bug,
  but are marking it as a breaking change since the values of these metrics may change drastically
  compared to previous expectations. However, the values you get now will be more accurate than before.
• (Contrib) receiver/kafkametrics: receiver.kafkametricsreceiver.UseFranzGo feature gate is now in Beta stage and enabled by default (#44600)

🚩 Deprecations 🚩

• (Contrib) processor/k8s_attributes: Rename k8sattributes processor to k8s_attributes processor and add deprecated alias k8sattributes. (#45894)
• (Contrib) receiver/kubeletstats: The GCEPersistentDisk, AWSElasticBlockStore, and Glusterfs have been deprecated as these have been depreacted in k8s (#40477)
  K8s documentation for the three deprecated volume types is below:
  • GCEPersistentDisk: https://v1-32.docs.kubernetes.io/docs/concepts/storage/volumes/#gcepersistentdisk
  • AWSElasticBlockStore: https://v1-32.docs.kubernetes.io/docs/concepts/storage/volumes/#awselasticblockstore
  • Glusterfs: https://v1-32.docs.kubernetes.io/docs/concepts/storage/volumes/#glusterfs
• (Contrib) receiver/signalfx: This receiver is deprecated. Please use the OTLP receiver instead (#46079)
  This component will be removed in a future release.
• (Contrib) receiver/wavefront: Deprecate the wavefront receiver (#46087)
  There is no replacement for the wavefront receiver.
  Wavefront is EOL: https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/release-announcements/0/25153

💡 Enhancements 💡

• (Splunk) packaging: Update Splunk OpenTelemetry Java agent to v2.25.0 (#7249)
• (Splunk) packaging: Update JMX metrics gatherer to v1.53.0 (#7082)
• (Core) all: Add detailed failure attributes to exporter send_failed metrics at detailed telemetry level. (#13956)
  The otelcol_exporter_send_failed_{spans,metric_points,log_records} metrics now include
  failure attributes when telemetry level is Detailed: error.type (OpenTelemetry semantic convention
  describing the error class) and error.permanent (indicates if error is permanent/non-retryable).
  The error.type attribute captures gRPC status codes (e.g., "Unavailable", "ResourceExhausted"),
  standard Go context errors (e.g., "canceled", "deadline_exceeded"),
  and collector-specific errors (e.g., "shutdown").
  This enables better alerting and debugging by providing standardized error classification.
• (Core) exporter/debug: Add output_paths configuration option to control output destination when use_internal_logger is false. (#10472)
  When use_internal_logger is set to false, the debug exporter now supports configuring the output destination via the output_paths option.
  This allows users to send debug exporter output to stdout, stderr, or a file path.
  The default value is ["stdout"] to maintain backward compatibility.
• (Contrib) exporter/signalfx: Preserve 'k8s.service.' property names on the 'k8s.service.uid' dimension instead of converting them to 'kubernetes_service_' prefix. (#46291)
• (Contrib) exporter/file: Add support for rotation when group_by is enabled in file exporter (#43143)
• (Contrib) exporter/googlecloudstorage: Add compression support for Google Cloud Storage exporter (#45337)
  The Google Cloud Storage exporter now supports compression of log data before uploading to GCS.
  Supported compression algorithms: gzip and zstd.
• (Contrib) exporter/kafka: Add conn_idle_timeout configuration option to control when idle connections are not reused and may be closed. (#45321)
  Defaults to 9 minutes.
• (Contrib) pkg/ottl: Add IsInCIDR function to check if IP belongs to given list of CIDR (#42215)
• (Contrib) pkg/stanza: Ensure filter operator does not split batches of entries (#42391)
• (Contrib) processor/filter: Introduces inferred context conditions for filtering (#37904)
  Introduces three new top-level config fields [metric_conditions, log_conditions, trace_conditions].
  A user can supply OTTL conditions for each without needing to supply context.
• (Contrib) processor/k8s_attributes: Added container.image.tags resource attribute with feature gate controls according to OpenTelemetry semantic conventions. (#44589)
• (Contrib) receiver/hostmetrics: Add optional system.memory.linux.shared metric (#32712)
  This metric reports shared memory usage, including tmpfs filesystems,
  System V shared memory, and POSIX shared memory. Currently only available
  on Linux systems due to platform-specific data availability.
  This corresponds to the Shmem field in /proc/meminfo.
• (Contrib) receiver/k8s_cluster: Add opt-in service metrics derived from k8s Service and EndpointSlice API (#45620)
  New metrics (disabled by default):
  • k8s.service.endpoint.count: Number of endpoints by condition (ready, serving, terminating), address type, and zone
  • k8s.service.load_balancer.ingress.count: Number of load balancer ingress points assigned to the service
    New resource attributes:
  • k8s.service.name: The k8s service name
  • k8s.service.uid: The k8s service uid
  • k8s.service.type: The k8s service type
  • k8s.service.traffic_distribution: The service's traffic routing preference
  • k8s.service.publish_not_ready_addresses: Whether the service publishes endpoints before pods are ready
• (Contrib) receiver/kafka: Add conn_idle_timeout configuration option to control when idle connections are not reused and may be closed. (#45321)
  Defaults to 9 minutes.
• (Contrib) receiver/mongodb: Add support for auth_mechanism, auth_source, and auth_mechanism_properties configuration options (#40686)
  Users can now specify the authentication mechanism (e.g., SCRAM-SHA-256, GSSAPI, MONGODB-AWS), auth source database,
  and auth mechanism properties when connecting to MongoDB instances. This is particularly useful for MongoDB servers
  that require specific authentication mechanisms. For example, GSSAPI (Kerberos) may require SERVICE_NAME, and
  MONGODB-AWS may require AWS_SESSION_TOKEN when using tempo...

v0.145.1

This Splunk OpenTelemetry Collector release includes changes from the opentelemetry-collector v0.145.0
and the opentelemetry-collector-contrib v0.145.0 releases where appropriate.

🛑 Breaking changes 🛑

• (Splunk) autoinstrumentation: Remove the example of using SystemD to configure zero-config instrumentation (#7192)
  In preparation of adopting the injector, remove the SystemD approach to injecting environment variables.

💡 Enhancements 💡

• (Splunk) otel-collector: Add support for RHEL 10, CentOS 10, Oracle Linux 10, and Rocky Linux 10 (#7195)
• (Splunk) Windows: Add a Windows ARM64 binary distribution to the released files (#7203)

Docker Image Manifests:

• Linux (amd64, arm64, ppc64le) and Windows (2019 amd64, 2022 amd64):
  • quay.io/signalfx/splunk-otel-collector:0.145.1
  • digest: sha256:d14ec076415b0029b6e053e8a55b7186a6e3af16d588c5e470ba5dc2e9b36e22

v0.145.0

This Splunk OpenTelemetry Collector release includes changes from the opentelemetry-collector v0.145.0
and the opentelemetry-collector-contrib v0.145.0 releases where appropriate.

🛑 Breaking changes 🛑

• (Splunk) installer.ps1: Remove FluentD support from PowerShell installer (#7137)
  FluentD support is removed after deprecation period.
  Prefer using the filelog receiver for log ingestion.
• (Splunk) rpm/deb: Remove FluentD installation and configuration (#7138)
  FluentD is removed from debian and RPM packages after a period of deprecation.
  Please use the filelog receiver instead to ingest logs.
• (Contrib) pkg/translator/azure: Updated OpenTelemetry semantic conversion to the latest version 1.38.0 in azure pkg. (#44801)
• (Contrib) processor/resourcedetection: Promote processor.resourcedetection.removeGCPFaasID feature gate to Stable and is now always enabled (#45797)
  The faas.id attribute is replaced by the faas.instance attribute.
• (Contrib) receiver/azure_event_hub: Upgrade receiver.azureeventhubreceiver.UseAzeventhubs feature gate to stable. (#45527)
• (Contrib) receiver/kafka: Replace StartTracesOp/EndTracesOp with StartProfilesOp/EndProfilesOp in profilesHandler. (#45601)
  The span name generated by the profiles receiver now uses the ProfilesReceived suffix instead of TraceDataReceived.
• (Contrib) receiver/prometheus: Promote receiver.prometheusreceiver.RemoveReportExtraScrapeMetricsConfig feature gate to beta (#44181)
  The report_extra_scrape_metrics configuration option is now ignored by default. Extra scrape metrics are instead controlled by the receiver.prometheusreceiver.EnableReportExtraScrapeMetrics feature gate and the Prometheus upstream configuration available in promconfig (either globally or per-scrape config).

🚩 Deprecations 🚩

• (Splunk) collectd/opcache: Deprecate collectd/opcache (#7140)
  Deprecate the collectd/opcache monitor.
  It will be removed on or after April 2026.
  There is no direct replacement for this monitor. Please consider using the PHP SDK for OpenTelemetry moving forward.
• (Splunk) collectd/php-fpm: Deprecate collectd/php-fpm (#7140)
  Deprecate the collectd/php-fpm monitor.
  It will be removed on or after April 2026.
  There is no direct replacement for this monitor. Please consider using the PHP SDK for OpenTelemetry moving forward.
• (Splunk) collectd/protocols: Deprecate collectd/protocols (#7170)
  Please use the hostmetrics receiver with the network scraper instead.
• (Splunk) includeconfigsource: Deprecate delete_files setting (#7141)
  Deprecate the delete_files include configsource setting, to be removed on or after April 2026.
• (Splunk) smartagent/postgresql: Deprecate the postgresql monitor (#7142)
  This monitor is deprecated and will be removed on or after April 2026.
  Please use the postgresql receiver instead.
• (Contrib) receiver/azure_event_hub: Rename azureeventhub receiver to azure_event_hub and add deprecated alias azureeventhub (#45637)
• (Contrib) receiver/jmx: Deprecate the jmxreceiver to avoid running Java subprocesses in the Collector and prevent container-based deployments from requiring a Java runtime. (#45740)
• (Contrib) receiver/mongodb_atlas: Rename mongodbatlas receiver to mongodb_atlas and add deprecated alias mongodbatlas (#45652)

🚀 New components 🚀

• (Splunk) receiver/memcached: Add memcached receiver to the distribution (#7171)
  See README
• (Splunk) receiver/saphana: Add SAP HANA receiver (#7162)
  See README
• (Splunk) receiver/systemd: Add systemd receiver (#7143)
• (Splunk) receiver/yanggrpc: Add YANG/gRPC receiver (#7161)
  Add new YANG/gRPC receiver

💡 Enhancements 💡

• (Splunk) packaging: Update bundled OpenJDK to 11.0.30_7 (#7172)
• (Splunk) packaging: Update Splunk OpenTelemetry Java agent to v2.24.0 (#7092)
• (Splunk) packaging: Update Splunk OpenTelemetry .NET agent to v1.13.0 (#7132)
• (Core) pkg/scraperhelper: ScraperID has been added to the logs for metrics, logs, and profiles (#14461)
• (Contrib) connector/routing: Add move/copy support in routing connector (#45061)
• (Contrib) exporter/googlecloudstorage: Add support for exporting traces to Google Cloud Storage (#44945)
• (Contrib) exporter/signalfx: Add support for processing entity events from logs pipeline to send as dimension property updates (#27890)
  The SignalFx exporter now supports processing entity events (e.g., from k8s_cluster receiver)
  received via the logs pipeline and converting them to dimension property updates. This provides
  an alternative to the metadata_exporters option and enables consistent metadata handling.
  This feature is behind the exporter.signalfx.consumeEntityEvents feature gate (disabled by default).
• (Contrib) extension/oauth2client: Support jwt-bearer grant-type (RFC7523) (#44314)
• (Contrib) extension/opamp: This change adds support for the OpAMP AcceptsRestartCommand capability. The implementation for this capability sends a SIGHUP signal to restart the collector which will reload the config on startup. (#45056)
  This functionality is behind a feature gate (extension.opampextension.RemoteRestarts) that defaults to disabled. The SIGHUP signal does not work on Windows systems, but might later be updated to use the SIGUSR2 signal.
• (Contrib) internal/coreinternal: Improve performance of hashing function for attraction package. (#45211)
• (Contrib) pkg/fileconsumer: Open files on Windows with FILE_SHARE_DELETE mode (#32037)
• (Contrib) pkg/ottl: Added generic path to get/set span flags in OTTL trace span context. (#34739)
• (Contrib) pkg/ottl: Introducing delete_index function for deleting items from an existing array (#43098)
• (Contrib) pkg/stanza: Ensure recombine operator does not split batches of entries (#42392)
• (Contrib) pkg/stanza: Ensure container operator does not split batches of entries (#42389)
• (Contrib) pkg/stanza: Ensure syslog operator does not split batches of entries (#42394)
• (Contrib) pkg/translator/azurelogs: Add support for all Activity Logs categories (#44871)
  Includes support for the Alert, Autoscale, Policy, Recommendation, Security, ServiceHealth, and ResourceHealth categories.
• (Contrib) processor/k8sattributes: Added processor-specific observability metrics: otelcol.k8s.pod.association with status, pod_identifier, and otelcol.signal attributes ([#44587](open-telemetry/opentelemetry-collector-contrib#44587...

v0.144.0

This Splunk OpenTelemetry Collector release includes changes from the opentelemetry-collector v0.144.0 and the opentelemetry-collector-contrib v0.144.0 releases where appropriate.

🛑 Breaking changes 🛑

• (Splunk) appmesh: Remove appmesh plugin (#7106). Use the statsd receiver instead.
• (Splunk) cadvisor: This plugin is removed at the end of its deprecation period. (#7086). Please use the prometheus receiver instead.
• (Splunk) collectd/chrony: This plugin is removed at the end of its deprecation period. (#7090). Please use the chronyreceiver instead.
• (Splunk) collectd/cpu: Remove the collectd/cpu monitor (#7097). The collectd/cpu monitor is removed in favor of the cpu monitor.
• (Splunk) collectd/couchbase: This plugin is removed at the end of its deprecation period. (#7077). The collectd/couchbase plugin is removed. Please use the prometheus receiver instead. See https://docs.couchbase.com/server/current/manage/monitor/set-up-prometheus-for-monitoring.html for more information.
• (Splunk) chocolatey: Remove FluentD from choco installer (#7125). FluentD is no longer installable as part of the collector using chocolatey. Please use native OpenTelemetry log receivers such as filelog receiver instead.
• (Splunk) installer: Remove FluentD support (#7123). Please use native OTel receivers instead (e.g. the filelog receiver).
• (Splunk) msi: remove FluentD support (#7124). Use native receivers such as the filelog receiver instead.
• (Splunk) haproxy: This plugin is removed at the end of its deprecation period. (#7088). Please use the haproxyreceiver instead.
• (Splunk) heroku: Remove deprecated plugin (#7102). Please use https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor#heroku instead.
• (Splunk) collectd/jenkins: This plugin is removed at the end of its deprecation period. (#7076). Please see https://plugins.jenkins.io/opentelemetry/ to enable OpenTelemetry signals.
• (Splunk) kubelet-stats: This plugin is removed at the end of its deprecation period. (#7086). Please use the kubeletstats receiver instead.
• (Splunk) kubelet-metrics: This plugin is removed at the end of its deprecation period. (#7081). Please use the kubeletstats receiver moving forward.
• (Splunk) mongodbatlas: Remove deprecated monitor (#7100). Please use the mongodbatlasreceiver instead. See https://help.splunk.com/en/splunk-observability-cloud/manage-data/available-data-sources/supported-integrations-in-splunk-observability-cloud/opentelemetry-receivers/mongodb-atlas-receiver
• (Splunk) nagios: Remove nagios monitor (#7099)
• (Splunk) collectd/nginx: This plugin is removed at the end of its deprecation period. (#7091). Please use the nginx receiver instead.
• (Splunk) collectd/rabbitmq: This plugin is removed at the end of its deprecation period. (#7078). The collectd/rabbitmq smart agent monitor is removed. Please follow this documentation to set up the RabbitMQ receiver.
• (Splunk) collectd/redis: This plugin is removed at the end of its deprecation period. (#7079). The collectd/redis smart agent monitor is removed. Please follow this documentation to set up the Redis receiver.
• (Splunk) windows-legacy: This monitor is removed at the end of its deprecation period. (#7098). The smart agent monitor windows-legacy is removed. Please use the hostmetrics receiver and the windowsperfcounters receiver moving forward.
• (Splunk) collectd/spark: This plugin is removed at the end of its deprecation period. (#7080). Please use the apache spark receiver instead.
• (Splunk) collectd/statsd: This plugin is removed at the end of its deprecation period. (#7085). The smart agent monitor collectd/statsd is removed, please use the statsdreceiver instead.
• (Splunk) statsd: Remove deprecated plugin (#7106). Use the statsd receiver instead.
• (Core) pkg/exporterhelper: Change verbosity level for otelcol_exporter_queue_batch_send_size metric to detailed. (#14278)
• (Core) pkg/service: Remove deprecated telemetry.disableHighCardinalityMetrics feature gate. (#14373)
• (Core) pkg/service: Remove deprecated service.noopTracerProvider feature gate. (#14374)
• (Contrib) exporter/kafka: Remove Sarama producer implementation (#44565). The Sarama-based Kafka producer has been removed from kafkaexporter. Feature gate exporter.kafkaexporter.UseFranzGo has also been removed since Franz-go is now the only supported Kafka client.
• (Contrib) processor/tail_sampling: The deprecated invert decisions are disabled by default. (#44132). Drop policies should be used instead of invert decisions for explicitly not sampling a trace. If the deprecated behavior is required while migrating to drop policies, disable the processor.tailsamplingprocessor.disableinvertdecisions feature gate.
• (Contrib) receiver/kafka: Remove Sarama consumer implementation and default_fetch_size configuration option (#44564). The Sarama-based Kafka consumer has been removed from kafkareceiver. The default_fetch_size configuration option has also been removed as it was only used by the Sarama consumer. Feature gate receiver.kafkareceiver.UseFranzGo has also been removed since Franz-go is now the only supported Kafka client.

🚩 Deprecations 🚩

• (Splunk) collectd/apache: Deprecate the collectd/apache plugin (#7089). Please use the apachereceiver instead.
• (Splunk) collectd/cpufreq: Deprecate the collectd/cpufreq plugin (#7096). Please use the [hostmetrics receiver](https://help.splunk.com/en/splunk-observability-cloud/manage-data/available-data-sources/supported-integrations-in-splunk-observability-cloud/applic...

Technical addon for the Splunk distribution of the OpenTelemetry Collector v1.11.0

Release notes in progress.

v0.143.0

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 deprecated use_start_time_metric and start_time_metric_regex configuration options. (#44180)
  The use_start_time_metric and start_time_metric_regex configuration 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 the metricstarttime processor 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: Add Bool function 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 from awscontainerinsightreceiver to awscontainerinsight, controlled by feature gate receiver.awscontainerinsightreceiver.useNewTypeName. (#44052)
  When the feature gate is enabled, the receiver uses the new type name awscontainerinsight instead of awscontainerinsightreceiver.
  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)
  The db.server.top_query event now includes oracledb.procedure_id, oracledb.procedure_name, and oracledb.procedure_type attributes.
  The db.server.query_sample event now includes oracledb.procedure_id, oracledb.procedure_name, and oracledb.procedure_type attributes.
• (Contrib) receiver/postgresql: Added service.instance.id resource attribute for metrics and logs (#43907)
  service.instance.id is enabled by default.
• (Contrib) receiver/postgresql: Add trace propagation support (#44868)
  When postgresql.application_name contains a valid W3C traceparent, emitted db.server.query_sample logs include trace_id and span_id for correlation.
• (Contrib) receiver/prometheus: Add receiver.prometheusreceiver.RemoveReportExtraScrapeMetricsConfig feature gate to disable the report_extra_scrape_metrics config option. (#44181)
  When enabled, the report_extra_scrape_metrics configuration option is ignored, and extra scrape metrics are
  controlled solely by the receiver.prometheusreceiver.EnableReportExtraScrapeMetrics feature 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 most max_reads messages within each configured poll_interval, even if
  additional events were already available.
  This restriction has been removed. The poll_interval parameter behaves as described in the documentation:
  The poll_interval parameter 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 deprecated topic and exclude_topic fields 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 the tcpcheck.error metric from error to errors (#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

Technical addon for the Splunk distribution of the OpenTelemetry Collector v1.10.0

Release notes in progress.

v0.142.0

This Splunk OpenTelemetry Collector release includes changes from the opentelemetry-collector v0.142.0
and the opentelemetry-collector-contrib v0.142.0 releases where appropriate.

🛑 Breaking changes 🛑

• (Splunk) configserver: Removed the deprecated localhost config endpoint (http://localhost:55554/debug/configz) and its related environment variables. (#6984)
  The collector's default configuration files enable the zpages extension and the respective debug/expvarz endpoint,
  by default at http://localhost:55679/debug/expvarz. This endpoint provides a JSON map containing the collector
  configuration details. The keys splunk.config.initial and splunk.config.effective within this map
  hold, respectively, the initial and effective YAML configurations as strings.
  To retrieve the configuration in YAML format using this endpoint, you can use the following commands:
  On Windows PowerShell 5.1:

  (Invoke-WebRequest http://localhost:55679/debug/expvarz).Content | ConvertFrom-Json | Select-Object -ExpandProperty splunk.config.effective

  On Bash (with curl and jq):

  curl http://localhost:55679/debug/expvarz --silent | jq -r '.["splunk.config.initial"]'

• (Contrib) exporter/prometheusremotewrite: Updated to Remote Write 2.0 spec rc.4, requiring Prometheus 3.8.0 or later as the receiving endpoint. (#44861)
  The upstream Prometheus library updated the Remote Write 2.0 protocol from rc.3 to rc.4 in
  prometheus/prometheus#17411. This renamed CreatedTimestamp to StartTimestamp and moved it
  from the TimeSeries message to individual Sample and Histogram messages. This is a
  wire-protocol incompatibility, so if you are exporting to a Prometheus server, you must upgrade
  it to version 3.8.0 or later to receive data from this exporter.
• (Contrib) extension/googlecloudlogentry_encoding: Parse External Application Load Balancer logs into log record attributes instead of placing it in the body as is. (#44438)
• (Contrib) pkg/stanza: Allow max_batch_size of 0 for unlimited batching in recombine operator (#43982)
  The recombine operator now supports setting max_batch_size: 0 to disable batch size limits.
  This allows unlimited batching, letting entries be combined based only on max_log_size and matching conditions.
  If you have max_batch_size: 0 in your config and want to keep the behavior unchanged, change the configuration to max_batch_size: 1.
• (Contrib) processor/cumulativetodelta: Change default max_staleness from 0 (infinite) to 1 hour (#44427)
  The processor now defaults to a max_staleness of 1 hour instead of 0 (infinite retention).
  This prevents unbounded memory growth in long-running collector instances, especially when tracking metrics with high cardinality or frequently changing attribute values.
  To restore the previous behavior of infinite retention, explicitly set max_staleness: 0 in your configuration.
• (Contrib) processor/resourcedetection: Promote processor.resourcedetection.propagateerrors feature gate to beta (#44609)
  Note: Splunk OTel Collector has disabled this feature gate by default to prevent unexpected crashes due to resource detection errors
• (Contrib) processor/resourcedetection: Remove deprecated attributes configuration option (#44610)
• (Contrib) receiver/dockerstats: Upgrades default Docker API version to 1.44 to be compatible with recent Docker Engine versions. (#44279)
  Users requiring an older Docker API version can set the api_version in the docker stats receiver config. The minimum supported API level is not changed, only default.
• (Contrib) receiver/filelog: Move filelog.decompressFingerprint to stable stage (#44570)
• (Contrib) receiver/prometheus: Promote the receiver.prometheusreceiver.RemoveStartTimeAdjustment feature gate to stable and remove in-receiver metric start time adjustment in favor of the metricstarttime processor, including disabling the created-metric feature gate. (#44180)
  Previously, users could disable the RemoveStartTimeAdjustment feature gate to temporarily keep the legacy start time adjustment behavior in the Prometheus receiver.
  With this promotion to stable and bounded registration, that gate can no longer be disabled; the receiver will no longer set StartTime on metrics based on process_start_time_seconds, and users should migrate to the metricstarttime processor for equivalent functionality.
  This change also disables the receiver.prometheusreceiver.UseCreatedMetric feature gate, which previously used the <metric>_created series to derive start timestamps for counters, summaries, and histograms when scraping non OpenMetrics protocols.
  However, this does not mean that the _created series is always ignored: when using the OpenMetrics 1.0 protocol, Prometheus itself continues to interpret the _created series as the start timestamp, so only the receiver-side handling for other scrape protocols has been removed.
• (Contrib) receiver/prometheus: Native histogram scraping and ingestion is now controlled by the scrape configuration option scrape_native_histograms. (#44861)
  The feature gate receiver.prometheusreceiver.EnableNativeHistograms is now stable and enabled by default.
  Native histograms scraped from Prometheus will automatically be converted to OpenTelemetry exponential histograms.
  To enable scraping of native histograms, you must configure scrape_native_histograms: true in your Prometheus
  scrape configuration (either globally or per-job). Additionally, the protobuf scrape protocol must be enabled
  by setting scrape_protocols to include PrometheusProto.

🚩 Deprecations 🚩

• (Splunk) signalfx-agent: The collectd/zookeeper plugin is deprecated. Please use the zookeeper receiver instead. This plugin will be removed by the end of March 2026. (#7016)
• (Contrib) processor/k8sattributes: Removes stable k8sattr.fieldExtractConfigRegex.disallow feature gate (#44694)
• (Contrib) receiver/kafka: Deprecate default_fetch_size parameter for franz-go client (#43104)
  The default_fetch_size parameter is now deprecated for the franz-go Kafka client and will only be used with the legacy Sarama client.
  Users should configure max_fetch_size instead when using franz-go.
  This deprecation is marked as of v0.142.0.
• (Contrib) receiver/kafka: Support configuring a list of topics and exclude_topics; deprecate topic and exclude_topic (#44477)
• (Contrib) receiver/prometheus: Deprecate use_start_time_metric and start_time_metric_regex config in favor of the processor metricstarttime (#44180)

💡 Enhancements 💡

• (Core) exporter/debug: Add logging of dropped attributes, events, and links counts in detailed verbosity (#14202)
• (Contrib) exporter/kafka: Adds server.address attribute to all Kafka exporter metrics. (#44649)
• (Contrib) exporter/prometheusremotewrite: Add option to remove service.name, service.instance.id, service.namespace ResourceAttribute from exported metrics (#44567)
• (Contrib) exporter/signalfx: Support setting default properties for dimension updates to be set lazily as part of configuration (#44891)
• (Contrib) extension/googlecloudlogentry_encoding: Add support for GCP VPC Flow Log fields for MIG (Managed Instance Group) and Google Service logs. (#44220)
  Adds support for the following GCP VPC Flow Log fields:
  • Add support for gcp.vpc.flow.{source,destination}.google_service.{type,name,connectivity}
  • Add support for gcp.vpc.flow.{source,destination}.instance.managed_instance_group.{name,region,zone}
• (Contrib) extension/health_check: Added extension.healthcheck.useComponentStatus feature gate to enable v2 component status reporting in healthcheckextension while maintaining backward compatibility by default. (#42256)
• (Contrib) pkg/translator/azurelogs: Added support for Activity Logs Reco...

Technical addon for the Splunk distribution of the OpenTelemetry Collector v1.9.0

v1.9.0

• Updates addon to use v0.141.0 of the Splunk distribution of the OpenTelemetry Collector

v0.141.0

This Splunk OpenTelemetry Collector release includes changes from the opentelemetry-collector v0.141.0
and the opentelemetry-collector-contrib v0.141.0 releases where appropriate.

🛑 Breaking changes 🛑

• (Core) pkg/config/confighttp: Use configoptional.Optional for confighttp.ClientConfig.Cookies field (#14021)
• (Contrib) all: fix pprofile DurationNano to be a TypeUint64 (#44397)
• (Contrib) connector/spanmetrics: Add a feature gate to use the latest semantic conventions for the status code attribute on generated metrics. | This feature gate will replace the status.code attribute on the generated RED metrics with otel.status_code. | It will also replace the values STATUS_CODE_ERROR and STATUS_CODE_OK with ERROR and OK to align with the latest conventions. (#42103)
  This change is made to align with the latest semantic conventions. | The feature gate is disabled by default, but can be enabled with --feature-gates spanmetrics.statusCodeConvention.useOtelPrefix | or explicitly disabled with --feature-gates -spanmetrics.statusCodeConvention.useOtelPrefix.
• (Contrib) exporter/kafka: exporter.kafkaexporter.UseFranzGo feature gate moved to Stable and is now always enabled (#44565)
  The franz-go client is now the default and only Kafka client library for the Kafka exporter.
  The feature gate exporter.kafkaexporter.UseFranzGo has been promoted to Stable status and cannot be disabled.
  Users can no longer opt out of using the franz-go client in favor of the legacy Sarama client.
  The Sarama client and the feature gate will be removed completely after v0.143.0.
• (Contrib) extension/docker_observer: Upgrading Docker API version default from 1.24 to 1.44 (#44279)
• (Contrib) pkg/ottl: Type of field profile.duration changes from time.Time to int64. (#44397)
• (Contrib) receiver/azureeventhub: Promote Feature Gate receiver.azureeventhubreceiver.UseAzeventhubs to Beta (#44335)
• (Contrib) receiver/kafka: Remove deprecated topic and encoding (#44568)
• (Contrib) receiver/kafka: receiver.kafkareceiver.UseFranzGo feature gate moved to Stable and is now always enabled (#44564)
  The franz-go client is now the default and only Kafka client library for the Kafka receiver.
  The feature gate receiver.kafkareceiver.UseFranzGo has been promoted to Stable status and cannot be disabled.
  Users can no longer opt out of using the franz-go client in favor of the legacy Sarama client.
  The Sarama code and the feature gate will be removed completely after v0.143.0.

🚩 Deprecations 🚩

• (Contrib) receiver/prometheus: Add feature gate for extra scrape metrics in Prometheus receiver (#44181)
  deprecation of extra scrape metrics in Prometheus receiver will be removed eventually.

💡 Enhancements 💡

• (Splunk) splunk-otel-javaagent: Update splunk-otel-javaagent to v2.22.0 (#6976)
• (Splunk) jmx-metric-gatherer: Update jmx-metric-gatherer to v1.52.0 (#6964)
• (Splunk) splunk-otel-js: Update splunk-otel-js to v4.1.0 (#6956)
• (Core) pkg/config/confighttp: Setting compression_algorithms to an empty list now disables automatic decompression, ignoring Content-Encoding (#14131)
• (Contrib) connector/count: Support all attribute types in the count connector (#43768)
• (Contrib) connector/routing: Avoid extra copy of all data during routing (#44387)
• (Contrib) exporter/awss3: Support compression with ZSTD (#44542)
• (Contrib) exporter/file: Add create_directory and directory_permissions options; exporter can automatically create parent directories (also honored by group_by) with configurable permissions. (#44280)
  • New config: create_directory (bool) and directory_permissions (octal string, e.g. "0755").
  • When enabled, the exporter creates the parent directory of path on start.
  • group_by uses the configured permissions when creating per-attribute directories.
• (Contrib) exporter/signalfx: Makes sending tags from SignalFx Exporter configurable (#43799)
  New optional configuration flag drop_tags has been added to SignalFx Exporter to allow users to disable tag metadata sending.
  This feature has been introduced due to a common issue among Splunk Observability customers when they're receiving more tags
  than allowed limit.
• (Contrib) extension/headers_setter: Add support for chaining with other auth extensions via additional_auth configuration parameter. This allows combining multiple authentication methods, such as OAuth2 for bearer token authentication and custom headers for additional metadata. (#43797)
  The additional_auth parameter enables the headers_setter extension to work in conjunction
  with other authentication extensions like oauth2client. The additional auth extension is called
  first to apply its authentication, then headers_setter adds its configured headers on top.
• (Contrib) extension/k8sobserver: Add container name, container ID, and container image to port endpoint (#41309)
• (Contrib) pkg/ottl: Add ParseSeverity function to define mappings for log severity levels. (#35778)
• (Contrib) pkg/ottl: Introduce CommunityID function to generate network hash (20-byte SHA1 digest) flow from the given source and destination {IP, port}, optionally protocol and seed values. (#34062)
• (Contrib) pkg/ottl: Expand usage of literal into typed getters and avoid unnecessary work (#44201)
• (Contrib) pkg/ottl: SliceToMap: add support to convert slices with non-map elements to maps (#43099)
• (Contrib) processor/cumulativetodelta: Add support for exponential histograms (#44106)
• (Contrib) processor/resourcedetection: Use osProfile.computerName for setting host.name in Azure resource detection processor (#43959)
• (Contrib) processor/resourcedetectionprocessor/oraclecloud: Oracle Cloud (OCI) resource detection processor now differentiates between running off-platform (expected not to work), and encountering an error when running on-platform (expected to work) (#42794)
  • Collectors not running on Oracle Cloud return an empty resource and no error, since we don't expect this case to work.
  • If the Oracle Cloud platform is detected but metadata fetch fails, the error is now logged and signaled to the processor, since we do expect this case to work.
• (Contrib) processor/tail_sampling: Add bytes_limiting policy type, sample based on the rate of bytes per second using a token bucket algorithm. (#42509)
• (Contrib) processor/tail_sampling: Adaptive expected_new_traces_per_sec to improve performance lower bound (#43561)
• (Contrib) receiver/googlecloudpubsub: Update to cloud.google.com/go/pubsub/v2. (#44466)
• (Contrib) receiver/googlecloudpubsub: Adjusts the subscription regex to accommodate new project naming used for Google Trusted Partner Clouds. (#43988)
• (Contrib) receiver/k8s_events: Allow more event types like Error and Critical which are typically used by applications when creating events. (#43401)
  k8seventsreceiver allows event types Error and Critical in addition to the current Normal and Warning event types.
• (Contrib) receiver/kafka: Add support for exclude topics whe...