Hi Krysztof, I'm not 100% sure if this will help, but we are adding tracing and error capture to SPM <http://sematext.com/spm/>. I *think* that may do what you are after. In the mean time you could try setting up something like Zipkin.
Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/ On Wednesday, November 19, 2014 8:02:03 AM UTC-5, [email protected] wrote: > > Hmm > > Thanks for the answer but it unfortunately did not help me. What I would > like to achieve is ability to group logs from various system components. > > Assuming that we have a system containing 3 components: > > A - HTTP frontend > B - My App > C - Elasticsearch > > and communication chain is as follows: > > CLIENT -> A (generation of unique request id happens here) -> B (with > given request id) -> C (with given request id) > > Now if there is an exception or warning logged in one of those systems it > will be in the context of the generated unique request id. So assuming that > we have centralized logging infrastructure it is very easy now to track the > root causes and side effects of problems that occur in the system. > > On Wednesday, November 19, 2014 12:53:28 PM UTC+1, David Pilato wrote: >> >> I think you should solve that on application level. >> Though could this help? >> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-request-named-queries-and-filters.html#_named_queries >> >> Still, you have to record that somewhere. >> >> Not sure I helped... :( >> >> David >> >> Le 19 nov. 2014 à 11:58, [email protected] a écrit : >> >> Dear community, >> >> >> I am looking for a feature which allows to attach requestId to the >> commands that my app is passing to the elasticsearch. It is because of our >> client requirements regarding ability to track user requests through all >> system components. After quick look into java api I do not see any >> possibility to put additional field with requestId to the query builder. >> Can you confirm that? What do you suggest to do then? Would it be easier to >> write elasticsearch plugin adding this feature or should we just do some >> dirty hacks like modifying query to contain request id but in the way that >> it will not affect returned hits. >> >> Best regards, >> Krzysztof >> >> -- >> You received this message because you are subscribed to the Google Groups >> "elasticsearch" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/elasticsearch/7d73dabc-a274-4488-bf03-709d41c37ccd%40googlegroups.com >> >> <https://groups.google.com/d/msgid/elasticsearch/7d73dabc-a274-4488-bf03-709d41c37ccd%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> >> -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/8b04393d-900d-4283-aae2-c8e5c616ff92%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
