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

Topic		Replies	Views
Is there any way of tracking request id? Elasticsearch	5	6163	July 6, 2017
Recommendations for tracking down slow queries Elasticsearch	4	1432	July 5, 2017
Problems searching ES from other machine Elasticsearch	3	518	July 6, 2017
Elasticsearch X-Opaque-Id Not in application.log Exception Elasticsearch	1	544	February 24, 2020
Will add unique traceId per request to trace the cost time? Elasticsearch	2	1395	July 6, 2017