Nagios Support Forum

Hey Ludmill,

I'm not sure what
has to do with the issue I'm describing.

But if the developers think this is expected behaviour to change a configuration in CCM (notifications from skip to on) with XI gui, who am I to say it does not seem very logically.

When a Nagios XI admin chooses to make use of templates and decides to set the notifications to 'Skip' and inherit the property from the template, the Nagios XI gui will kind of mess things up over the years, as the changes done in Nagios XI gui are done by other user then the Nagios XI admin. He can not know all the changes that are done by all the users with enough permissions to reconfigure a service.
If in 2 years the Nagios Xi admin would have a problem where all services making use of a template start sending out too many alerts and he would like to stop these services from sending notifications, he would configure the used template notifications enabled option to off. All the services making use of the template that still have the notifications enabled on skip would stop sending alerts, but the ones that have been changed unwillingly by other Nagios user who would for example only add a contact or whatever small config change, would keep on sending alerts.

As this is not really a big issue, I'm not going to pursue this. I just don't really get the point.

Grtz

Willem

What you describe is systemic to how nagios core users work. We are adding a feature in a future release to unify the ccm and XI logins, which will allow for user changes in the ccm to get logged to the audit log. This may also provide a way to further restrict users. If you want to stop a user from "reconfiguring" a service, make them read only.

Ok, Andy. You can close this thread.

Thanks!

This issue was fixed and incorporated into the trunk release of Nagios XI. This fix should be in the current version of Nagios XI.