The integration portion of VMAN with NPM is lacking.
1. I keep having to re-sync constantly between npm and vman. Which means there is always stale and obsolete data. I shouldn't have to be constantly re-syncing the integration.
2. Many times I've had to flat out disable integration and start over again because re-sync's where not working any more. Again this shouldn't be the case.
3. It would be a great idea to have npm not monitor servers in a vm environment and just better integrate vman to do the monitoring and us NPM resoruces for better alerting and reporting.
What gets us upset is the inconsistency. And the fact that you can integrate and see the information from vman on npm but yet you can't alert on it till you actually add the device to npm. This is a pain to do as now you have monitoring from both ends and no proper way to build alerts for vman monitoring.
Here is a design concept I'd like to offer up. Why not integrate VMAN completely into NPM? Or of it remains a appliance why not integrate between them better? What I am saying is this. NPM will monitor Network devices. And other devices but leaves vman alone. And vman monitors virtual infrastructure but plays nice with solarwinds so that solarwinds can still take charge of the alerts and reporting for vman and the vm infrastructure. When this happens you no longer need to add the device to npm. The device is added to vman which is part of npm. The alerts are for vman and gives better information about the vm systems. same with reports.
The way it is right now it's not user friendly. And while I can understand it just fine, to explain things to others who may not have the same knowledge level as me becomes a nearly impossible task to complete. With the above. I can better explain to those who have questions. Ending frustrations and making SolarWinds look better.
Top Comments