What problems is Prometheus solving and how is that benefiting you?
Nagios was our first monitoring product. We went with Nagios XI for the same reason people buy Cisco switches - nobody ever got fired for buying Cisco hardware, and nobody ever got fired for going with Nagios for monitoring. However, as we grew, we found that Nagios XI doesn't really scale. In addition, both the checks and agent were community maintained and often poorly maintained at that.
We went from Nagios to Sensu - specifically, Sensu Go, which is a greatly improved rewrite of the original codebase. Sensu Go has a really interesting architecture - it's got its own built-in mechanism, Assets, for distributing checks, and the agents are maintained by the company. But the documentation and web UI were terrible, and you were still dependent on writing all checks yourself or sourcing old Nagios checks from the community.
After Sensu more than doubled its support costs year-over-year, we decided that we'd had enough, and I finally gave Prometheus a try. My DevOps friends had been raving about how well it's designed, now I can see why. It's trivial to set up; there's a vast array of strongly-supported exporters, and it's far more flexible than simply checking whether something is running or not.
And it does scale, either through sharding instances or through other projects like Thanos. Nagios is waaay over the hill, and it shows. Sensu isn't much further behind unless they can get their act in order. I see positive things for us and Prometheus. Review collected by and hosted on G2.com.