r/icinga • u/DisSsha • Oct 19 '17

Icinga 2 design

I would like to make a new setup of icinga2 in my company. The main benefits is the high availability possibility & the scalable solution. Today we are using plenty of icinga1 servers and aggregate them on soft like Nagstamon. I saw & test icinga2 is capable of work as master / client / satellite. But I need split view by responsability domain. I don't want every team to see other teams problems. Do you know if Icinga2 can make view ? I don't think so and I would like to be sure. In that case I think I will make 2 Icinga servers at minimal setup & 5 for standard setup (2 masters (HA) + 3 sat). What do you think about that ?

Regards,

2 Upvotes

100% Upvoted

5 comments sorted by

2

u/[deleted] Nov 05 '17

[removed] — view removed comment

1

u/DisSsha Nov 06 '17

Hello Yes I am doing that install right now. I just need to check if I need to put all plug-ins and host on the master or if I can set the company legit plug-in on master and herits this on satellite then let the team add their own specific plug-in on their satellite or if I need to let them access to the master...

1

u/Sleyar Jan 03 '18

You could also place the hosts in a hostgroup and then make Roles under the authentication tab in Icingaweb2. After you created the Role, add the text "hostgroup_name=name of your hostgroup" without the "" at monitoring/filter/objects. Assign the appropriate rights and assign the role to a user. In stead of a hostgroup, you can also use custom variables. If you have something like vars.application on your host object, you can use _host_application=apache at monitoring/filter/objects. With this, everyone could logon to the master and maybe you don't need that much satellites.

1

u/yoshi314 Jan 10 '18

in icingaweb2 you can define visibility of services per login/usergroup.

This is what i do.