Opsview is incredibly stable. We only had one maintenance window, where people said, "It's going to be offline for two hours while we update the backend." But the good thing is we did not do the updates. They did all the care and feeding of the OS, the apps, and the databases.

Opsview is a very stable solution.

I rate Opsview nine and a half out of ten for stability.

It is a stable solution.

We have not encountered any stability issues whatsoever, and I was a little concerned with this at first, since we were seeing dropped packets on our heavy SNMP usage before we migrated; have not had a dropped packet since we switched.

It's working. Sometimes the collector goes off, but it restarts by itself. Occasionally, it happens. During those times, we need to restart the services and investigate what is happening.

I would rate the stability of this solution an eight out of ten. 

Previously, an upgrade brought about some issues of instability. We were able to work through them, though, with the help of Opsview support.

For the most part it’s stable. We had some issues when I took the product over from an engineer who left and we were dealing with scalability. We had to address how it was architected. Opsview was pretty good about getting with me and helping me to come up with a plan and correct that. When we rolled out that solution, it's been pretty rock solid ever since. We haven't had many stability issues.

Every once in a while, we'll hit some kind of weird, wonky bug or something like that and we'll get with them, and either there's a fix or there will be a fix and some update or something along those lines.

We have had some stability issues, but that is largely because we're using an unsupported database. The product itself is stable.

No, we have had no stability issues.

We have had no issues with the stability.

Since Opsview heavily relies on MySQL and InnoDB, backups or large installations can be slow. You will need to put a lot of time into tning your database in order to keep it performing well.

It has just sat working forever throughout the last seven years without any problems.

We have not experienced any significant issues. We have had one slave crash in five years, and due to the redundancy, there was no loss of monitoring. We had the master break once, but due to the independence of the monitoring slave clusters, all we lost was the central management. Each slave can be run with its own web interface.

We did not encounter any issues with stability in our implementation.

There have been no performance issues.

There were no issues with the stability.

There have been no stability issues since we began running it in December. The only time it's been down was when we were patching the server that it runs on. All the services run, even with out new service watchdog. It monitors itself and I haven't gotten any notes about it going on.

Of course, you have to maintain the database. But to tell you the truth, we've put enough pressure on the system itself and it's been pretty reliable so far. It's low maintenance and a very, very reliable system.

No stability issues.

Often the webpage becomes inaccessible and you need to refresh the page.

Sometimes Opsview has crashed, but the multiple master/slave solution provides consistent uptime for monitoring.