Two options, you can use the internal sendemail command or the sendresults add-on for Splunk which provides much functionality and flexibility than the sendemail command.
thanks i am aware of this command. What i am unaware of is how to search for - um, banner messages and such internal errors...
I wonder if the REST API could help here.. Specifically /services/messages
I'm away from a Splunk instance currently to try things out and confirm but I would think that a query like:
| rest /services/messages count=0
Would work and then standard alerting from it... Or maybe you'd have to use map to loop over the subresources too but it might be a start 🙂
That said however, if the warning is about min disk space being reached a Splunk search would not be kicked off either (assuming the volume with the dispatch directory is the issue), so maybe monitoring with another tool like Zabbix could be warranted as well
Thanks, i will look into it, it certainly looks promissing.
For the second part we use Nimsoft Nimbus and monitor the logfile of the forwarder and react to "ERRORconnectionfailed".