Release v0.113.0 (#5641)

* Release v0.113.0

* fix changelog

CHANGELOG.md

@@ -1,6 +1,71 @@
 # Changelog
 ## Unreleased
 
+## v0.113.0
+
+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](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/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](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/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](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35445))
+- (Contrib) `journaldreceiver`: adds ability to parse journald's MESSAGE field as a string if desired ([#36005](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/36005))
+- (Contrib) `journaldreceiver`: allows querying a journald namespace ([#36031](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/36031))
+- (Contrib) `hostmetricsreceiver`: Add the system.uptime metric in the hostmetrics receiver ([#31627](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/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](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35814))
+- (Contrib) `pkg/ottl`: Add SliceToMap function ([#35256](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35256))
+- (Contrib) `journaldreceiver`: Restart journalctl if it exits unexpectedly ([#35635](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35635))
+- (Contrib) `routingconnector`: Add ability to route by request metadata. ([#19738](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/19738))
+- (Contrib) `exporter/signalfx`: Enabling retrying for dimension properties update without tags in case of 400 response error. ([#36044](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/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](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/36026))
+- (Contrib) `simpleprometheusreceiver`: Support to set `job_name` in config ([#31502](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/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](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/36071))
+- (Contrib) `routingconnector`: Add ability to route log records individually using OTTL log record context. ([#35939](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35939))
+- (Contrib) `splunkenterprisereceiver`: Add new metrics for Splunk Enterprise dispatch artifacts ([#35950](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35950))
+- (Core) `batchprocessor`: Move single shard batcher creation to the constructor ([#11594](https://github.com/open-telemetry/opentelemetry-collector/issues/11594))
+- (Core) `service`: add support for using the otelzap bridge and emit logs using the OTel Go SDK ([#10544](https://github.com/open-telemetry/opentelemetry-collector/issues/10544))
+
+### 🧰 Bug fixes 🧰
+
+- (Contrib) `receiver/windowseventlog`: Fix panic when rendering long event messages. ([#36179](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/36179))
+- (Contrib) `hostmetricsreceiver`: Do not set the default value of HOST_PROC_MOUNTINFO to respect root_path ([#35990](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35990))
+- (Contrib) `prometheusexporter`: Fixes an issue where the prometheus exporter would not shut down the server when the collector was stopped. ([#35464](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35464))
+- (Contrib) `k8sobserver`: Enable observation of ingress objects if the `ObserveIngresses` config option is set to true ([#35324](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35324))
+- (Contrib) `pkg/stanza`: Fixed bug causing Operators with DropOnErrorQuiet to send log entries to the next operator. ([#35010](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35010))
+  This issue was introduced by a bug fix meant to ensure Silent Operators are not logging errors ([#35010](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/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](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35294))
+- (Contrib) `receiver/filelog`: fix record counting with header ([#35869](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35869))
+- (Contrib) `connector/routing`: Fix detection of duplicate conditions in routing table. ([#35962](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35962))
+- (Contrib) `solacereceiver`: The Solace receiver may unexpectedly terminate on reporting traces when used with a memory limiter processor and under high load ([#35958](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35958))
+- (Contrib) `pkg/stanza/operator`: Retain Operator should propagate the severity field ([#35832](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/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](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/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](https://github.com/open-telemetry/opentelemetry-collector/issues/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](https://github.com/open-telemetry/opentelemetry-collector/issues/11537))
+
 ## v0.112.0
 
 This Splunk OpenTelemetry Collector release includes changes from the opentelemetry-collector v0.112.0 and the opentelemetry-collector-contrib v0.112.0 releases where appropriate.
@@ -175,8 +240,8 @@ Additionally, updates `splunk-otel-javaagent` to [`v2.8.1`](https://github.com/s
 - (Contrib) `prometheusreceiver`: Fix the retrieval of scrape configurations by also considering scrape config files ([#34786](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/34786))
 - (Contrib) `redactionprocessor`: Fix panic when using the redaction processor in a logs pipeline ([#35331](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35331))
 - (Contrib) `exporter/splunkhec`: Fix incorrect claim that the exporter doesn't mutate data when batching is enabled. The bug lead to runtime panics when the exporter was used with the batcher enabled in a fanout scenario. ([#35306](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/35306))
-- (Splunk) Choco upgrade should preserve collector service custom env vars ([#5386](https://github.com/signalfx/splunk-otel-collector/pull/5386)) 
-- (Splunk) `discoveryreceiver` with `splunk.continuousDiscovery` feature gate enabled: Remove redundant discovery.receiver.rule attribute ([#5403](https://github.com/signalfx/splunk-otel-collector/pull/5403)) 
+- (Splunk) Choco upgrade should preserve collector service custom env vars ([#5386](https://github.com/signalfx/splunk-otel-collector/pull/5386))
+- (Splunk) `discoveryreceiver` with `splunk.continuousDiscovery` feature gate enabled: Remove redundant discovery.receiver.rule attribute ([#5403](https://github.com/signalfx/splunk-otel-collector/pull/5403))
 - (Splunk) `discoveryreceiver` with `splunk.continuousDiscovery` feature gate enabled: Remove redundant resource attributes ([#5409](https://github.com/signalfx/splunk-otel-collector/pull/5409))
 
 ## v0.109.0
@@ -199,9 +264,9 @@ Additionally, updates `splunk-otel-javaagent` to [`v2.8.1`](https://github.com/s
   If the collector is running as a process on the host OS and the Apache Web Server is in a Docker container add `--set=splunk.discovery.extensions.docker_observer.config.use_host_bindings=true` to the command-line arguments for the discovery to create the correct endpoint.
 - (Splunk) Introduce continuous service discovery mode. This mode can be enabled with a feature gate by adding `--feature-gates=splunk.continuousDiscovery` command line argument. ([#5363](https://github.com/signalfx/splunk-otel-collector/pull/5363))
   The new mode does the following:
-  - It allows discovering new services that were not available at the time of the collector startup. If discovery is 
+  - It allows discovering new services that were not available at the time of the collector startup. If discovery is
     successful, the metrics collection will be started.
-  - Information about discovered services is being sent to Splunk Observability Cloud. The information will include 
+  - Information about discovered services is being sent to Splunk Observability Cloud. The information will include
     instructions to complete discovery for particular services if the discovery was not successful out of the box.
 - (Core) `service`: move `useOtelWithSDKConfigurationForInternalTelemetry` gate to beta ([#11091](https://github.com/open-telemetry/opentelemetry-collector/issues/11091))
 - (Core) `service`: implement a no-op tracer provider that doesn't propagate the context ([#11026](https://github.com/open-telemetry/opentelemetry-collector/issues/11026))
@@ -406,11 +471,11 @@ This release fixes CVE-2024-42368 on the `bearerauthtokenextension` ([#34516](ht
   - vcenter.vm.vsan.operations
   - vcenter.vm.vsan.latency.avg
 - (Contrib) `vcenterreceiver`: Several host performance metrics now return 1 data point per time series instead of 5. ([#34708](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/34708))
-  The 5 data points previously sent represented consecutive 20s sampling periods. Depending on the collection interval 
+  The 5 data points previously sent represented consecutive 20s sampling periods. Depending on the collection interval
   these could easily overlap. Sending just the latest of these data points is more in line with other performance metrics.
-  
+
   This change also fixes an issue with the googlecloud exporter seeing these datapoints as duplicates.
-  
+
   Following is the list of affected metrics which will now only report a single datapoint per set of unique attribute values.
   - vcenter.host.cpu.reserved
   - vcenter.host.disk.latency.avg
@@ -421,7 +486,7 @@ This release fixes CVE-2024-42368 on the `bearerauthtokenextension` ([#34516](ht
   - vcenter.host.network.packet.rate
   - vcenter.host.network.throughput
   - vcenter.host.network.usage
-  
+
 - (Splunk) Remove converters helping with old breaking changes. If those changes were not addressed, the collector will fail to start. ([#5267](https://github.com/signalfx/splunk-otel-collector/pull/5267))
   - Moving TLS config options in HEC exporter under tls group
   - Moving TLS insecure option in OTLP exporter under tls group