You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, elastic_transport.transport logs every request at the INFO level, which can lead to cluttered logs in production environments. While INFO logs may not always be necessary, retaining WARNING and ERROR logs is critical for identifying potential issues and errors.
Use Case:
In a Tornado application interacting with Elasticsearch, frequent INFO logs from elastic_transport.transport dominate the log output. For example:
Nov 22 15:30:59 ip-172-30-1-34 python[115073]: [INFO elastic_transport.transport:271] POST http://elasticsearch:9200/mygene_index/_search?rest_total_hits_as_int=true [status:200 duration:0.006s]
These logs are less useful in normal operation but can mask more important WARNING and ERROR messages.
Current workaround involves manually setting the log level:
Feature Request
Currently,
elastic_transport.transport
logs every request at theINFO
level, which can lead to cluttered logs in production environments. WhileINFO
logs may not always be necessary, retainingWARNING
andERROR
logs is critical for identifying potential issues and errors.Use Case:
INFO
logs fromelastic_transport.transport
dominate the log output. For example:These logs are less useful in normal operation but can mask more important
WARNING
andERROR
messages.The text was updated successfully, but these errors were encountered: