Our department is responsible for monitoring the network and servers for
our portion of The Company Network. Basically, we watch the output from
several monitoring tools and call the sysadmins when something goes
Our primary monitoring tool was taken away from our department and spun
off into its own department, so we're no longer responsible for monitoring
the output from that, which is good, because the day the new
department is formed the tool stops working because of a failed upgrade.
It's been two days now.
That's okay, because we have multiple monitoring software. Only two
other packages we use to monitor the Windows NT servers both crash. So
there is no way to monitor the Windows NT servers.
But that's still okay, because we have monitoring tools for the
Unix servers. Only we've been told that it's not terribly reliable. We
certainly seem to be devoid of monitoring tools in a monitoring
Welcome to the Cheese
You have my permission to link freely to any entry here. Go
ahead, I won't bite. I promise.
The dates are the permanent links to that day's entries (or
entry, if there is only one entry). The titles are the permanent
links to that entry only. The format for the links are
simple: Start with the base link for this site: https://boston.conman.org/, then add the date you are
interested in, say 2000/08/01,
so that would make the final URL:
You can also specify the entire month by leaving off the day
portion. You can even select an arbitrary portion of time.
You may also note subtle shading of the links and that's
intentional: the “closer” the link is (relative to the
page) the “brighter” it appears. It's an experiment in
using color shading to denote the distance a link is from here. If
you don't notice it, don't worry; it's not all that
It is assumed that every brand name, slogan, corporate name,
symbol, design element, et cetera mentioned in these pages is a
protected and/or trademarked entity, the sole property of its
owner(s), and acknowledgement of this status is implied.