Other products have been expanded such that their Bulk/ingest requests include header x-elastic-product-origin so we can better identify traffic from its upstream source. Will you kindly consider expanding Logstash's Elasticsearch output to do the same?
Ideally, same as Kibana and Agent(/beats) examples, Logstash will also self-report to more easily trace back high ingest volume/queues on the Elasticsearch side.
👋🏽 howdy, team!
Other products have been expanded such that their Bulk/ingest requests include header
x-elastic-product-origin
so we can better identify traffic from its upstream source. Will you kindly consider expanding Logstash's Elasticsearch output to do the same?Looks like this from Elasticsearch's List Tasks:
Single examples (privacy redacted)
Ideally, same as Kibana and Agent(/
beats
) examples, Logstash will also self-report to more easily trace back high ingest volume/queues on the Elasticsearch side.TIA! 🙏
(Self note: Building off es#111773 as we work to more officially publish this common troubleshooting.)