-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restricting by hostgroup_name shows only this hostgroup and no other groups containing the host #3349
Comments
@dgoetz could you show the filters and the SQL query snippet when adding |
@lazyfrosch below we have a filter that only shows the "systemen_hosts" hostgroup. That hostgroup is defined like this:
There are many other hostgroups defined in our setup. But when you log in, you only see that one hostgroup. The filter:
|
Looks like the hostgroup filter is incomplete here. Will review it. |
The hostgroup filter is not incomplete. If you restrict objects by hostgroup_name, you restrict the hostgroups too. Though, I understand that it would be helpful to see the other hostgroups the host is part of. If we implement this, I don't think that it is a good idea to change the current behavior. We could support this via a dedicated role option or a new operator. Anyway, this feature requires a lot of coding and testing efforts. So, I don't think that we'll implement this without sponsoring anytime soon. Help would be much appreciated. |
+1 for not making this the default. And btw, |
ref/NC/620273 |
Updated OP to include the current work-around. |
Update: (by @nilmerg)
This is related to #3550 and is avoidable the same way: By custom variables.
Instead of restricting on
hostgroup_name
, use a custom variable:_host_adminonly!=yes
Original:
Expected Behavior
If I restrict access to hosts by hostgroup_name, I would like users to see also other hostgroups containing those hosts.
Current Behavior
If I restrict by hostgroup_name I only see this hostgroup.
Possible Solution
Show all hostgroups which have at least one host in it after restriction is applied.
Context
If I have many hostgroups they are probably nested or created for different purposes so limiting restricted users to see only the one hostgroup hides useful information. One example for nested groups would be different roles in project, for different purposes having groups for stages and application. Losing those groups because you are restricted to the hostgroup for the project makes using the interface more difficult as you will always have to use filters if possible at all.
Your Environment
icinga2 --version
): 2.8.0The text was updated successfully, but these errors were encountered: