Guide Event Log – how to archive the log files
One of the key features of Guide is the ability to store the fire system activity on the Guide computer hard drive. Against each event it is possible to add comments advising the reason for the event. This can be useful for false alarm analysis, as required under the Limitation of False Alarms requirements of BS5839-1.
Supplied with Guide is a powerful event log viewing and filtering application, which can be launched within the Guide program or can be run as a separate application (to allow log files to be copied and interrogated remotely from the site Guide computer).
The log can be filtered by dates, event types, user logins, loops and addresses.
The results of the event log filtering can be viewed in either HTLM or list format and can be saved / exported in comma separated values (csv) file format for analysis using an external program, such as Microsoft Excel.
The Guide event log is actually made up from a number of individual “lst” files which are generated regularly at a pre-configured interval, set under the Guide administrator settings.
These files are stored in a defined event output folder in a path configured under the Guide Administrator settings.
Using a number of small files for the event log allows the older part of the log to be regularly archived, without losing the more recent event history.
For optimum performance, we strongly recommend the older event log files are regularly archived. This will prevent the event log viewer application from taking excessive time and processing power to filter the event history.
The recommended procedure for archiving the event log may be downloaded using the link below
Event log archive procedure
For further advice on any of the items in this bulletin, please contact the Technical Support team on +44 (0)1322 222121 or by e-mail using firstname.lastname@example.org