Viewing The Trace Log (Web Interface); Viewing The Stream Log (Web Interface); Viewing The Fmsconnector Log (Web Interface); Viewing The Fmsaccess Log (Web Interface) - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
Example:
[Fri Jun 26 19:37:09.754 2009] ADD "/http-cl18:ed239a85/100k-files/117/29" SAS dc_3 32768 [Fri Jun
26 19:38:14 2009]
Fields (display according to event type):
[Date]
Content_Length_In_Bytes [Expiry_time_for_this_URI]

Viewing the Trace Log (Web Interface)

Media Flow Controller includes a delivery trace facility to help diagnose the handling of a
particular HTTP request; trace results are written to the Trace Log; in the CLI this is the
tracelog. See
Continuous log, updated every 10 seconds.
Current log, that day's activity.
Download log—Opens a File Open dialog so you can save the trace log locally.
Archived (does not display if not applicable) log (1 - n), past logs.

Viewing the Stream Log (Web Interface)

This Media Flow Controller service log records RTSP streaming transactions; in the CLI this is
the streamlog. Use this tab to access the Media Flow Controller Service log. See
(streamlog)" on page 220
Continuous log, updated every 10 seconds.
Current log, that day's activity.
Download log—Opens a File Open dialog so you can save the trace log locally.
Archived (does not display if not applicable) log (1 - n), past logs.

Viewing the FMSConnector Log (Web Interface)

This Media Flow Controller service log records RTSP transaction details including what URIs
are accessed and how many bytes are returned by the FUSE module. In the CLI this is the
fuselog. Use this tab to access the Media Flow Controller Service log. See
Log / fuselog" on page 219
Continuous log, updated every 10 seconds.
Current log, that day's activity.
Download log—Opens a File Open dialog so you can save the trace log locally.
Archived (does not display if not applicable) log (1 - n), past logs.

Viewing the FMSAccess Log (Web Interface)

This Media Flow Controller service log lists all FMS server command executions. Streaming
fmsaccesslog events include play, pause, seek, and stop events; session fmsaccesslog
events include connect, disconnect, and connect-pending events, by default. This log is
generated by the FMS server (must be installed, see
Controller (CLI)" on page
Event_Type "<URI_name>"
"Trace Log (tracelog)" on page 223
for details.
for details.
97). In the CLI this is the fmsaccesslog. Use this tab to access the
Media Flow Controller Configuration Tasks (Web Interface)
Cache_Tier_Name
for details including trace points.
"Installing and Using FMS in Media Flow
Cache_Name
"Stream Log
"FMSConnector
Viewing Logs Overview 191