signalfx/splunk-otel-collector v0.113.0

on GitHub

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

🛑 Breaking changes 🛑

• (Contrib) sapmreceiver: Remove the deprecated access_token_passthrough from SAPM receiver. (#35972)
  Please use include_metadata instead with the following config option applied to the batch processor:
  batch:
  metadata_keys: [X-Sf-Token]
• (Contrib) pkg/ottl: Promote processor.transform.ConvertBetweenSumAndGaugeMetricContext feature gate to Stable (#36216)
  This gate can no longer be disabled. The convert_sum_to_gauge and convert_gauge_to_sum may now only be used with the metric context.

💡 Enhancements 💡

• (Contrib) splunkenterprisereceiver: Add telemetry around the Splunk Enterprise kv-store. (#35445)
• (Contrib) journaldreceiver: adds ability to parse journald's MESSAGE field as a string if desired (#36005)
• (Contrib) journaldreceiver: allows querying a journald namespace (#36031)
• (Contrib) hostmetricsreceiver: Add the system.uptime metric in the hostmetrics receiver (#31627)
  This metric is provided by the new system scraper.
• (Contrib) hostmetrics: Adjust scraper creation to make it so the scraper name is reported with hostmetrics scraper errors. (#35814)
• (Contrib) pkg/ottl: Add SliceToMap function (#35256)
• (Contrib) journaldreceiver: Restart journalctl if it exits unexpectedly (#35635)
• (Contrib) routingconnector: Add ability to route by request metadata. (#19738)
• (Contrib) exporter/signalfx: Enabling retrying for dimension properties update without tags in case of 400 response error. (#36044)
  Property and tag updates are done using the same API call. After this change, the exporter will retry once to sync
  properties in case of 400 response error.
• (Contrib) signalfxexporter: Add more default metrics related to Kubernetes cronjobs, jobs, statefulset, and hpa (#36026)
• (Contrib) simpleprometheusreceiver: Support to set job_name in config (#31502)
• (Contrib) solacereceiver: Add support to the Solace Receiver to convert the new Move to Dead Message Queue and new Delete spans generated by Solace Event Broker to OTLP. (#36071)
• (Contrib) routingconnector: Add ability to route log records individually using OTTL log record context. (#35939)
• (Contrib) splunkenterprisereceiver: Add new metrics for Splunk Enterprise dispatch artifacts (#35950)
• (Core) batchprocessor: Move single shard batcher creation to the constructor (#11594)
• (Core) service: add support for using the otelzap bridge and emit logs using the OTel Go SDK (#10544)

🧰 Bug fixes 🧰

• (Contrib) receiver/windowseventlog: Fix panic when rendering long event messages. (#36179)
• (Contrib) hostmetricsreceiver: Do not set the default value of HOST_PROC_MOUNTINFO to respect root_path (#35990)
• (Contrib) prometheusexporter: Fixes an issue where the prometheus exporter would not shut down the server when the collector was stopped. (#35464)
• (Contrib) k8sobserver: Enable observation of ingress objects if the ObserveIngresses config option is set to true (#35324)
• (Contrib) pkg/stanza: Fixed bug causing Operators with DropOnErrorQuiet to send log entries to the next operator. (#35010)
  This issue was introduced by a bug fix meant to ensure Silent Operators are not logging errors (#35010). With this fix,
  this side effect bug has been resolved.
• (Contrib) splunkhecreceiver: Avoid a memory leak by changing how we record obsreports for logs and metrics. (#35294)
• (Contrib) receiver/filelog: fix record counting with header (#35869)
• (Contrib) connector/routing: Fix detection of duplicate conditions in routing table. (#35962)
• (Contrib) solacereceiver: The Solace receiver may unexpectedly terminate on reporting traces when used with a memory limiter processor and under high load (#35958)
• (Contrib) pkg/stanza/operator: Retain Operator should propagate the severity field (#35832)
  The retain operator should propagate the severity field like it does with timestamps.
• (Contrib) pkg/stanza: Handle error of callback function of ParserOperator.ProcessWithCallback (#35769)
  ProcessWithCallback of ParserOperator first calls the ParseWith method
  which properly handles errors with HandleEntryError.
  Then the callback function is called and its returned error should also
  be handled by the HandleEntryError ensuring a consistent experience.
• (Core) service: ensure traces and logs emitted by the otel go SDK use the same resource information (#11578)
• (Core) config/configgrpc: Patch for bug in the grpc-go NewClient that makes the way the hostname is resolved incompatible with the way proxy setting are applied. (#11537)

Docker Image Manifests:

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