Ryan Frantz defined monitoring at http://www.ryanfrantz.com/posts/solving-monitoring/ as
Monitoring is the aggregation of health and performance data, events, and relationships delivered via an interface that provides an holistic view of a system's state to better understand and address failure scenarios.
Here's my alternative definition
- Monitoring is the detection of variation outside the steady state of the business.
|$ ./bin/bit-whois.pl adobe.com|
|adobe.com variation bdobe.com is taken (ns01.domaincontrol.com)|
|adobe.com variation aeobe.com is !! ERROR !!|
|No Match Domain!|
|adobe.com variation acobe.com is taken (ns1.s416.sureserver.com)|
|adobe.com variation adpbe.com is taken (ns2.hastydns.com)|
|adobe.com variation adnbe.com is ** AVAILABLE **|
|adobe.com variation adoce.com is taken (ns2.warptech.net)|
|adobe.com variation adoae.com is ** AVAILABLE **|
|adobe.com variation adobf.com is ** AVAILABLE **|