We performed a comparison between DX NetOps and PagerDuty Operations Cloud based on real PeerSpot user reviews.
Find out in this report how the two AIOps solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."I like that it provides an overall view of our network. From the topology view to every event, we can view it. We can also see the interface utilization for future capacity planning. It fits our use case and environment."
"It's good for root cause analysis for network problems and network link problems."
"The AI is the best feature in this solution."
"It is straightforward to configure, and you can quickly gather data from your infrastructure."
"The solution is stable."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"PagerDuty is very stable and very reliable."
"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 alerts are immediate in this solution, which allows us to respond to errors quickly."
"PagerDuty's best features are the dedicated application that allows me to reach my engineers immediately and the ability to directly assign specific tasks to individuals and have them report back."
"PagerDuty let us set up rosters based on our shifts. We could assign a hierarchy for how the calls should be escalated and the number of times the call will be transferred between people before it is answered. It makes it easy to access an agent via mobile phone."
"Notification is the most valuable feature."
"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."
"Technical support needs to be better. They need to be more knowledgeable and responsive."
"One improvement that could make the product better is to streamline its modules into a more cohesive solution."
"Technical support could be more responsive."
"It would be better if they had an NFA network analysis feature. We appreciate features like extended network security for bucket flows, but it would be better to have some IDs, IPS functionalities, DDoS, or something like that."
"Lacks dashboards and better integration with other solutions."
"It cannot be integrated with our upgraded Jira system."
"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."
"PagerDuty can improve the integration with Terraform."
"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."
"PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration."
"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."
"PagerDuty should be integrated with other tools, so it can import the IT roster automatically. Our other rules continue to work once they're configured, but the roster must be added manually."
"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."
DX NetOps is ranked 11th in AIOps with 5 reviews while PagerDuty Operations Cloud is ranked 8th in AIOps with 35 reviews. DX NetOps is rated 8.6, while PagerDuty Operations Cloud is rated 8.8. The top reviewer of DX NetOps writes "Good performance, simple setup, and helpful for root cause analysis". On the other hand, the top reviewer of PagerDuty Operations Cloud writes "Effectively generates alerts for incidents, making it suitable for 24/7 monitoring of infrastructure". DX NetOps is most compared with DX Spectrum, SolarWinds NPM, AppNeta by Broadcom, PRTG Network Monitor and IBM SevOne Network Performance Management (NPM), whereas PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and Everbridge IT Alerting. See our DX NetOps vs. PagerDuty Operations Cloud report.
See our list of best AIOps vendors.
We monitor all AIOps 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.