Logging and Usage Tracking
What to Log?
For the most part, logging is done for two reasons: to look for problems on the server or proxy (e.g., which requests are failing), and to generate statistics about how web sites are accessed.
A few examples of commonly logged fields are:
For the most part, logging is done for two reasons: to look for problems on the server or proxy (e.g., which requests are failing), and to generate statistics about how web sites are accessed.
A few examples of commonly logged fields are:
- HTTP method
- HTTP version of client and server
- URL of the requested resource
- HTTP status code of the response
- Size of the request and response messages (including any entity bodies)
- Timestamp of when the transaction occurred
- Referer and User-Agent header values
Log Formats
Common Log Format
Combined Log Format
The Combined Log Format is very similar to the Common Log Format; in fact, it mirrors it exactly, with the addition of two fields
Netscape Extended Log Format
The first seven fields in the Netscape Extended Log Format are identical to those in the Common Log Format (see Table 21-1). Table 21-3 lists, in order, the new fields that the Netscape Extended Log Format introduces.
Netscape Extended 2 Log Format
The Netscape Extended 2Log Format derives from the Netscape Extended Log Format, and its initial fields are identical to those listed in Table 21-3.
Table 21-4 lists, in order, the additional fields of the Netscape Extended 2 Log Format.
Squid Proxy Log Format
Hit Metering
The Hit Metering protocol requires caches to periodically report cache access statistics to
origin servers.
Overview
The Meter Header
A Word on Privacy
No comments:
Post a Comment