0

We have a Groovy application that uses the Elasticsearch java client library to query an Elasticsearch cluster. We'd like to see the actual queries the library is sending, for debugging purposes.

We are also using Logback and it would really be convenient to be able to tweak our logback config to have the Elasticsearch client output more detailed debugging logs on its own, without having to redeploy a code change.

I've been looking but have not found any documentation on this so far -- does anyone know if there is a logger that can be affected by logback that we can change? Something like org.elasticsearch.client?

Improve this question
3
  • I don't think there is one. Elasticsearch has a dedicated logging mechanism exactly for this purpose - slowlogs. That's the official and recommended approach for monitoring the slow queries. Of course, you could lower the thresholds to very small values and basically see all the queries. Commented May 4, 2016 at 18:10
  • Ok, thanks @AndreiStefan Commented May 4, 2016 at 19:00
  • Also see @AndreiStefan's answer about how to set up slowlogs: stackoverflow.com/questions/33410701/… Commented May 5, 2016 at 3:22
Related questions
7743
Is Java "pass-by-reference" or "pass-by-value"?
4439
How do I avoid checking for nulls in Java?
4771
How do I read / convert an InputStream into a String in Java?
Load 7 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.