That is a nice solution, with Nagios 3 you could also make one contact
group receive warnings via the service definition (or a service
escalation) and then use a serviceescalation for the contact [group]
that is to receive critical notifications.
well, I have to admit I've *never* used any
On Jan 31, 2008 10:35 AM, Max [EMAIL PROTECTED] wrote:
Agreed, I have been doing a lot of refactoring as well and have seen a
very nice shrink in configuration file sizes and ease of adding new
hosts :) too.
- Max
Is 3 rc2 ready for primetime?
On Jan 31, 2008 11:24 AM, seb [EMAIL PROTECTED] wrote:
well, I have to admit I've *never* used any kind of escalations
with Nagios :) At my previous work, there was always only
one person on duty and the backup engineer was managed
manually. Nevertheless, it's quite a nice trick, I really love
On Jan 31, 2008 12:20 PM, seb [EMAIL PROTECTED] wrote:
Is 3 rc2 ready for primetime?
I use two small installations of it, one with just 12 nodes, the other
with 100 nodes/550 checks, both have been very good so far.
imho rc1 is already quite stable... ndoutils seem to fragilize (don't know
Do I need 2 similar service entries in order to have different contact
groups for warning and critical?
i'd rather play with host_notification_options and
service_notification_options : make one contact
receive only warnings and the other critical alerts, and
but both of them in the same
On Jan 29, 2008 4:21 PM, seb [EMAIL PROTECTED] wrote:
Do I need 2 similar service entries in order to have different contact
groups for warning and critical?
i'd rather play with host_notification_options and
service_notification_options : make one contact
receive only warnings and the
