--_000_8965F13223A9A44DBBC6C62EB5589B9E0B46676040qtdenexmbm20A_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Thank you to everyone who works on developing Nagios!
I am currently using Nagios 3.0.6 on Solaris 10 update 6 on i86
Here are some changes I would like to see in Nagios.
1) It seems awkward to me that during a defined escalation, the escala=
tion contact_groups *replace* the contact_groups defined in the host or ser=
vice check. It would make more sense (to me at least), if the escalation co=
ntact_groups were *added* to the list of notifications.
2) I also think it would make more sense if increasing severity of esc=
alations could be defined, with additional contacts added at each level. Fo=
r example a service defined with "HelpDesk" as a contact for *all* notifica=
tions; a "Severity 1" escalation being defined as beginning with the 3rd un=
handled notification and adding the contact group "Supervisors"; a "Severi=
ty 2" escalations being defined as beginning with the 6th unhandled notific=
ation and adding the contact group "Managers", etc. On the 7th notification=
all three groups would be getting notified without having to define "HelpD=
esk" as part of "Severity 1", or both "HelpDesk" and "Supervisors" in "Seve=
rity 2".
3) Different escalations definable for different severity of alert, Wa=
rning, Critical, Unknown, etc.
4) Apparently notifications and escalations do not work the same for p=
assive checks as active checks. I have defined passive checks with "notific=
ation_interval 60" and escalations with "first_notification 3". My expectat=
ion was that this would behave exactly the same as an active check would, n=
otifications hourly to the group defined in the check, with escalations aft=
er 3 hours to the group(s) in the escalation. In fact, since the passive ch=
eck only happens once each day, I only get one notification to the contact =
group defined in the service on each of the first two days, and then notifi=
cations to the contact groups defined in the escalations thereafter. Not wh=
at I expected.
Thanks again,
Matthew
--_000_8965F13223A9A44DBBC6C62EB5589B9E0B46676040qtdenexmbm20A_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<o:shapedefaults v:ext=3D"edit" s
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]