We performed a comparison between PagerDuty Operations Cloud and SolarWinds NPM based on real PeerSpot user reviews.
Find out what your peers are saying about PagerDuty, Atlassian, Everbridge and others in IT Alerting and Incident Management."The most valuable feature is definitely the flexibility of the schedule. The mobile app is quite also good for what we do: for receiving alerts, acknowledging, assigning, adding new responders. It has rich features for our needs."
"The product easily integrates with other solutions."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"The SMS pages and the mobile application are pretty much the top two features."
"The initial setup is straightforward."
"A cool feature is that it helps us to understand the flow of the alert. If the alert was coming to the current on-call and he didn't catch the call or didn't notice it for any reason, it starts being escalated automatically, according to the escalation schedule, or to other teammates. You can see the flow very easily on your phone or via the website, if you want to do a post-mortem."
"The initial setup is a simple process."
"PagerDuty is very stable and very reliable."
"Monitoring capabilities are at a high level and it is easy to see utilization, access ports, and CPU memory in real time or through a lens for long-term visualization."
"Their support team is efficient, and it is easy to set up."
"SolarWinds dashboard is very fast. Also, their interface is very good, it looks very user-friendly. The product allows me to see a summary of the network being monitored at a glance."
"I can do everything remotely, including running PowerShell scripts or performing standard updates."
"A product that is well-tested and trusted in demanding situations."
"The solution is easy to install and it takes a couple of hours."
"From web interfaces to custom monitors and alarms, this product has a high level of flexibility that can be molded to suit your business needs, regardless of the size of your organization."
"The solution is stable and reliable."
"The solution's analytics are okay. I don't think the features, at this point, give you a lot of insights. We have actually been trying to get insights from it but it hasn't really given us a lot of extra points to explore. We were looking at the number of alerts to see where many of the alerts were coming from. We never managed to get many insights on this."
"PagerDuty's webhooks need some improvement."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
"The biggest area for improvement with PagerDuty is noise suppression. There have been a handful of incidents through our use of PagerDuty over the years where one incident may lead to 30 to 50 pages because you're monitoring all these different things, and each thing is an individual page. There should be the ability to set up paging tiers and group correlations between some of the different pages. That is something that would be really valuable. We should be able to say this one page may have a group or a tree of effective other pages that may tier off of it. So, if you see those pages independently, go ahead and alarm, but if you see this plus that, don't do that."
"The On-Call Teams feature could be better in terms of levels of conditions related to which team or member should get the responsibility of handling a matter or incident."
"Because of the way you have to structure the rosters, if an engineer has to go on leave (or something), you can't just go in and reassign/take this person out of all of the different rosters that they're in. You have to go into each of the rosters and take them out. There might be a roster for business hours, after hours rotation, and monitoring deployments. Each time we need to take an engineer out of the pool, e.g., if they're sick or on leave, then we have to go and touch all of those rosters, updating and replacing them. Whereas, if we could just take the person out and have it automatically fill in the rostering, then that would make life a lot easier for managing it."
"The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue."
"There is room for improvement with the time schedule. The way the schedule currently works is you assign all the team members in one schedule and it automatically spreads them around throughout the schedule... It would be better to be able to edit the schedule and place my team members where I want, or at least to have that option in addition to the automatic process."
"The only thing that can be improved is to continually add to the existing capabilities of the product."
"It would be nice to have a test to check if you can access a particular device via API without installing it and waiting for a poll cycle. You should have the capacity to initiate a test to see if it was reachable and get the results almost immediately."
"The interface could be made more user-friendly."
"Real-time analytics is the major weakness of the SolarWinds NPM platform today. They've done a fantastic job enabling the collection of data. Users are now demanding the ability to generate their own graphs, views, and so on; all of this must be done by an admin today."
"SolarWinds NPM can be very slow at times. The database optimization can be done to improve the product performance."
"In terms of scalability, there is room for improvement. When you start monitoring, if you have so many interfaces and you're trying to monitor them at a faster interval, or a shorter interval, you get to a point where you need to request another node."
"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."
"If they’re going for a “cover everything” approach, then they need to do so and enable a bit more of the "cover everything approach" within every one of the tools."
PagerDuty Operations Cloud is ranked 1st in IT Alerting and Incident Management with 35 reviews while SolarWinds NPM is ranked 4th in Network Monitoring Software with 147 reviews. PagerDuty Operations Cloud is rated 8.8, while SolarWinds NPM is rated 8.2. The top reviewer of PagerDuty Operations Cloud writes "Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure". On the other hand, the top reviewer of SolarWinds NPM writes "High-level, comprehensive, and proactive monitoring in a user-friendly interface". PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and Everbridge IT Alerting, whereas SolarWinds NPM is most compared with Zabbix, PRTG Network Monitor, ManageEngine OpManager, ThousandEyes and Entuity.
We monitor all IT Alerting and Incident Management reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.