Ad Widget

Collapse

syslog monitoring

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • andyfry
    Junior Member
    • Mar 2013
    • 10

    #1

    syslog monitoring

    Hi,

    I wonder if anybody can help with this minor issue?

    I'm succesfully using rsyslog to filter out messages from a firewall so only the stuff I'm interested in goes into the log file I'm monitoring.

    The result is my network engineers receive an email whenever someone logs on and makes changes or we get an unexpected attack. The only problem is the Trigger always shows as a problem regardless of how long ago the entry hit the log file.

    What I'd like to do is send the email but then reset the trigger to OK.

    Can anybody suggest a way of doing this?

    Cheers

    Andy
  • mbrand5371
    Member
    • May 2009
    • 55

    #2
    Hi Andy.

    Try something like this trigger:

    {TEMPLATE:log[/var/log/zabbix/os_cron,"logger: crond:.*Fehler"].nodata(120)}#1

    This trigger will launched for 120 seconds if the string: "logger: crond:.*Fehler" will be found in the log file: "/var/log/zabbix/os_cron"
    So now you can use an trigger based action to send the email.

    Regards, Marcus

    Comment

    Working...