As with any new software implementation, during the integration we found a couple of minor issues when integrating certain products (such as SCOM). However, each time this happened Evanios was very quick to identify the bug we were seeing, patch it and provide the new update set for us to install.

Also, during the evaluation of Evanios we found that they already had integrations with most of our larger monitoring tools, however they also stated that they would be able to create update sets to integrate certain products we used that they did not currently support. This proved to be very valuable for us because they were able to become an even better fit for our organization by creating update sets\integrations for PRTG, Quest Foglight, TIBCO and Thousand Eyes as well.

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.

The product could be improved in providing ROI reports and reports on effectiveness of correlation etc. Rest its a rock star product and can bring value in any kind of environment where operations teams are dealing with alert fatigue.

• System information and status (easy to read for all levels of IT)
• Clearer instructions on setting up alert notifications to support staff in the event of an issue with product: There are some instructions on their support site but I'm looking for something a little more detailed to understand the flow of events (expected compared to unexpected).

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.  

• Native domain separation