splunk-otel-collector-0.62.1

Splunk OpenTelemetry Collector for Kubernetes

[0.62.1] - 2022-11-01

Fixed

• Make sure filelog receiver uses file_storage for checkpointing (#567)

splunk-otel-collector-0.62.0

[0.62.0] - 2022-10-28

Changed

• Upgrade splunk-otel-collector image to 0.62.0 (#573)

🚨 KNOWN ISSUE 🚨

This chart introduces an issue affecting users using otel file logging, where the checkpoint file used to set the current offset of the files being monitored is ignored. See #567 for more information. Please consider upgrading to v0.62.1. Fluentd users are unaffected by this bug.

splunk-otel-collector-0.61.0

[0.61.0] - 2022-10-07

Changed

• Increase number of queue consumers in the gateway configuration (#554)
• Upgrade splunk-otel-collector image to 0.61.0 (#556)

🚨 KNOWN ISSUE 🚨

This chart introduces an issue affecting users using otel file logging, where the checkpoint file used to set the current offset of the files being monitored is ignored. See #567 for more information. Please consider upgrading to v0.62.1. Fluentd users are unaffected by this bug.

splunk-otel-collector-0.59.0

0.59.0 - 2022-09-17

Added

A way to provide a custom image for init container patching host log directories (#534, #535)

Changed

Upgrade splunk-otel-collector image to 0.59.1 (#536)

[BREAKING CHANGE] Datatype of filelog.force_flush_period and filelog.poll_interval were changed back from map to string due to upstream changes. See upgrade guidelines

🚨 KNOWN ISSUE 🚨

This chart introduces an issue affecting users using otel file logging, where the checkpoint file used to set the current offset of the files being monitored is ignored. See #567 for more information. Please consider upgrading to v0.62.1. Fluentd users are unaffected by this bug.

splunk-otel-collector-0.58.0

Changed

• Make Openshift SecurityContextConstraints more restrictive (#513)
• Upgrade splunk-otel-collector image to 0.58.0 (#518)
  • [BREAKING CHANGE] Datatype of filelog.force_flush_period and filelog.poll_interval were
    changed from string to map due to upstream changes.
    See upgrade guidelines

splunk-otel-collector-0.57.1

Changed

• Do not send clusterReceiver metrics through gateway (#491)

splunk-otel-collector-0.57.0

Changed

• Upgrade splunk-otel-collector image to 0.57.0 (#504)

🚨 KNOWN ISSUE 🚨

An issue with the clusterReceiver was reported in 0.57.0 and fixed in 0.57.1, the splunk-otel-collector-0.57.0.tgz binary has been removed for this reason.

splunk-otel-collector-0.56.0

Changed

• Removed unnecessary change of group ownership in chmod initContainer (#486)
• Upgrade splunk-otel-collector image to 0.56.0 (#501)

splunk-otel-collector-0.55.0

Changed

• Upgrade splunk-otel-collector image to 0.55.0 (#485)

splunk-otel-collector-0.54.2

Changed

• The receiver.k8sclusterreceiver.reportCpuMetricsAsDouble feature gate has been removed (#487)
  • If you are using this feature gate, then see the upgrade guidelines
• Remove high cardinality fields from k8s events: (#484)
  • k8s.event.start_time
  • k8s.event.name
  • k8s.event.uid

Fixed

• Make sure that logs are enabled to send k8s events (#481)
• Make sure that "sourcetype" field is always set on k8s events (#483)