You will need to program your application servers to process the user event types and user attributes that your applications need.
The following table describes all the RTMON user attributes that the appliance sends to application servers. User attributes provide details about the user events that occur. Whether a specific application server receives all user attributes depends on how the NetCache administrator has configured RTMON on the appliance. The NetCache administrator specifies by logical application server group the RTMON user attributes that will be sent to servers in that group.
All RTMON user attributes are delivered in each user event.
User attribute
|
Description
|
|---|
CID
|
Client ID. For each unique client stream, NetCache generates a CID.
|
CIP
|
Client IP address
|
CONNECTED-TIME
|
Amount of time the client has been connected.
|
DELIVERY-BITRATE
|
Bit rate at which the stream is being delivered, in kilobytes per second.
|
DROPPED-PACKETS
|
Total number of client-side packets dropped.
|
DT
|
Time stamp of the event since the UNIX Epoch time (00:00:00 GMT, January 1, 1970), for example, "1003298424". DT is suitable for input to C or PERL "gmtime"and "localtime" routines.
|
DT-USEC
|
Microsecond portion of the event timestamp, that is, microseconds past DT.
|
ENCODING-BITRATE
|
Bit rate at which the stream was encoded, in kilobytes per second.
|
GUID
|
Globally Unique ID string that a media player might send to the appliance to identify itself. GUIDs follow a specific format, for example, "503379d0-2346-11d3-b63f-00a0c9eeea28."
Not all streaming protocols include GUIDs, and GUIDs for different protocols might vary in length. The GUID should be treated as an opaque string that can be used to track a particular client by protocol. Currently, of the protocols that the appliance supports, QuickTime does not include GUIDs. GUIDs from RealPlayer that consist of all zeroes indicate that the user has disabled the sending of GUID information in the player preferences.
|
HIT-BYTES
|
Number of bytes sent to the client that were served from the cache (a cache hit).
|
LIMIT-BANDWIDTH
|
Bit rate that the client requested but was refused because Admission Control is in effect on the appliance for that client and dedicated bandwidth was unavailable. Admission Controls ensure that streaming requests at specific bandwidths are accepted only when it is possible to deliver a stream with predictable quality.
|
MISS-BYTES
|
Number of bytes that the appliance sent to the client from the origin server (a cache miss).
|
MTYPE
|
The player type:
Q = QuickTime
R = RealPlayer
W = Windows Media Player
|
NIP
|
Appliance IP address.
|
QS
|
The query string portion of the URL (everything after the `?' in the URL).
|
PLAY-TIME
|
The amount of time the client has been playing the stream.
|
PROXY-USERNAME
|
User name supplied by the client when authenticating to the appliance.
|
SESSION-ID
|
A session ID is sent by the RADIUS server if the RADIUS IP authentication feature is in use. The application server can use the SESSION-ID to share information (or state) with the RADIUS server.
|
SIP
|
Origin server IP address.
|
STREAM
|
The name of the media file in the URL, for example, "file.wmv".
|
TOTAL-BYTES
|
Total number of bytes delivered to the client.
|
TRANSPORTS
|
Shows the following information about connections that exist between the appliance and the client and the appliance and the server:
- End points of the connection
<type>client|server|cache</type>
- IP addresses and ports
<ip>i.b.c.d</ip> <port>1234</port>
- The protocol used for the connection, either TCP or UDP
<protocol>tcp|udp</protocol>
- The type of connection, which can be
- control ("control")
- audio stream ("audio")
- video stream ("video")
- retransmits and acknowledgements ("feedback")
The syntax is:
<media>
<type>audio></type>
<type>feedback</type>
...
</media>
|
URL
|
The URL that the client sent, for example, "mms://server.corpA.com:1755/movies/file.wmv".
|
