It certainly means different things to different people: As sysadmins, we want to know our systems are ok, to the slightest detail, and if not, what is wrong. Preferably before, or at least while it happens. As (enlightened) developers we
want to be able to follow our applications behaviours in production. As service managers we want to know if were delivering the service as agreed. Whats up, down, for how long, how slow, whos to blame. As managers we might want to know the bottom line, of how many downloads, sales,..in a pretty Widget. You can probably think of a few more. And you're probably not happy with that you have (or you wouldnt have monitoringsux), which is most likely different systems runing besides each other, with different paradigms, platform-dependent APIs (if any), Different Web GUI with lineair lists and state colors, that you force to refresh ever few minutes, and even then look at old information, and that have credentials to authenticate to the systems they monitor, making them dangerous points of failure in terms of security.
Depending on what you're trying to monitor, you may be OK with all of these. But if you're like us, youll end up in a multi-everything (platform, application, networks, silos, sites, policies) environment with no end of interdependencies, where at least some applications are interactive and time-critical, and the sysadmins and developers are collegues, horizontal team members, or all the same people. This is the type of environment that were growing Extremon for. Taking 3 important headlines from the Extreme Monitoring Manifesto:
- Live, with Subsecond temporal resolution
- Hot-pluggable components
- Display on a meaningful representation, and in real-time.
.. We Go for it.