Director at a tech vendor with 1,001-5,000 employees
Real User
Nov 2, 2022
The price could be cheaper. That was one reason why we switched to PagerDuty. We wanted to switch to something that provided the same features but at a lower cost. We also switched because PagerDuty provided other features like integration with ServiceNow and the scheduling of engineers. Evanios was only for event integration. Evanios created too much noise. For every alert, it would create an incident. We received too many alerts and incidents from monitoring. It wasn't able to intelligently ingest alerts. It created 4,000 incident tickets in a month, which didn't reflect what was happening. If we received an alert, the synthetic monitoring and volume drop would give us the same alert. Evanios should include alert ingestion and de-duplication of alerts and noise reduction. We couldn't have people resolving each and every incident. PagerDuty gives us reports on how many alerts are being ingested, how many are noise, how many have bigger incidents, and which of the alerts are creating noise. It would be helpful if Evanios had metrics on the amount of alerts and types of the alerts to show which ones were serious incidents and which ones were just noise.
More complex correlation rules would be nice. The ability to clearly define a parent event in a correlation and nested correlations, specifically. We would like the ability to have an "exit" option for events when they are being processed. So, if we find a condition within an event, and we no longer want to process it, we can stop it rather than have it filtered out of the rules.
Evanios offers a comprehensive approach to IT system management, optimizing workflows through integration and automation tools tailored for IT operations. It enhances efficiency by streamlining data processes and providing a unified platform for system monitoring.Designed for IT environments, Evanios integrates seamlessly with existing infrastructures, offering streamlined workflows and effective data management. Its powerful automation tools facilitate incident response and problem...
The price could be cheaper. That was one reason why we switched to PagerDuty. We wanted to switch to something that provided the same features but at a lower cost. We also switched because PagerDuty provided other features like integration with ServiceNow and the scheduling of engineers. Evanios was only for event integration. Evanios created too much noise. For every alert, it would create an incident. We received too many alerts and incidents from monitoring. It wasn't able to intelligently ingest alerts. It created 4,000 incident tickets in a month, which didn't reflect what was happening. If we received an alert, the synthetic monitoring and volume drop would give us the same alert. Evanios should include alert ingestion and de-duplication of alerts and noise reduction. We couldn't have people resolving each and every incident. PagerDuty gives us reports on how many alerts are being ingested, how many are noise, how many have bigger incidents, and which of the alerts are creating noise. It would be helpful if Evanios had metrics on the amount of alerts and types of the alerts to show which ones were serious incidents and which ones were just noise.
More complex correlation rules would be nice. The ability to clearly define a parent event in a correlation and nested correlations, specifically. We would like the ability to have an "exit" option for events when they are being processed. So, if we find a condition within an event, and we no longer want to process it, we can stop it rather than have it filtered out of the rules.