Milestone Basis+ 6.5 - Manual (Page 124)

Milestone XProtect Basis+ 6.5; Administrator’s Manual
Event log files should be viewed using the Smart Client (see page 140) or the Viewer (see page
135):
• Smart Client: In the Browse tab’s Alerts section, select the required event, then click the
Get List button to see when the event in question was detected.
• Viewer: Select the Viewer’s Alarm Overview control panel, then click the Events button to
view the events log.
Image Server Service Log Files
These files log activity on the Image Server service. A log file is created for each day the Image
Server is used.
Image Server log files are by default placed in the folder containing the XProtect Basis+ software,
typically C:\Program Files\Milestone\Milestone Surveillance\.
Image Server log files are named according to the structure ISLog_YYYYMMDD.log, e.g.
ISLog_20070615.log .
Image Server Audit Log Files
These files log Remote Client (see page 142) and Smart Client (see page 140) user activity, if audit
logging is enabled in the Image Server Administrator (see page 109). A log file is created for each
day with remote user activity.
Image Server audit log files are by default placed in a subfolder named ISAuditLog under the folder
containing the XProtect Basis+ software, typically C:\Program Files\Milestone\Milestone
Surveillance\.
Image Server audit log files are named according to the structure is_auditYYYMMDD.log, e.g.
is_audit20070615.log.
Image Import Service Log Files
These files log activity regarding the Milestone Image Import service, which is used for fetching
pre-alarm images, and storing the fetched images in the database. 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.
Image Import Service log files are by default placed in the folder containing the XProtect Basis+
software, typically C:\Program Files\Milestone\Milestone Surveillance\.
Image Import Service log files are named according to the structure
ImageImportLog_YYYMMDD.log, e.g. ImageImportLog20070615.log.
Integrity Checks and Possible Error Messages
Log files are subjected to an integrity check once every 24 hours. The result of the integrity check
is automatically written to a file named according to the structure LogCheck_YYYYMMDD.log, e.g.
www.milestonesys.com Page 124 Logging