Cisco Cisco StadiumVision Mobile Streamer Maintenance Manual
© 2011 Cisco Systems, Inc. All rights reserved.
Page 13 of 14
Cisco Services Monitor
This service is not currently implemented.
Log Service
As events happen within SV Director, they are logged in log files. A normal
event may be logged at a low log level such as „INFO‟. A more critical event
that requires intervention to fix will be logged at a higher log level such as
„ERROR‟ or „FATAL‟. Any messages in the log files logged at ERROR or
FATAL are also shown in the Log Service status window.
event may be logged at a low log level such as „INFO‟. A more critical event
that requires intervention to fix will be logged at a higher log level such as
„ERROR‟ or „FATAL‟. Any messages in the log files logged at ERROR or
FATAL are also shown in the Log Service status window.
The Log Services monitor checks the StadiumVision log files for severe
messages (log level ERROR or FATAL). It looks back for a period of time
specified as the timeWindowInHours, which is set at 8. Errors older than that
period are not shown here. The messages are reported as a histogram,with
the top 10 errors shown.
messages (log level ERROR or FATAL). It looks back for a period of time
specified as the timeWindowInHours, which is set at 8. Errors older than that
period are not shown here. The messages are reported as a histogram,with
the top 10 errors shown.
Log4j configuration can specify the timeWindowInHours and the
topNToDisplay values.
topNToDisplay values.
The Log Service Status window shows a report with the following information:
Timestamp: When the first error in the rolling 8 hour window occurred.
Level: The log level at which the message was logged.