Posts tagged Monitoring
LogicMonitor automatically monitors an array of standard information about a web server, from CPU and memory use via SNMP to status and response time for a default HTTP query. If your web server performs a few critical functions, you can also monitor a specific page or service by URI.
One of the many cool things LogicMonitor can do is auto-discover your Apache web server and collect server statistics on it. This requires that the server have the mod_status module enabled, and that the LogicMonitor agent have access to the server-status page.
Normally, this is controlled by a Location block in the Apache server configuration, which associates the server-status handler with the URL path. Since you probably don’t want to let the world know exactly what your server’s doing, the block also defines which hostnames or IP addresses are allowed to get access to it.
Ok, so maybe I’m a touch paranoid, but I like logging. I also like monitoring, and statistics. I like to know what’s going on, when and how. I don’t mind a little noise, as long as I can quickly assess what’s happening with my servers.
Or “How I Stopped Worrying and Learned to Love SaaS”
I touched on monitoring in an earlier post but I thought that I would expand on my thoughts.
Let me just get this out there: LogicMonitor (company site) is awesome. It’s not perfect (what is?), but it’s amazing, simple, straightforward, and it works. It combines effective monitoring with graphing (metrics); it’s easy to understand and customize and it works.
Repeat: It works.
LogicMonitor is a really cool server and network monitoring and measurement system which we’ve been working with. It uses a lightweight monitoring agent installed on your local network which collects data from your systems and passes it over SSL to an external aggregator. It’s capable of auto-discovery and is mostly self-configuring though you can adjust many of the metrics. After many years of working with patchwork monitoring and alert systems we’re pretty excited about it. Call us if you’re interested.
Setting up a monitoring agent on your local network is easy. The server hosting the agent just needs a JRE (Java Runtime Environment) installed using version 1.6 or greater and must be able to make an outgoing SSL connection. To monitor Windows systems, you’ll need to install the agent on a Windows server.