Forum Moderators: DixonJones

Message Too Old, No Replies

apache logs

interpreting log files

         

cardpro

12:10 am on Mar 14, 2005 (gmt 0)

10+ Year Member



Where or how can I learn how to interpret my apache log files?

larryn

1:00 am on Mar 14, 2005 (gmt 0)

10+ Year Member



Depends upon what you mean by 'interpret'. If you want to learn the layout, go to the Apache foundation web site. If you want to analytics from the log, I'd suggest going to the a directory (Yahoo or DMOZ for instance) and finding a product that suits your needs.

cardpro

1:23 am on Mar 14, 2005 (gmt 0)

10+ Year Member



Basically, I want to be able to look at mt server logs and interpret the data. How can I access a list of codes and their meanings (404, 200, 148 etc)?

Stefan

2:13 am on Mar 14, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Try a search like this:

[google.com...]

There are many sites with explanations using that query, and others.

cgrantski

12:52 pm on Mar 14, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



The codes are also explained in a lot of places if the Apache explanation pages don't, try searching on "404 302 304 500" (no quotes).

the_real_io

5:15 am on Mar 15, 2005 (gmt 0)



To get an understanding of the different pages and their meanings, you should read rfc2616 (a Google search for "rfc2616" is a good place to start).

On the other hand, if you want to interpret and represent the data in your logfiles, you may try using something like Webalizer. It is a free web server log file analysis program (my Linux distribution had it included).

I hope this helps.

cardpro

1:58 pm on Mar 15, 2005 (gmt 0)

10+ Year Member



Thanks for all the input. Do you have to have your own server to utilize something like webalyzer? Microsoft bCentral hosta my website and generates my web logs.

cgrantski

2:21 pm on Mar 15, 2005 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



No, not at all. The free and inexpensive programs
all run on your desktop. It's best if you put copies of your logs on your desktop as well.

If you're going to get into this area, I guarantee you will benefit greatly from a) carefully reading the documentation of whatever program you run, which will hopefully explain the basics, b) getting a book on the topic. Two books that tend to be recommended often are by Jim Sterne and by Eric Peterson; they are easy to find on Amazon etc.