The product we used previously was complicated in its implementation and required specific configuration for each event you wanted to generate. It was also unstable and had a high cost. Evanios is simpler in its implementation; however, we also have much more capability than we did before due to the wide range of rules that can be created, as well as the ServiceNow integration. Our previous solution was purely SNMP, so Evanios has given us much more flexibility and allowed us to get more reliable data into ServiceNow.

I also have experience with PagerDuty. They have good rules in terms of de-duplication, noise reduction, and alert integration. Evanios is a little more customizable. PagerDuty provides all of the rules, and it's not possible to change something.

PagerDuty's features are very rich, and the setup is clear. Basically, you have an endpoint and expose the endpoint in PagerDuty. PagerDuty is able to pick the alerts using those endpoints, so the setup is easier. The configuration for Evanios was a little better, and PagerDuty had a lot of other features that we needed.

Yes we used our home grown solution which was getting to complex and unmanageable so we had to fin something more scalable.

We previously used CA Spectrum. We switched because the software interface was very bulky, it required a very large network footprint and cost.

I did not previously use a different solution.