We performed a comparison between PagerDuty Operations Cloud and ScienceLogic 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."The initial setup is a simple process."
"The product has valuable on-call scheduling, escalation, and incident workflow management features."
"Notification is the most valuable feature."
"PagerDuty is very stable and very reliable."
"The SMS pages and the mobile application are pretty much the top two features."
"The alerts are immediate in this solution, which allows us to respond to errors quickly."
"PagerDuty's notification process is the most valuable feature."
"The initial setup is straightforward."
"Dynamic Component Mapping is key and unique."
"When it comes to features, the power pack is the most valuable."
"Science Logic provides distributed and all-in-one concept in monitoring, you can easily customize the features in this product."
"The flexibility to support most technologies. The way ScienceLogic gathers data from multiple sources is vital to our customers. As we work with new customers (often with different technology requirements), ScienceLogic is flexible enough to support our clients’ varying network needs."
"Its ITSM and EMS combination is really amazing. There is no need to purchase two products, one for ITSM and a second for EMS/NMS."
"It is simple."
"I'm satisfied with ScienceLogicfor for what they can offer today because they can offer both serverless connectivity and agent connectivity."
"The tool is quite easy to deploy, and it offers very good support."
"It is a very non-customizable product, so you cannot add things like root cause analysis or the classification of incidents based on the area where you are getting more incidents. For example, if you're getting a lot of database issues, that may be an are you want to probe."
"They could include incident merging and alert grouping features in the product."
"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."
"I am not a direct end user of PagerDuty. It's hard to consider its shortcomings in that sense."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
"PagerDuty can improve the integration with Terraform."
"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 user interface could be more intuitive."
"The product must educate its strategic partners for deployment."
"ScienceLogic could improve the implementation, it could be made easier."
"It doesn't have the complete application-level topology. It could have service topology and business service monitoring. I would like to see how business service monitoring will function with agent-based installation, and how flexible and business-oriented it is for service modeling and service infrastructure. I have a lot of experience in using business service monitoring, service topology, and service hierarchy functionalities in similar products from BMC and Micro Focus (OpenView), and I want to see how these functionalities will look like in ScienceLogic."
"The product's reporting functionalities have certain shortcomings, making it an area where improvements are required."
"From a performance perspective, it needs to improve a lot."
"We want to understand: how does the back end work? What if some problem occurs? What we can do? They need to provide more information."
"They should add CLI command modes and scripts for high performance."
"I would like to see out-of-the-box standard dashboards for common services."
PagerDuty Operations Cloud is ranked 8th in AIOps with 35 reviews while ScienceLogic is ranked 5th in AIOps with 42 reviews. PagerDuty Operations Cloud is rated 8.8, while ScienceLogic is rated 8.6. 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 ScienceLogic writes "Great integrations, power flow, and good support". PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and Everbridge IT Alerting, whereas ScienceLogic is most compared with Dynatrace, LogicMonitor, SolarWinds NPM, Datadog and Zabbix. See our PagerDuty Operations Cloud vs. ScienceLogic 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.
