I am using the log item to monitor a log file, which is similar to the output of shorewall. I have an item set up to capture the two IP addresses within that, and the output looks something like:-
I have a trigger set up which works perfectly.
However, if I have the trigger set to multiple problem generation I get a problem for every line that matches in the config file.
If I have the trigger set to single problem generation, I get one problem, which is what I want. However, if I had two matches for the same item, I still only get one problem.
An example of this is below, showing the values reported by Zabbix in latest data:-
...generates one problem for "123.45.67.89 -> 192.168.1.254", until this line stops being seen in the log file.
...Generates one problem for "123.45.67.89 -> 192.168.1.254", but not "456.78.89.90 -> 192.168.6.42".
Basically I want to have each match generate separate triggers, but the same line appears multiple times as shown above.
Can anyone suggest a way round this? Thanks in advance!
Code:
123.45.67.89 -> 192.168.1.254
However, if I have the trigger set to multiple problem generation I get a problem for every line that matches in the config file.
If I have the trigger set to single problem generation, I get one problem, which is what I want. However, if I had two matches for the same item, I still only get one problem.
An example of this is below, showing the values reported by Zabbix in latest data:-
Code:
123.45.67.89 -> 192.168.1.254 123.45.67.89 -> 192.168.1.254 123.45.67.89 -> 192.168.1.254 123.45.67.89 -> 192.168.1.254
Code:
123.45.67.89 -> 192.168.1.254 456.78.89.90 -> 192.168.6.42 123.45.67.89 -> 192.168.1.254 456.78.89.90 -> 192.168.6.42 123.45.67.89 -> 192.168.1.254 456.78.89.90 -> 192.168.6.42
Basically I want to have each match generate separate triggers, but the same line appears multiple times as shown above.
Can anyone suggest a way round this? Thanks in advance!