check_eventlog scan range issue

[shivangi]

Hi Team,

Check_eventlog is not accepting scan range .To be more exact i want alert if specfic eventid registering itself in last 2 min should raise alert , but when i am keeping scan range of -2m , it still showing warning alert for that specific id which is not registered in last 2 min but before that time and also removing the scan range option totally also does not affect the result .

What is the use of scan range then ? Not quite understanding this behaviour . Please help in this .

Thanks in advance .

[cdienger]

Are you using the check_eventlog plugin that is available with NSClient++?

https://docs.nsclient.org/reference/win ... kEventLog/

Make sure you're passsing the scan-range argument with the -a flag. For example:

Code: Select all

./check_nrpe -H 192.168.55.5 -c check_eventlog -a "scan-range-2m"

[shivangi]

Thankyou , Its working now .

Also can you also please let me know if there is a way not to mention the eventid to be monitored in the filter but getting the ID info . in the output message whenever the warning or error id is logged .

I have to monitor 100 eventids for 3 instances which is a bit of tedious task to define service defintion for each event id separately .

Also will monitoring so many eventids have cause a load on Nagios (if i go separately defining them ) ?? My current version is nagios core 4.4.1 and is a cloud instance m4.xlarge .

Thanks in advance

[shivangi]

Hi Team,

Any suggestions on this please ?

Thanks