We use ES in production. We generate our own transactionId / requestId for each request, so that we can trace the query. However, if there is a 400 / 500 error returned by ES (because of client or server error), there is no easy to to stitch the failure in the pipeline with ES failure other than loo…

Passing requestId in ES logs

danielmitterdorfer (Daniel Mitterdorfer) September 6, 2017, 7:23am 2

stats groups may help as I've mentioned in Use of _meta field in elasticsearch 2.4.1?. I'm not sure whether this would help with 400/500s though.

Daniel

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.