We performed a comparison between PagerDuty Operations Cloud and Zenoss 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."It has scaled well for us."
"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."
"The alerts are immediate in this solution, which allows us to respond to errors quickly."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"The initial setup is a simple process."
"The most valuable feature of PagerDuty is its integration with other tools, such as Amazon AWS, to receive notifications or create automatic instances."
"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 offers good documentation that helps with initial training."
"Its Docker Container concept is mind blowing. It is the first monitoring tool which comes with Docker features."
"They have also accommodated many state-of-the-art technologies like Docker and ZooKeeper."
"The custom built integration is one of the most valuable features because you can see all the especially critical items."
"It's easy to use."
"The most valuable feature is the flexible discovery mechanism."
"What I like most about Zenoss Service Dynamics is that it monitors the devices and gives close to real-time alerts. For example, in case the device is not available, Zenoss Service Dynamics generates an alert so my team can resolve the issue."
"PagerDuty's webhooks need some improvement."
"The solution does not code all alerts correctly so sometimes you get false positives or multiple alerts for the same issue."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
"It’s quite hard to reach the support team."
"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."
"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."
"It cannot be integrated with our upgraded Jira system."
"PagerDuty could improve the event orchestration by enhancing features, such as easier condition setup inside the orchestration."
"The inclusion of a feature to show a graphical view of the network would be a helpful improvement."
"As Zenoss Service Dynamics is more for network-centric devices and you want to monitor, for example, a server, its services, IP addresses, and interfaces, if it's a network and you're going to monitor multiple items, you'll be charged multiple times. This is what Zenoss Service Dynamics needs to improve to make sure that customers pay just one fee to monitor the entire server. What I'd like to see in Zenoss Service Dynamics in the future is a public cloud monitoring feature, particularly for the Azure public cloud. Another additional feature I'd like to see in the next release of the solution is integration with the Azure public cloud because I know that there are some services from Azure that Zenoss Service Dynamics is currently unable to monitor."
"There was a problem with Zenoss and storage monitoring."
"There is room for improvement with the administrative part. They introduced Control Center to manage things in Zenoss 5. The services that Zenoss provides remained the same, but the administrative part, since they introduced Docker, etc., has become a little complex"
"The AI aspect needs to improve."
"It would be ideal if the product offered sound alerts."
"Now it is stable, but they should design threshold parameters in percentage instead of raw values."
PagerDuty Operations Cloud is ranked 8th in AIOps with 35 reviews while Zenoss Cloud is ranked 16th in AIOps with 8 reviews. PagerDuty Operations Cloud is rated 8.8, while Zenoss Cloud is rated 8.4. 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 Zenoss Cloud writes "Generates close to real-time alerts so users can resolve issues, but needs more integration and public cloud monitoring features". PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and Everbridge IT Alerting, whereas Zenoss Cloud is most compared with Zabbix, Nagios XI, ServiceNow IT Operations Management, SCOM and ScienceLogic. See our PagerDuty Operations Cloud vs. Zenoss 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.