elastic / elastic/logstash

(output.elasticsearch) force user agent to be logstash

Open
#16,449 1 comment 0 reactions 0 assignees View on GitHub
enhancement status:needs-triage
Dominant language
Java
Stars
14.9k
Forks
3.5k
Avg merge
19h 14m
Merged PRs (30d)
63

Description

👋 howdy, team!

For the Logstash API outputs or at least for [its Elasticsearch output](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html) would you kindly consider forcing its HTTP user agent to report as Logstash? "Manticore" still creeps through sometimes-almost-randomly which most team mates don't know how to interpret.

Example from Elastic Cloud proxy logging showing even recent versions affected by `user_agent: Manticore *`

![Image](https://github.com/user-attachments/assets/aee90d45-2724-43dd-b24d-53ca280ccb64)

![Image](https://github.com/user-attachments/assets/2f5cf532-9bf2-4e83-a6b4-f8b10d5ce63a)

Vs expected user agent formats `Logstash/*` like

![Image](https://github.com/user-attachments/assets/27280830-b1ff-4370-a978-5bdcede97b38)

TIA! 🙏

(Self-note: data uncertainty would be further exposed once [es#112845](https://github.com/elastic/elasticsearch/issues/112845) done, but concern would be reduced by [ls#16448](https://github.com/elastic/logstash/issues/16448) if implemented instead.)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.