I thought about a really dirty way to do it. I have seen I can filter user visibility to hosts using regexp in name. If I force to use some prefix per instance in hostnames I could filter in user profile using a host-name based pseudo instance filter.
Please, help me to find a real instance filter per user. This solution is really derty. Thanks, txemi On Fri, Apr 11, 2014 at 2:30 AM, txemi <[email protected]> wrote: > Thanks for your response. > > I have checked that I can create custom cronks with filters that it > seems I could use to create "custom limited views for users". I did it > from user interface with no need to edit files or write code. I could > also use de instance field as filter that is what I needed. > > I also was able to create new users. > > What I did not manage to do is restrict these uses to view only a > subset of cronks. > When I create user I add it to icinga.user credential that it seems > is the minimal credential I need to let him log in, but as soon as I > do this the new user has access to all default cronks and I do not > want that. Besides, new user cannot see new custom crons that seems to > own to admin user. > > I am using ubuntu 13.10 with default packaged icinga-web that is > 1.9.0+dfsg1-3. I tell that in case acl over cronks is not available > and that is the reason for me not finding it. > > Thanks > txemi. > > On Tue, Apr 8, 2014 at 4:03 PM, Michael Friedrich > <[email protected]> wrote: >> On 07.04.2014 22:40, txemi wrote: >>> >>> Hi, I am building a distributed monitoring architecture and I selected >>> icinga because it seems to fit my needs. >>> >>> - I have one icinga basic on each network I want to monitor. >>> - I have one icinga-web on a machine receiving alerts from all >>> previous icinga classics using ido2db and idomod as usual. >>> - I use instance name on icingal cassic so I can distinguish data on >>> icinga-web machine. >>> - For my project each network monitored has one administrator that >>> only care about its network, so he should not see other network hosts >>> in icinga-web. >>> >>> At this point every user can see every host on every network and it is >>> not what I want. >>> >>> As I have seen icinca-web has user and group capabilities and >>> permissions on hosts and services, but I am not able to define >>> visibilities upon instance what I think it should be easier. >>> Could anyone help me with this? I did not find a way to do it from >>> user interface and I have started to inspect the code looking for >>> where to touch to achieve this. I would like to do that with icinga as >>> it seems if fits my needs and there is no need to develop a complete >>> new user interface layer for this. >> >> >> Filter by 'instance' (values provided with idomod.cfg:instance_name) and >> save a custom cronk. >> >> >>> >>> Thanks, >>> txemi >>> _______________________________________________ >>> icinga-users mailing list >>> [email protected] >>> https://lists.icinga.org/mailman/listinfo/icinga-users >>> >> >> >> -- >> DI (FH) Michael Friedrich >> >> [email protected] || icinga open source monitoring >> https://twitter.com/dnsmichi || lead core developer >> [email protected] || https://www.icinga.org/team >> irc.freenode.net/icinga || dnsmichi >> _______________________________________________ >> icinga-users mailing list >> [email protected] >> https://lists.icinga.org/mailman/listinfo/icinga-users _______________________________________________ icinga-users mailing list [email protected] https://lists.icinga.org/mailman/listinfo/icinga-users
