Notifications are triggered by Graylog and indicate a situation you should act upon. Many notification types will also provide a link to the Graylog documentation if you need more information or assistance.
×
Journal utilization is too high (triggered 2 hours ago)
Journal utilization is too high and may go over the limit soon. Please verify that your Elasticsearch cluster is healthy and fast enough. You may also want to review your Graylog journal settings and set a higher limit. (Node: 742950e5-9e80-44cb-a860-77b014c24493 )
×
Uncommited messages deleted from journal (triggered 2 hours ago)
Some messages were deleted from the Graylog journal before they could be written to Elasticsearch. Please verify that your Elasticsearch cluster is healthy and fast enough. You may also want to review your Graylog journal settings and set a higher limit. (Node: 742950e5-9e80-44cb-a860-77b014c24493 )
what is the state of the Elasticsearch instance behind Graylog?
If Graylog is not able to output any logs, it’s most likely related with a non working Elasticsearch or a broken connection to it.
Have a look at the Graylog default file locations and post the content of the Elasticsearch logs and config.
Additionally, the log from Graylog could be helpful. If your able to, clear the log file, restart Graylog and wait a few minutes. Then copy the log and paste it here.
Greetings,
Philipp
PS: Remember to use tripple backticks or using a gist/etc. when posting logs.