Re: [opsview-users] Passive check state automatically revert to OK state.

Duncan Ferguson Mon, 15 Jun 2009 03:40:55 -0700

On 15 Jun 2009, at 03:13, Kang wrote:

I checked this again.

Changing State is repeats of the last manual state change to OK.

Service Ok[15-06-2009 10:57:44] SERVICE ALERT: hostname;syslog_event;OK;HARD;1;WILL THIS REPEAT? <------- AUTOMATIC STATE REVERT( This should not happen )
Service Critical[15-06-2009 10:40:48] SERVICE ALERT: hostname;syslog_event;CRITICAL;HARD;1;security[success] ....

Service Ok[15-06-2009 09:57:24] SERVICE ALERT: hostname;syslog_event;OK;HARD;1;WILL THIS REPEAT? <------- MANUAL STATE CHANGE
Service Critical[15-06-2009 09:37:48] SERVICE ALERT: hostname;syslog_event;CRITICAL;HARD;1;security[success] ....

I ran a test of this all weekend - basically set up a passive check, set the status to not-OK and left it. The state was not reverted.

Can you provide more details of your setup? The log server reports directly to the master server? Are these checks therefore asigned to the master or one of the slaves? Even though the checks are passive the nsca events should be sent to the assigned monitoring server.

Duncs

Duncan Ferguson
Senior Developer

Opsera Limited | Unit 69 Suttons Business Park
Reading | Berkshire | RG6 1AZ | UK

Phone:   +44 (0) 845 057 7887
Mobile:   +44 (0) 7968 148 748
Skype:   duncan_j_ferguson     Email:   [email protected]
www.opsera.com

Opsera Limited is registered in the

under Company Number 5396532. Our registered office is Gorse View, Horsell Rise, Woking, Surrey, GU21 4RB.

_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/listinfo/opsview-users

Re: [opsview-users] Passive check state automatically revert to OK state.

Reply via email to