|
Apache Log-Monitoring
MicroApache with Tail Server logs and keeping your eye on them are the most important aspect of good webserver management. They can help you to shape the server configuration, develop new filters and rules and to focus on which content is popular and which isn't. Not to mention keeping your eye on miscreants and finding out where all of your bandwidth is going. For general managerial use a good log analyser such as The Webalyzer is great to have run automatically on a regular schedule. Say daily on a busy server or maybe once a week on a less-busy one. But for day to day monitoring and diagnosis you really need to be able to watch the server logs in "real time" This is where tail comes in. Tail allows you to monitor logs in real time. Updates to the file are displayed dynamically as they're added to the log file, line-by-line. This site offers three versions of tail which are suitable for use with either MicroApache, standard Apache or any other compatible Win32 webserver. Each of them offers different advantages and disadvantages. All versions of tail have the advantage that they can efficiently view the "tail" end of the file no matter how large it is. The entire file is never read, just the last few bytes are they're added.
There's no reason why you can't combine all 3 forms of log-monitoring at different times. I tend to use TailCGI most-often because it's quick to use, lightweight and it's convenient to bookmark particular log files once you've opened them. I use Tail for Windows on the server itself continuously for keeping an eye on the local DNS server or intrusion-logs as this makes it easy to see if my own DNS is having problems or my preferred external DNS service, OpenDNS is either blocked or down. If you have a particularly busy server it is also vitally-important that you keep your log files small and filter only useful information from each page load. If you monitor every single file then not only will the log be updating too fast for any version of tail to cope but you log files will rapidly fill your hard drive. To configure logs you may need to learn how to use mod_rewrite and set environment variables. You won't want to log every image file from every page for example, just the main HTML content. There are two logs at mimimum that you need to keep an eye on with others that can be added via configuration:
Here are some great articles on the subject
Other Log-Viewers
Other useful pages This is quite an awesome-looking log-visualiser... (Logstalgia or Apache Pong)
And this looks pretty handy too...
|
Page last updated on 25 February 2021 - This page is optimised for Mozilla Seamonkey and 1024x768 or higher screens