Skip to content

[exporter/elasticsearch] Improve response filtering and use response compression with Elasticsearch #37785

Open
@strawgate

Description

Component(s)

exporter/elasticsearch

Is your feature request related to a problem? Please describe.

The output for Elasticsearch in Beats and Logstash use filter_path set to errors,items.*.error,items.*.status to reduce the size of the response from Elasticsearch. The response size is basically 30 bytes + 25 bytes per event.

The filter_path used by docappender includes the target index for every document which results in the response growing by 85 bytes per event.

In addition, go-docappender does not request compression from Elasticsearch for responses. The compression ratio of bulk responses is >95%.

Describe the solution you'd like

Setting the filter_path to match beats and passing "Accept-Encoding" with gzip if compression is enabled

Describe alternatives you've considered

No response

Additional context

No response

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions