Types of events

Application Server creates several types of runtime event messages, which are saved as historical data.

• System events

  Event messages are logged when a Platform, Engine, Area, DI Network or DI Device start or stop. Any system action that affects a large number of objects is logged as an event.

  A System event message contains the following information:

  • Event type, which is System.

  • Tagname, which is the name of the object generating the event.

  • Tag description, which is a short description of the object generating the event.

  • Area, which is the name of the area that contains the object generating the event.

  • Event description, which describes the system action and can be either Started or Stopped.

  • Timestamp, which is the current system time.

• Security-audit (operator change) events

  Event messages are logged to the Alarms and Events subsystem when an operator logs on to or logs off from an application, and when a logon attempt fails (for example, due to an incorrect password). Also, security-audit events are logged when an operator changes actions by means of User sets.

  A Security-audit event message contains the following information:

  • Event type, which is operator change.

  • Timestamp, which is the date and time when the operator change event occurred. The timestamp of the event is the current AppEngine scan time.

  • Tagname, which is the name of object generating the event.

  • Prim.attr, which is the reference string of the attribute being changed.

  • Tag description, which is a short description of the object. For Secured and Verified writes, this will contain the following:

    • Type of write (Secured or Verified)

    • Comment from the user, if any

    • Reason description, if any

  • FieldAttribute description, if the attribute is a FieldAttribute and has a description; otherwise, this is the Object description.

  • Area, which is the name of the area that contains the object generating the event.

  • UserEngine, which is the name of the view engine or other user engine requesting the operator change.

  • Operator1, which is the full name of the primary operator requesting a change. The full name is an attribute of the UserProfile.

  • Operator2, which is the full name of the secondary operator validating the change, if any.

  • Old value, which is the previous value of an attribute.

  • New Value, which is the new value of an attribute.

• Application (or process) related events

  Application event messages are generated by application objects in response to process actions. For example, application event messages are created when a process pump starts or stops.

  An Application event contains the following information:

  • Event type, which is data change.

  • Timestamp, which is the date and time when the application event occurred. The timestamp assigned to the event is the timestamp of the attribute associated with the event, if available. Otherwise, the event timestamp is the current AppEngine scan time.

  • Tagname, which is the name of the object generating the event.

  • Prim.attr, which is the reference string of the attribute being changed.

  • Tag description, which is a short description of the object.

  • Area, which is the name of the area that contains the object generating the event.

  • Old value, which is the previous value of an attribute.

  • New Value, which is the new value of an attribute.