Not sure if the title is correct so hope this clears up the questions. We have been using NPN for a few years and have several nodes entered. We now have other divisions that want to start to add there nodes into NPM. What we want to do is allow the division to add there node but only they will see what nodes they have entered and not see the nodes others have added. I can not find anything in Solarwinds documentation or here on THWACK. Is there anyway this is possible?
There are a lot of ways to do this. In all cases you would want to apply account limitations to filter them to only see nodes that are intended for their consumption. The specifics of how you set up that limitation are up to your organization. You could set them up based on dynamic queries in groups, aka if the node names would have some way of indicating what division they belong to, or maybe specific ip blocks. Another way is to set up a custom property to tag the nodes by whatever division they are in, but the danger in relying on a custom property that you have to set manually is that if someone forgets to set it or sets the value incorrectly then that node would effectively disappear from them and they wouldn't be able to correct it without help from someone who is not under the same limitation. Ideally you want to come up with a way of differentiating the nodes that does not require anyone to manually do anything.
Thank you. That is a great list of solutions. The one thing that will happen before this is the node needs to be added. I’m not to keen on giving everyone right to manage nodes before the group step. Or can I just set the group limitation and give them node management rights and they can only add or delete there nodes from the group?
The latter, if you give them management they can manage any nodes they can see, but with the account limitation they will only see nodes that match the criteria you set up on their account.
In short yes you can, and that's exactly what we did. There was a department in our organization that had a fairly small IT department with a small budget. We offered to manage their equipment in Solarwinds as a service to them. This is what I did to achive what your taking about.
However, there are some caveats to be aware of.
The beauty of it all, I've added multiple user groups and they all have limitations on what they see, with the exception of alerts and events. They all have a feeling of ownership of Solarwinds and they can do what they need to do with out pulling me away from doing what I need to do.
SolarWinds solutions are rooted in our deep connection to our user base in the THWACK® online community. More than 150,000 members are here to solve problems, share technology and best practices, and directly contribute to our product development process. Learn more today by joining now.