-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider renaming the tracer
logger to improve clarity
#950
Comments
tracer
logger to improve clarity
Hey @yeikel! The log configuration is something that the java clients inherits from the elasticsearch server code through the RestClient (the low level transport client), so we currently don't have a way of changing it. When we'll stop using the server's RestClient (hopefully soon!) we'll be able to name the logs how we want - accepting suggestions! |
Thank you for the context. I noticed that the issue was closed. Could you clarify what changed? |
Thank you for the context Is that new major version of the client expected soon? |
pretty soon 👀 |
As per the logs: https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/current/java-rest-low-usage-logging.html#_trace_logs
To enable the "Tracer" logs, one needs to change the log levels of the "tracer" log name such as
In my opinion, the name "tracer" was a poor choice because it does not link back to Elasticsearch in any way. The "tracer" term may conflict with other projects as well which may not be desired
I always see myself linking back to https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/current/java-rest-low-usage-logging.html to explain what this does
The text was updated successfully, but these errors were encountered: