elasticsearch index failures not log into log file #4166
If Graylog is not able to ingest the messages to elasticsearch it should write a meaningful log message that contains something the admin can work with. That should contain what and why with as much information as possible.
The information / log should be found in the server.log as this would be the place where ppl check if anything is not working.
In the MongoDB we have currently the following entry:
But in the Logfile during that time is only visible that a deflector cycle had happened.
In case something unexpected happen we could not shift between different location of possible log information. In fact the server.log should be the single source of information. To make investigation easier.
Additional the given Information should be with out a doubt useful and say what happened.
The text was updated successfully, but these errors were encountered: