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.
A key component of the Event Management process is consolidation of events from across the enterprise. By consolidating disparate events into a single solution, they can be de-duplicated and correlated. For example, network failure events can be correlated with system failures, and then prioritized based on service impact.
Reduce the noise
Evanios Integrations allows filtering and processing close to the event source, keeping the weight off of the ServiceNow system for increased performance....
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.