We performed a comparison between IBM Tivoli NetCool Impact and PagerDuty Operations Cloud based on real PeerSpot user reviews.
Find out what your peers are saying about BMC, ServiceNow, Microsoft and others in Event Monitoring."This product allows us to make use of open-source products, including running Java code."
"The most valuable feature that comes with Netcool/Impact is the ISPF APA support. It is inherent to Netcool/Impact, so I can use the ISPF of any other product, which I can invoke and consume through Impact, and do integrations, which is great. I run the Netcool desktop application so I can integrate with other applications in the ticketing system. It's a great ability being able to invoke ISPF and integrate."
"The solution is great at being able to fetch almost any kind of file."
"It is easy to integrate with other models such as Oracle, other systems, external systems, and to reach events."
"The inbound integrations that PagerDuty provides with most of the DevOps tools are valuable."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"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."
"PagerDuty's notification process is the most valuable feature."
"The solution's most valuable features are that it adds each alert as a service, has good scheduling capabilities, and includes the ability to write logic based on texts."
"The product easily integrates with other solutions."
"The most valuable features of PagerDuty are customization, access, policies, and different rules regarding the path of escalation. Additionally, it's easy to use and create overrides. For example, if you all are on a call for one week each, but somebody wants to go on PTO, the team needs to swap shifts in PagerDuty. This is easy to do by creating overrides to switch up the set schedules. It's very user-friendly in that aspect. It works well for monitoring and alerting."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"For improvement, I'd say the dashboard and the overall GUI could use some work. Although, I don't think that there's much improvement that Netcool really needs to achieve in this area, because when we're talking GUI, Impact is able to integrate with any third-party system and it comes with ISPF APA. It's more beneficial than Netcool/OMNIbus in this respect, and it's quite easy to handle."
"The solution is somewhat complicated. It's not exactly straightforward."
"Stability-wise, this product needs to be improved."
"IBM is not investing in the development of the on-premise version of this solution."
"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."
"They could include incident merging and alert grouping features in the product."
"I would like the UI to be more intuitive. I would like to be able to group or color-code the discoveries. When you create a system, you have a listing of all the different configurations. You can list them by teams, but some additional color coding would be helpful. I would break it down by incident controls. In other words, it should be broken down it into response teams and engineering divisions."
"Something that needs to be improved, is adding multilingual support."
"The user interface could be more intuitive."
"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."
"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."
"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."
IBM Tivoli NetCool Impact is ranked 9th in Event Monitoring with 4 reviews while PagerDuty Operations Cloud is ranked 1st in IT Alerting and Incident Management with 35 reviews. IBM Tivoli NetCool Impact is rated 7.8, while PagerDuty Operations Cloud is rated 8.8. The top reviewer of IBM Tivoli NetCool Impact writes "Supports APA through ISPF and lets us easily integrate with other apps for ticketing purposes". 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". IBM Tivoli NetCool Impact is most compared with IBM Tivoli NetCool OMNIbus, ScienceLogic and IDERA SQL Safe Backup, whereas PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and Everbridge IT Alerting.
We monitor all Event Monitoring 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.
