We performed a comparison between Evanios and PagerDuty Operations Cloud based on real PeerSpot user reviews.
Find out what your peers are saying about Splunk, New Relic, Devo and others in IT Operations Analytics."The most valuable feature is the integration with various alert-generating systems because you might have synthetic alerts or monitoring alerts for volume drops."
"Provided up to a 90% noise reduction in some our noisy monitoring tools."
"The ability to manipulate events via JavaScript getting the exact data that we want."
"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."
"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."
"PagerDuty is very stable and very reliable."
"The product easily integrates with other solutions."
"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."
"The alerts are immediate in this solution, which allows us to respond to errors quickly."
"The initial setup is a simple process."
"Alert deduplication and noise reduction for alerts are the major features that I found useful."
"We would like the ability to have an "exit" option for events when they are being processed."
"The price could be cheaper."
"More complex correlation rules would be nice. The ability to clearly define a parent event in a correlation and nested correlations, specifically."
"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."
"It cannot be integrated with our upgraded Jira system."
"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."
"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."
"I would like to see more content in the notification messages; although, that might be a configuration on our end."
"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."
"This solution works best in conjunction with a proper logging system, which can be an additional cost to organizations."
Evanios is ranked 12th in IT Operations Analytics with 6 reviews while PagerDuty Operations Cloud is ranked 1st in IT Alerting and Incident Management with 35 reviews. Evanios is rated 9.6, while PagerDuty Operations Cloud is rated 8.8. The top reviewer of Evanios writes "The vendor is willing to work with us and develop solutions for products they did not already have an integration for". 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". Evanios is most compared with Splunk Enterprise Security, whereas PagerDuty Operations Cloud is most compared with Opsgenie, ServiceNow, JIRA Service Management, Splunk On-Call and xMatters .
We monitor all IT Operations Analytics 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.