Allow optional integration of NPM Node Groups with NCM Groups. You shouln't have to create your groupings twice.
We use Solarwinds for network monitoring only. We have hundreds of customers and many internal environments as well. It is a pain in the a*$ to manage the same grouping twice! Please add this, it cannot be that much of a hassle?
The reason for buying Solarwinds product is to integrate the different systems together.. If this is not the case in real life, why should we choose Solarwinds next time?
For the love of god, please integrate them!!!
This is probably a bigger request that needs more visibility. I know this is a major disaster when crossing between NPM and NCM functions now that NCM is far more "integrated" into NPM. NPM groups are useless outside of permissions. I would like to see NPM groups overtake NCM and be selectable in compliance reporting and other features. I realize that the merger of modules is a slow process, but for a product suite that boasts integration, that integration is still a long ways off.
This is clearly a case of false advertising. You can't describe the products as integrated and require your customers to group things twice. Ridiculous at least, criminal at worst.
Wow! I always assumed they were the same thing. This explains why my report policy didn't match any nodes! I'm surprised this hasn't been addressed yet.
Has anyone got a script to sync the two?
I belive many actually do think that NPM and NCM database is the same thing. I can see that someone might have all devices monitored in NPM, but only want backup of a set of devices due to licence limitations, if this exists. This way I understand why NCM and NPM groups are separated.However, the real problem for me is that I cannot setup ALERTS based on NPM groups, only NCM. This makes no sense to me, as alerts usally is originating from NPM. Maybe I should add this as a separate request..
The other issue here is that you can't have a single node be a member of multiple "groups" in the NCM node groups. We ended up just using them like tags and wild card searching for them like "iseDevices, energyWise" then search Node Group LIKE '%iseDevices%', etc.
so this is a issue, what it shows is the old heritage of NCM being Cirrus and not integrated still into Orion after all this time It should be a simple option or selection. Meh.
