text here
 Viewing Your Access Log

RealServer can create reports of historical data that let you see trends and gather information. Track who visited your site and for how long; what clips they watched and whether they watched them all the way through to completion. This information is stored in the access log. Your access log is available to you at a specific URL address sent to you by email when you subscribe, for example:


Access Log

The RealServer access log records the IP addresses of the clients that have connected, the clips they listened to, the times of day they connected, and more. This information can give you an idea of who your audience is. New information is appended to the end of the access log.

Reading an Access Log

Access Log Format

RealServer stores information about each clip it serves in a separate record. Each record is delimited by a new line. Fields within each record are separated by spaces.

One record is created for every clip served; if the client requests a presentation that includes several clips, one record is created for each clip in the presentation.

Remember your access log file is updated every hour on the hour and the log file time may not be your time zone. You may need to aquire thiord party software to interpret the data graphically.
See tables below for information on how to interpret each line of the access log:


This is the way each line actually appears in your access log file: - - [07/Sep/1999:13:33:26 -0600] "GET ~user/live.rm PNA/10" 200 43200 [Win98_4.10_6.0.6.45_play32_SF60_en-US_586] [UNKNOWN]
And the following is a description of each part of the line above:
client_IP_address - - [timestamp] "GET filename protocol/version" HTTP_error_code bytes_sent [client_info] [client_id]

The following is a full description of each field in an access log file line:

Access Log Format
Access Log Field Description
client_IP_address IP address of client, such as
- - Two hyphens for compatibility with standard Web server log formats.
timestamp Time that client accessed the file in the format:
dd/Mmm/yyyy:hh:mm:ss TZ
where TZ is the time zone expressed as the number of hours relative to the Coordinated Universal Time (Greenwich, England) and is relative to the server. Server time is currently set to Mountain Time. For example:
[31/Oct/1996:13:44:32 -0600]
"GET filename File name (and path) requested by the client. Path is relative to BasePath in local file system. If the client requests a file that doesn't exist, UNKNOWN appears in place of a file name.
protocol/version" Application-layer protocol used to send the clip to the client. Possible values are:
In addition, a letter at the end of the string indicates which transport type was used:
(blank) UDP connection
T TCP connection
H HTTP connection
M Multicast
For example, PNAT means that the clip was sent using the PNA protocol over a TCP connection.

The version number indicates the edition of the protocol.
HTTP_status_code Return code using HTTP standard error codes. Usually returns 200 (which means ok).
bytes_sent Number of bytes transferred to the listener or viewer's RealPlayer.
[client_info] Describes the version and type of client being used. Client information appears in the following format,
[platform version client type dist_code language CPU]
Field Description
platform Operating system RealPlayer runs on-Win16, WinNT, Mac, and so on.
version Operating system version number.
client Version number of RealPlayer.
type Type of RealPlayer.
dist_code Distribution code of RealPlayer.
language Language setting in RealPlayer.
CPU Type of processor on which the client is running. If the processor does not have a hardware Floating Point Unit, the string "no-FPU" is appended to the end of the CPU field with no delimiter. For example:
RealAudio Player version 1.0 shows only two fields for [client_info]. They are platform and client.
client_id Unique ID generated during RealPlayer installation that enables you to track details for individual clients.
This information may not be available in your log and may read [UNKNOWN].

How It Works | Prices | Support | FAQ | Contact Us