I have upgraded server to 1.8.10 (from 1.8.9) and after this a trigger that includes a regexp evaluates always to PROBLEM.
Any idea why is this?
The trigger is:
{Template_Windows Active:eventlog[Security,,,,4648,].regexp(@netaddr)}=0
and it worked fine before upgrade (not firing if the regexp was TRUE).
Regexp @netaddr is:
Expression: Network Address:\s*-
Expected result: Result is TRUE
Case sensitive: No
and it evaluates correctly to true or false in the regular expression test.
This trigger wants to fire only when somebody logs in a Windows server from any IP address and should not fire if the IP address is -.
I have not upgrade the client to 1.8.10 (it is still 1.8.9) but I think this regexp is evaluated only on server and has nothing to do with the client.
Anybody ran into this problem before?
Thanks for any hint!
Any idea why is this?
The trigger is:
{Template_Windows Active:eventlog[Security,,,,4648,].regexp(@netaddr)}=0
and it worked fine before upgrade (not firing if the regexp was TRUE).
Regexp @netaddr is:
Expression: Network Address:\s*-
Expected result: Result is TRUE
Case sensitive: No
and it evaluates correctly to true or false in the regular expression test.
This trigger wants to fire only when somebody logs in a Windows server from any IP address and should not fire if the IP address is -.
I have not upgrade the client to 1.8.10 (it is still 1.8.9) but I think this regexp is evaluated only on server and has nothing to do with the client.
Anybody ran into this problem before?
Thanks for any hint!
Comment