Am 29.07.2015 um 14:57 schrieb Zachary McGibbon: Ok I could work on migrating to the new interface however I do have one question. Most everyone here at McGill uses Nagstamon on their desktop which talks to the classic CGIs. If I want to keep supporting this option will I still need to install the classicui or does icingaweb2 provide a similar interface for external applications like nagstamon?
Afaik the nagstamon developer is waiting for the rest api before implementing support for icingaweb2. But you may kindly ask him yourself :) Kind regards, Michael - Zac On Tue, Jul 28, 2015 at 7:03 PM, Michael Friedrich <<mailto:[email protected]>[email protected]<mailto:[email protected]>> wrote: Am 28.07.2015 um 18:39 schrieb Zachary McGibbon: Hi, I am in the process of converting all our Icinga1 config to Icinga2 and I'm running into a problem when trying to get user permissions setup right. We have many departments accessing our Icinga console, and we don't want them to necessarily see all hosts/services that we monitor. Here is an example of our Icinga1 config (removing unnecessary lines for the example) define host{ name poe1 contact_groups host_poe } define contactgroup{ contactgroup_name host_poe contactgroup_members noc } define contactgroup{ contactgroup_name noc alias noc } define contactgroup{ contactgroup_name ops alias ops } In this example above, only the users in the 'noc' group would be able to see the host 'poe1' in the classic ui, I believe these are the flag I set for this to happen in cgi.cfg is: show_partial_hostgroups=1 So now I'm trying out how to replicate something like this in Icinga2. For now I'm not at the point of doing notifications as those will all go to an ITOM solution which will do the proper filtering.
From what I can see you can't assign hosts into UserGroups in Icinga2? Am I missing something?
Using Notifications with Users as mapping for the compat host/service contacts is an ugly workaround, which is why we generally don't recommend doing that with Icinga 2 and Classic UI. Rather look into Icinga Web 2 offering more capabilities on limiting views to certain users and scratch that "contacts for auth"-idea. On a related note - we won't implement new Icinga 2 features into 1.x interfaces such as Classic UI or Web1, there's way more possible with Icinga Web 2 in the future. Kind regards, Michael - Zac _______________________________________________ icinga-users mailing list [email protected]<mailto:[email protected]> https://lists.icinga.org/mailman/listinfo/icinga-users -- Michael Friedrich, DI (FH) Application Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77<tel:%2B49%20911%2092885-77> GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | <mailto:[email protected]> [email protected]<mailto:[email protected]> ** OSBConf 2015 - September - osbconf.org<http://osbconf.org> ** ** OSMC 2015 - November - netways.de/osmc<http://netways.de/osmc> ** _______________________________________________ icinga-users mailing list [email protected]<mailto:[email protected]> https://lists.icinga.org/mailman/listinfo/icinga-users _______________________________________________ icinga-users mailing list [email protected]<mailto:[email protected]> https://lists.icinga.org/mailman/listinfo/icinga-users -- Michael Friedrich, DI (FH) Application Developer NETWAYS GmbH | Deutschherrnstr. 15-19 | D-90429 Nuernberg Tel: +49 911 92885-0 | Fax: +49 911 92885-77 GF: Julian Hein, Bernd Erk | AG Nuernberg HRB18461 http://www.netways.de | [email protected] ** OSBConf 2015 - September - osbconf.org ** ** OSMC 2015 - November - netways.de/osmc **
_______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
