To answer your original question:
This line of code extracts the search string from the config file:
($string[$i], $action[$i], $actionargs[$i], $numrows[$i]) = split /\t+/, $_;
And this line decides if the logfile has a match:
if ($_ =~ /$string[$str_index]/i) {
As far as I can tell, if you were to put a regular expression in for your string in the config file, it would directly interpret it as such. This is a direct conflict with your statement that it doesn't take regular expressions.
Have you tried
orchestral.*execution mail 1
at all? Because unless I'm missing something (and I sort of skimmed the code so it's of course possible), it sure looks to me like it would work.
In reply to Re^3: question on log_watcher input
by marinersk
in thread question on log_watcher input
by adewolf38
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |