splunk-hec-apply-compression.yaml

# Use this changelog template to create an entry for release notes.
# If your change doesn't affect end users, such as a test fix or a tooling change,
# you should instead start your pull request title with [chore] or use the "Skip Changelog" label.

# One of 'breaking', 'deprecation', 'new_component', 'enhancement', 'bug_fix'
change_type: enhancement

# The name of the component, or a single word describing the area of concern, (e.g. filelogreceiver)
component: exporter/splunk_hec

# A brief description of the change.  Surround your text with quotes ("") if it needs to start with a backtick (`).
note: Apply compression to Splunk HEC payload unconditionally if it's enabled in the config.

# Mandatory: One or more tracking issues related to the change. You can use the PR number here if no issue exists.
issues: [22969, 22018]

# (Optional) One or more lines of additional information to render under the primary note.
# These lines will be padded with 2 spaces and then inserted directly into the document.
# Use pipe (|) for multiline entries.
subtext: |
  The compression used to be enabled only if the payload size was greater than 1.5KB which significantly
  complicated the logic and made it hard to test. This change makes the compression unconditionally applied to 
  the payload if it's enabled in the config. The benchmarking shows improvements in the throughput and CPU usage for 
  large payloads and expected degradation for small payloads which is acceptable given that it's not a common case.