[exporter/stefexporter] Fix incorrectly implemented STEF exporter zstd compression option #38089
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Resolves #38088
Previously the compression option was incorrectly set both for STEF Writer and gRPC Client. This was unnecessary and also did not work if the destination gRPC receiver did not enable zstd compressor.
This change correctly removes the zstd compression option from gRPC client and only sets it as a STEF Writer option.
Interestingly, with zstd enabled we get less than 1 byte per metric data point with STEF exporter and hostmetrics receiver!
Testing Done
Added zstd compression option to TestExport unit test.
Tested manually with STEF Server here https://github.com/splunk/stef/tree/main/otelcol/cmd/stefmockserver
Built Collector contrib via
make otelcontribcol
. Used the following config for testing: