Five observations about why your server monitoring still
stinks by a monitoring specialist-turned-consultant.
Early in my career, I was responsible for managing a large fleet of
printers across a large campus. We're talking several hundred networked
printers. It often required a 10- or 15-minute walk to get to
some of those printers physically, and many were used only sporadically. I
always know what was happening until I arrived, so it was anyone's
guess as to the problem. Simple paper jam? Driver issue? Printer currently
on fire? I found out only after the long walk. Making this even more
frustrating for everyone was that, thanks to the infrequent use of some of
them, a printer with a problem might go unnoticed for weeks, making itself
known only when someone tried to print with it.