splunk-otel-collector-0.113.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.113.0.

🧰 Bug fixes 🧰

• agent: Fixes hostmetrics receiver to use the correct mount path of the host's filesystem from inside the container (#1547)
• agent: Exclude scraping filesystem metrics from mounts that are not accessible from inside the container to avoid scraping errors. (#1550)

splunk-otel-collector-0.112.1

⚠️ Known issue ⚠️

This release of the Helm chart is not recommended to use due to the following issue:

• agent: Host metrics reported by this version are incorrect. The collector container assumes itself as a host instead of fetching data from the underlying node.

splunk-otel-collector-0.112.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.112.0.

⚠️ Known issues ⚠️

This release of the Helm chart contained the following issues, both resolved in the next patch release:

• agent: The hostmetrics receiver failed to scrape the some filesystem targets (#1533)
• operator: Instrumentation opentelemetry.io/v1alpha1 could sometimes attempt to be installed prematurely (#1544)

🛑 Breaking changes 🛑

• agent, gateway, chart: update default traces exporter to otlphttp (#1518)
  If you use the sapm exporter with custom settings, you have two options:
  • Migrate your sapm settings to the new otlphttp exporter.
  • Retain SAPM settings by moving them to your agent.config or gateway.config overrides to ensure they remain effective.

💡 Enhancements 💡

• operator: Bump operator to 0.71.2 in helm-charts/splunk-otel-collector/Chart.yaml (#1511)
• operator: Bump java to v2.9.0 in helm-charts/splunk-otel-collector/values.yaml (#1509)
• operator: Bump nodejs to v2.14.0 in helm-charts/splunk-otel-collector/values.yaml (#1519)

splunk-otel-collector-0.111.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.111.0.

🚩 Deprecations 🚩

• chart: Added a note anbout the deprecation of the fluentd option in the chart (#1460)

💡 Enhancements 💡

• chart: Propagated "sourcetype" to work for metrics and traces (#1376)
• agent: The agent is now deployed with a Kubernetes service for receiving telemetry data by default (#1485)
• operator: Bump dotnet to v1.7.0 in helm-charts/splunk-otel-collector/values.yaml (#1474)
• operator: Bump nodejs to v2.13.0 in helm-charts/splunk-otel-collector/values.yaml (#1470)

🧰 Bug fixes 🧰

• agent: Add k8s.node.name attribute to discovered service entities to fix broken link in the UI. (#1494)

splunk-otel-collector-0.110.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.110.0.

💡 Enhancements 💡

• template: Add default metadata key for token to batch processor (#1467)
  Add default metadata key for token to batch processor.
  This will allow the token to be retrieved from the context. When SAPM is deprecated and
  OTLP used, this will be the normal mode of operation.
• operator: Bump operator to 0.56.0 in helm-charts/splunk-otel-collector/Chart.yaml (#1446)
• operator: Bump java to v2.8.1 in helm-charts/splunk-otel-collector/values.yaml (#1458)

🧰 Bug fixes 🧰

• agent: use root_path to configure the hostmetricsreceiver, instead of environment variables. (#1462)

splunk-otel-collector-0.109.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.109.0.

🛑 Breaking changes 🛑

• operator: Operator Helm values previously under .Values.operator.instrumentation.spec.* have been moved to .Values.instrumentation.* (#1436)
  If you use custom values under .Values.operator.instrumentation.spec.* please review the upgrade guidelines

💡 Enhancements 💡

• agent: Added fsyncFlag configuration to allow users to enable fsync on the filestorage. (#1425)
• agent: Add a feature gate useControlPlaneMetricsHistogramData (#1372)
  This feature gate allows to gather control plane metrics and send them as histogram data to Observability Cloud.
  This is an experimental feature under heavy development.
• agent: Add base configuration to support the new continuous discovery mechanism. (#1455)
  The new continuous discovery mechanism is disabled by default. To enable it, set the following values in your configuration:

  agent:
    discovery:
      enabled: true
    featureGates: splunk.continuousDiscovery

• operator: Bump nodejs to v2.12.0 in helm-charts/splunk-otel-collector/values.yaml (#1434)

🧰 Bug fixes 🧰

• targetAllocator: Fix the name of the service account token given when featureGates.explicitMountServiceAccountToken is true (#1427)

splunk-otel-collector-0.105.5

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.105.0.

💡 Enhancements 💡

• all: Offer an experimental feature gate to mount service tokens in specific containers. (#1421)
  Kubernetes API access tokens are currently granted via mounting them on all containers of the cluster receiver,
  gateway and daemonset. They are also enabled for the target allocator deployment.
  This experimental change defines how to mount the service account token on specific containers.

splunk-otel-collector-0.105.4

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.105.0.

🛑 Breaking changes 🛑

• operator: Bump java from v1.32.3 to v2.7.0 in helm-charts/splunk-otel-collector/values.yaml (#1349)
  This is a major upgrade. If you use Java auto-instrumentation please review the upgrade guidelines

🧰 Bug fixes 🧰

• agent: Retry indefinitely on filelog receiver if noDropLogsPipeline feature gate is enabled. (#1410)

splunk-otel-collector-0.105.3

[0.105.3] - 2024-08-21

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.105.0.

🛑 Breaking changes 🛑

• agent: Remove the deprecated OTLP HTTP port 55681 (#1359)

🚀 New components 🚀

• targetAllocator: Add support for Target Allocator as part of the Helm chart. (#689)
  Target Allocator is a component of the OpenTelemetry Operator.
  With this addition, the target allocator is deployed to work in coordination with the daemonset of collectors.
  It applies a default configuration applying scrape targets per node.
  By default, the Target Allocator looks for all ServiceMonitor and PodMonitor CRDs across all namespaces.
  This can be tuned by overriding the service account associated with the Target Allocator.

💡 Enhancements 💡

• operator: Bump nodejs to v2.11.0 in helm-charts/splunk-otel-collector/values.yaml (#1352)
• agent: Add an experimental feature gate to use exporter batching instead of the batch processor (#1387)
• all: Set automountServiceAccountToken to true explicitly for the chart's defined service accounts. (#1390)
• operator: Bump java to v1.32.3 in helm-charts/splunk-otel-collector/values.yaml (#1355)

🧰 Bug fixes 🧰

• agent: Remove apparmor pod annotation by enabled default (#1378)

splunk-otel-collector-0.105.0

This Splunk OpenTelemetry Collector for Kubernetes release adopts the Splunk OpenTelemetry Collector v0.105.0.