Sr. Network Engineer at a comms service provider with 10,001+ employees
Real User
2021-03-30T20:02:00Z
Mar 30, 2021
There are some tweaks and enhancements that I've already requested. One is to be able to make changes per device rather than as a global setting. That has to do with naming. It's minor.
One area that requires a little bit of improvement is the topology of visualization and being able to map out connections, end-to-end. It's able to do that, but it's not as impressive as we would like it to be. We would like to understand the different interface types and the connection points better, through the visualization. Heatmaps also need further development. In addition, you can take a device and look at all the metrics that are being collected or enabled. But having a quick map view of the KPIs versus the alerting policies that we've built around a device, and being able to map that quicker and have a one-to-one correlation, would be useful.
Operations Engineer at a government with 5,001-10,000 employees
Real User
2020-12-03T22:35:38Z
Dec 3, 2020
It sometimes does get false positives. Sometimes, it'll move something when it really wasn't a performance metric. I've seen it do that, but it's pretty much an automated tool for performance. We've only got about 500 virtual machines, so lots of times, I'm able to manage it physically, but it's definitely a nice tool for a larger enterprise that might be managing 2,000 or 3,000 virtual machines.
Analyst of Budgets and Financial and Administrative Information at a tech services company with 1,001-5,000 employees
Real User
Top 10
2020-10-22T09:59:00Z
Oct 22, 2020
As I mentioned before, there are cheaper solutions available. Earlier, our management team only managed ICMP, like IP SLA. That's why, at that point in time, we decide to use Cisco IP SLA. Well, I don't know if it's in development at SevOne, but some similar solutions offer end-to-end visibility, both regarding the server and also the network elements. Other solutions also include the server and some additional layers, like an operating system or database, and in some cases, the application, too; their network elements are designed for management-level. I don't know if SevOne plans on incorporating these features into their next release, but they should. On a scale from one to ten, I would give SevOne a rating of nine.
Learn what your peers think about IBM SevOne Network Performance Management (NPM). Get advice and tips from experienced pros sharing their opinions. Updated: March 2024.
The IBM® SevOne Network Performance Management (IBM SevOne NPM) solution helps you spot, address, and prevent network performance issues early with machine learning-powered analytics from a single source. Boost network performance and improve your user application experience by proactively monitoring your multivendor end-to-end network across enterprise, communication, and managed service provider networks.
Transform raw network performance data into intelligent and actionable insights. The...
There are some tweaks and enhancements that I've already requested. One is to be able to make changes per device rather than as a global setting. That has to do with naming. It's minor.
One area that requires a little bit of improvement is the topology of visualization and being able to map out connections, end-to-end. It's able to do that, but it's not as impressive as we would like it to be. We would like to understand the different interface types and the connection points better, through the visualization. Heatmaps also need further development. In addition, you can take a device and look at all the metrics that are being collected or enabled. But having a quick map view of the KPIs versus the alerting policies that we've built around a device, and being able to map that quicker and have a one-to-one correlation, would be useful.
It sometimes does get false positives. Sometimes, it'll move something when it really wasn't a performance metric. I've seen it do that, but it's pretty much an automated tool for performance. We've only got about 500 virtual machines, so lots of times, I'm able to manage it physically, but it's definitely a nice tool for a larger enterprise that might be managing 2,000 or 3,000 virtual machines.
As I mentioned before, there are cheaper solutions available. Earlier, our management team only managed ICMP, like IP SLA. That's why, at that point in time, we decide to use Cisco IP SLA. Well, I don't know if it's in development at SevOne, but some similar solutions offer end-to-end visibility, both regarding the server and also the network elements. Other solutions also include the server and some additional layers, like an operating system or database, and in some cases, the application, too; their network elements are designed for management-level. I don't know if SevOne plans on incorporating these features into their next release, but they should. On a scale from one to ten, I would give SevOne a rating of nine.