Legato
Legato

GoFiler Legato Script Reference

 

Legato v 1.6c

Application v 6.1a

  

 

Chapter SixteenApplication (continued)

16.5 Event Log

16.5.1 Introduction

[The Event Log Object allows events, errors, transactions and other information to be written to a flat text file. Depending on the platform, the application itself has a default event log usually located in the application data section of the user’s profile.]

[Events are written as text lines with an optional timestamp (which is enabled by default). The log can be shared and also has options for roll over and size limiting. Event Log Objects do not support structured options such as message types, target files or locations.]

[The Event Log is different from the general Log Object and Info View logs in that while it could be displayed to the user, it is designed to be a facility for recording information in the background. It can be used to perform forensic analysis of processes and operations for both software and user behavior purposes.

[Finally, the Event Log Object is designed to be fast employing overlapping I/O. However, it is not as robust as spooling to a File Object using the FO_FORCE_SPOOL option.

16.5.2 Operation

[An object is created or opened using the EventLogOpen function and returns an Event Log Handle. That handle is the used to write information using the EventLogWrite or AddMessage functions.]

[To view a log, it is recommended that the file be opened in an application such as Windows Notepad that does not lock file sharing. If the log file is opened in the application editor, it will be locked for read share at a minimum. This primarily applies to logs that are actively being used, as such while an Event Log Object is open, the file will be locked.]

16.5.3 Functions

Page revised 2025-06-16