Hi there,
I'm very excited in regards to the new multi-tenancy, and I have questions:
Will it be possible to sort the hostlist on a different field than IP/Host? I already manually apply a 'tag'-field appropriate to the logsource and it would be awesome if there was a possibility that I could use that rather than the 'host'.
Also, is the admin user going to be able to access the dashboards of the normal users? In my usecase, it would be nice to be able to edit the user-dashboards, and then save them under the users name. The only way to bypass it now, would be to have the direct link to the user-made (non-global) dashboard. Then you can access it normally.
Thanks in advance.
Host limitation and multitenancy?
Re: Host limitation and multitenancy?
We do have a feature request related to user dashboard management, but I'm not seeing one to sort the host list by another field. Just to expand on this a little, are you talking about the host list in the Unique Hosts page?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!
-
Wintermute
- Posts: 13
- Joined: Fri Feb 22, 2019 4:25 am
Re: Host limitation and multitenancy?
Great news with the user dashboard management - glad that there's something in the works
And yes - the 'Unique Hosts' list is the data we can currently seperate users on (as far as i know).
It's not that I wan't the list gone or anything, it's just that in my logcollection I apply a "tag" field on every log at an agent level. That "tag" is originally meant to be used with a usertenancy service just like the one you've just implemented and it's a shame that I can't use it
.
For example: Instead of having to find all the unique hosts designated for user A, I can just assign him all the hosts with the tag:USR_A. As i manage the tags at the source, all hosts with tag:USR_A, will be the ones meant for him.
To be able to seperate the hosts list based on a custom field would make the whole process of assigning hosts to user much easier for me and others who manage their sources agent-side.
Does it make sense?
And yes - the 'Unique Hosts' list is the data we can currently seperate users on (as far as i know).
It's not that I wan't the list gone or anything, it's just that in my logcollection I apply a "tag" field on every log at an agent level. That "tag" is originally meant to be used with a usertenancy service just like the one you've just implemented and it's a shame that I can't use it
. For example: Instead of having to find all the unique hosts designated for user A, I can just assign him all the hosts with the tag:USR_A. As i manage the tags at the source, all hosts with tag:USR_A, will be the ones meant for him.
To be able to seperate the hosts list based on a custom field would make the whole process of assigning hosts to user much easier for me and others who manage their sources agent-side.
Does it make sense?
Re: Host limitation and multitenancy?
Yes, that sounds like a great idea, thank you! I'll get that in as a feature request, and we'll see if we can get it implemented.
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Be sure to check out our Knowledgebase for helpful articles and solutions!