Format of the event log

The location and format of the event log depends on whether History Format is set to Proprietary or Database. This section describes both.

When the History Format is Proprietary (default), the event log is saved as a series of text files in your project’s Alarm folder, with one file per calendar day. The name of each file is EVyymmdd.EVT, where:
  • yy is the last two digits of the year in which the event log file was generated;
  • mm is the month in which the event log file was generated; and
  • dd is the day of the month on which the event log file was generated.

Therefore, the event log file for 07 May 2003 is located at […]DocumentsInduSoft Web Studio v7.1 ProjectsprojectnameAlarmEV030507.EVT.

Tip: To change where your project saves these files, use the SetAppAlarmPath function.
Within a specific day’s *.EVT file, each event is saved as a new line, using the pipe character ( | ) to delimit the fields, as illustrated below: 
  P1|P2|P3|P4|P5|P6|P7|P8|P9|P10|P11|P12|P13  P1|P2|P3|P4|P5|P6|P7|P8|P9|P10|P11|P12|P13  .  .  P1|P2|P3|P4|P5|P6|P7|P8|P9|P10|P11|P12|P13

When the History Format is Database, the event log is saved as a table in whichever database you configured for Event Database. For more information, see Saving your event log to an external database.

The fields/columns of the event log are described below:
Proprietary Database Description
Field Number Column Name Data Type
P1 Version Integer This field is created only when the History Format is Proprietary. Current version: 002
P2 Event_Type Integer 1 Security System
2 Display
3 Recipe
4 Report
5 Custom Message
6 System Warning
7 Log Tags
P3 Event_Time TimeStamp

Time stamp indicating when the event occurred.

When the History Format is Proprietary, the project saves the event time in the following format: MM/DD/YYYY HH:MM:SS.MSS. When the History Format is Database, the project saves the event time in the default timestamp format of the database.

P4 Event_Info String Tag name.
P5 Value Real Tag value when the event occurred.
P6 Source String Name of the task that generated the event.
P7 User String User logged on when the event occurred.
P8 User_Full String Full name of the user logged on when the event occurred.
P9 Message String Event message.
P10 Station String Name of the station (computer) where the event occurred.
P11 Comment String Comment (optional) typed by the operator when the event occurred. This field only exists for Version >= 2.
P12 Previous_Value Real Tag value that occurred before the event. This field only exists for Version >= 2.
— Deleted Boolean This field is created only when the History Format is Database.
  • 0 (FALSE): Event message was not deleted.
  • 1 (TRUE): Event message was deleted.
P13 Bias Integer Difference (in minutes) between Event_Time and the GMT time. This field only exists for Version >= 2.
— Last_Update TimeStamp Time stamp indicating when the register was created/modified. This field is used to synchronize the databases when using the Secondary Database in addition to the Primary Database. This field is created only when the History Format is Database.
Tip: You can customize the names of the columns in the database table by manually editing the project file (e.g., […]DocumentsInduSoft Web Studio v7.1 Projectsprojectnameprojectname.APP) as follows: 
  [EventLogger]  DefaultName=NewName
For example: 
  [EventLogger]  Event_Info=Information  Message=Event_Message
InduSoft Web Studio -Technical Reference

Format of the event log