SolarWinds NPM pros and cons

There should be a little bit more integration in some of the other tooling and utilizing the APIs of devices or tools could be a little bit better.

If they could combine everything into one product, that would be very helpful.

The dashboard of the solution is an area with certain shortcomings that need improvement.

We also had to be attentive to vulnerabilities, because SolarWinds NPM have some issues in that area. We had to work with our security team, so that they could help us check and backup the data, and check what they needed to secure.

The only real caveat that we have or that I have an issue with is when I go on vacation, it's a little hard for me to go and modify alerts so that I don't get alerted about things when I'm on vacation.

An area for improvement in SolarWinds NPM is the short retention period. Currently, it's just for seven days of data, which is very low, making it hard for my organization to keep that data. SolarWinds recommended a seven-day retention period, but my organization needs a fourteen-day data retention period. Hence, I'd like an increase in the retention period or the database limit in SolarWinds NPM because you can't go back to the data for any investigation if seven days have passed. Another area for improvement in SolarWinds NPM is the database, which needs to be a bit more mature. I want a modified database in the next release of SolarWinds NPM. I'd also like more options added to groups because, currently, it's very limited.

The integration with the APIs and the web servers deployed can definitely be improved.

SolarWinds NPM could improve the graphics of the interface and more customized reporting.

The dashboards for this solution could be improved. We would like to divide the dashboards to give a clear view to our management team to show what we have and what deficiencies exist in our network.

They need to work on their automation and automatically discover devices. They are not very good at automatically discovering devices.