| Cheshire Cat Computing http://steveshipway.org/forum/ |
|
| Nagios EventLog: FAQ http://steveshipway.org/forum/viewtopic.php?f=22&t=404 |
Page 1 of 2 |
| Author: | stevesh [ Tue Nov 09, 2004 4:21 pm ] |
| Post subject: | Nagios EventLog: FAQ |
| Author: | jmituzas [ Sat Nov 14, 2009 4:41 am ] |
| Post subject: | Re: Nagios EventLog: FAQ |
Hmmm do you have the define command as well? Thanks in advace |
|
| Author: | stevesh [ Sat Nov 14, 2009 7:22 am ] |
| Post subject: | Re: Nagios EventLog: FAQ |
It is a passive service, so you dont have a command. In the case of a service which you want to change to 'unknown' if it doesnt hear from the eventlog monitor in a specified amount of time, use freshness checking and set the check_command to be a dummy command that just sets the status to 'unknown'. |
|
| Author: | jmituzas [ Sat Nov 14, 2009 8:11 am ] |
| Post subject: | Re: Nagios EventLog: FAQ |
Thanks I had it set as: check_command check_dummy Status info within the nagios web interface reports: Service is not scheduled to be checked... has been stating this for over 2 hrs. now, is this normal? |
|
| Author: | stevesh [ Sat Nov 14, 2009 9:44 am ] |
| Post subject: | Re: Nagios EventLog: FAQ |
This is normal; a passive service is never check by Nagios. Instead, when an eventlog message appears on the windows box, the nageventlog agent forwards it to Nagios immediately as a passive alert. If no message arrives, no alert is sent to Nagios. Because of this, you may choose to use Freshness Checks to reset the servie status to OK, Critical or Unknown if an alert is not received for a specified period of time, depending on how you are using the agent. |
|
| Author: | jmituzas [ Sat Nov 14, 2009 10:48 am ] |
| Post subject: | Re: Nagios EventLog: FAQ |
Got it! Great software, many thanks. |
|
| Author: | jmituzas [ Tue Dec 15, 2009 3:58 am ] |
| Post subject: | Re: Nagios EventLog: FAQ |
I have created the heartbeat passive check as follows: define service{ service_description EventLog Agent host_name desktopname active_checks_enabled 0 passive_checks_enabled 1 flap_detection_enabled 0 check_period 24x7 max_check_attempts 1 normal_check_interval 15 retry_check_interval 1 check_command check_dummy!3!Check agent is running notification_interval 120 notification_period 24x7 notification_options c,r } This works for one desktop reports: HEARTBEAT [INFO #0]: Service running OK , the rest of them have been reporting pending for 3 days, also stating: Service is not scheduled to be checked... Please help me out, I have no idea why this works for one desktop and not the others. Thanks in advanced, Joe |
|
| Author: | stevesh [ Tue Dec 15, 2009 8:56 pm ] |
| Post subject: | Re: Nagios EventLog: FAQ |
You should set the check_command to check_command check_dummy!2!Eventlog agent is not running and then enable the freshness checks for this service. Set the freshness threshold to double whatever you set at the heartbeatfrequency (normally, this would be 600 sec or 10min) The freshness check causes the check_command to execute if nothing has been received for this amount of time, which sets the status to critical. Under normal conditions, an OK hearbeat is received every 5min so the freshness check never triggers. From what you say it sounds like you are not receiving heartbeat signals from most of your hosts. Check the agent is running, heartbeats enabled, and nsca configured correctly. |
|
| Page 1 of 2 | All times are UTC + 12 hours [ DST ] |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|