User manual

ADPRO
®
XOa Client Software User Manual
21796_05_preliminary 157
24.5 Logs
24.5.1 About Logs
Local legal requirements (variable and depending on state and region, please check with your local
authorities) may stipulate that a video system has to keep a logbook (e.g. the Law Sarkozy in France). The
logbook, or log for short, registers all user interventions and events.
The server offers different log types with different information, to make it easier to keep an overview and find
the data you need.
Note
A log is limited to 100 000 events per type (log, event, or command; see below) and has a time
period limit of 6 months. RMG automatically deletes any logged data older than 6 months. If you
need to keep logged data longer than that, you can save the log on a local hard drive or USB
stick.
The following log types are available:
Log
Log of users and what they viewed. You can filter the log to display one or more of
the following view types:
 Live video view: lists the users that started a live video stream.
 Live multicast view: lists the users that started a live multicast video stream.
 Still image view: lists the users that viewed still images = starting/stopping playback
of recorded video.
 Recorded video view: lists the users that watched or downloaded recorded video.
Event (CMS Tx)
Log of events that are configured for transmission to the CMS. You can filter the log
to display one or more of the following event types:
 Faults: alarms and errors, such as tamper alarms, locked recordings, etc.
 Fire: fire events.
 Other: other events that are not faults or fire events, such as system messages,
motion detection, live viewing, inputs and outputs, etc.
Event (E-mail Tx)
Log of events that are configured for transmission to email. You can filter the log
using the same event types as described for transmission to the CMS.
Event (ParTx 1)
Log of events that are configured for transmission to parallel destination 1. You can
filter the log using the same event types as described for transmission to the CMS.
Event (ParTx 2)
Log of events that are configured for transmission to parallel destination 2. You can
filter the log using the same event types as described for transmission to the CMS.
Command
Log of users and the commands that they executed, such as connecting to servers,
saving configurations, etc.
Note
The logs contain events that actually occurred, and that are configured for the selected
transmission. However, this does not imply that the destination has actually received the event
message. For example, if you set up LICENSE EXPIRED for email transmission, the event
appears in the log when a license expires. However, if you did not set up a mailing list for it,
then the message LICENSE EXPIRED does not reach any email destination.