Milestone XProtect Express 2014 - Manual (Page 131)

Milestone XProtect ® Express 2014 Administrator's Manual
www.milestonesys.com 131 Advanced configuration
Name Description
Image Server service log files
Shows Image Server service activity. A new log file is created for
each day the service is used.
You cannot disable this type of logging. Image Server service log
files are named according to the structure ISLog_YYYYMMDD.log,
for example ISLog_20091231.log.
Image Import service log files
Shows Image Import service activity, when this service is used for
fetching pre-alarm images, and storing the fetched images in
camera databases.
Pre-alarm images is a feature available for selected cameras only.
It enables sending of images from immediately before an event took
place from the camera to the surveillance system via e-mail. A new
log file is created for each day the service is used.
You cannot disable this type of logging. Image Import service log
files are named according to the structure
ImageImportLog_YYYMMDD.log, for example
ImageImportLog20091231.log.
Event log files
Shows registered events' activity. A new log file is created for each
day on which events occur.
You cannot disable this type of logging. Event log files should be
viewed using XProtect Smart Client (use the Playback tab's Alerts
section).
Audit log files
Shows XProtect Smart Client user activity (if audit logging is
enabled).
A new log file is created for each day with audit logging enabled
and client user activity. Audit log files are named according to the
structure is_auditYYYMMDD.log, for example
is_audit20091231.log. The _is prefix is due to the fact that the audit
log files are generated by the Image Server service.
Log locations
All log files are by default placed in the appropriate All Users folder for the operating system you are
using. By default, they are stored there for seven days. Note that you can change log file locations as
well as the number of days to store the logs when you configure logging.
Log structures
Most log files generated by your system use a shared structure complying with the W3C Extended Log
File Format. Each log file consists of a header and a number of log lines:

The header outlines the information contained in the log lines.

The log lines consist of two main parts: the log information itself as well as an encrypted part.
The encrypted part makes it possible, through decryption and comparison, to assert that a log
file has not been tampered with.