3 ms·
It's pretty, and sounds good. I've used Nagios for server monitoring in the past and that can be a bit of a pain, but that's because you can use it to monitor
by JohnTitus 16y ago
It's pretty, and sounds good. I've used Nagios for server monitoring in the past and that can be a bit of a pain, but that's because you can use it to monitor damn near anything. As a sometimes-sys-admin, I assume that in order to achieve your claim of "Monitor virtually any Linux, Windows or Cloud Service" that you're going to be offering only pretty basic metrics. Can you elaborate on how you'll keep it simple when dealing with virtually-infinite possible combination of server configs?
- tenaciousJk 16y agoKeeping it simple while still remaining functional for "advanced" users is one of my primary goals. We will start with the basics, but only so we can actually launch the product asap. That's really the problem we're looking to solving though. Simplifying the mess. (that includes billing) In the end, we have a certain feature set that's our internal goal. Whether their is demand for every part of that is another topic. Polling and a/b testing will determine where our development efforts are focused and how the first iterations shape up. btw, thanks :)
- JohnTitus 16y agoPerhaps use something like uservoice.com as a simple way to track feature/monitor plugin requests.