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.
