Dear all,
Fortunately, Zabbix is able to monitor log files that enable us to fire a trigger when a given string matches. Basically the Zabbix doc was sufficient to run a simple monitoring profile
Thus, it is very nice to receive a notification once an error message for example being detected in a log file then we get something like :
As was shown above, logrt was used to collect data from files that matches the pattern "files-.*event.log"
Basically, it collects more than 5 log files in the given log directory.
Everything seems OK, excepting 2 things would like to negotiate and share with everyone:
1. The trigger notification shows the value the line containing the error string.
But how it can be modified to show from which EXACTLY log file name ???
2. Imagine Zabbix is being monitoring large and hundreds of log files by collecting data. Is there a better way to save history write cache for zabbix ?
Fortunately, Zabbix is able to monitor log files that enable us to fire a trigger when a given string matches. Basically the Zabbix doc was sufficient to run a simple monitoring profile
Thus, it is very nice to receive a notification once an error message for example being detected in a log file then we get something like :
Code:
Trigger: Error Message Log Server detected Trigger status: PROBLEM Trigger severity: Information Trigger URL: Item values: 1. Logging (TestLog:logrt["/home/log/files-.*.event.log"]): 20140916-08:40:03.469 : processNextMessage: received error message code: 0, message length: 24
Basically, it collects more than 5 log files in the given log directory.
Everything seems OK, excepting 2 things would like to negotiate and share with everyone:
1. The trigger notification shows the value the line containing the error string.
But how it can be modified to show from which EXACTLY log file name ???
2. Imagine Zabbix is being monitoring large and hundreds of log files by collecting data. Is there a better way to save history write cache for zabbix ?