Data displayed in the Alarm and Event Log Viewer

The data displayed in the Alarm and Event Log Viewer event list are organized into columns and represent alarm and event information. During design time, the columns can be added, removed, or re-ordered as appropriate to your application of the Alarm and Event Log Viewer. The following sections provide definitions of the data displayed:

Priority

The urgency of the event.

Low

Medium

High

Urgent

Event

Severity

The urgency of the event.

The value is in the range of 1 (lowest severity) to 1000 (highest severity) for alarms, and 0 for server-based events.

Alarm State

Applies to condition-related events only.

An icon may represent different alarm states. This is because the states Disabled, Suppressed, and Shelved take different orders of precedence.

Disabled takes precedence over Suppressed.

Suppressed takes precedence over Shelved.

See the following table for description of the alarm state icons:

This icon...	Represents this alarm state...
	In Alarm, Unacknowledged
	In Alarm, Acknowledged
	In Alarm, Unacknowledged, Suppressed In Alarm, Unacknowledged, Suppressed, Shelved
	In Alarm, Acknowledged, Suppressed In Alarm, Acknowledged, Suppressed, Shelved
	In Alarm, Unacknowledged, Shelved
	In Alarm, Acknowledged, Shelved
	Normal, Unacknowledged, Disabled Normal, Unacknowledged, Disabled, Suppressed Normal, Unacknowledged, Disabled, Shelved Normal, Unacknowledged, Disabled, Suppressed, Shelved Normal, Acknowledged, Disabled Normal, Acknowledged, Disabled, Suppressed Normal, Acknowledged, Disabled, Shelved Normal, Acknowledged, Disabled, Suppressed, Shelved
	Normal, Unacknowledged
	Normal, Acknowledged
	Normal, Unacknowledged, Suppressed Normal, Unacknowledged, Suppressed, Shelved
	Normal, Acknowledged, Suppressed Normal, Acknowledged, Suppressed, Shelved
	Normal, Unacknowledged, Shelved
	Normal, Acknowledged, Shelved
	Active, Faulted
	Normal, Faulted
	Normal, Suppressed
	Active
	Normal
	Active, Suppressed
	Normal, Disabled

Event Time

The time at which the event occurred.

For condition-related events, the time at which the alarm condition entered the alarm state.

For simple and tracking-related events, the time at which the event occurred. Note that simple events are not currently supported.

TIP:

The Event Time is logged Greenwich Mean Time (GMT) and converted to the local time zone of the computer where the Alarm and Event Log Viewer is running. For example, the Event Time displayed on computers in different time zones will differ by the number of hours between the time zones. The date and time format is controlled by the Region and Language settings in the

Windows

Control Panel on the computer where the Alarm and Event Log Viewer is running.

Other data field columns:

Column Name	Description
Area	The FactoryTalk Directory path to the area in which the event occurred, in the format: /Area1/SubArea1/... . For example: /Line1/MixingTank.
Server Name	The name of the server that generated the event. For example: Packaging Server.
Group	The name of the group associated with the alarm, in the format: Group1.SubGroup1
Event Source	A reference to the object which generated the event notification. For FactoryTalk Alarms and Events the event source is the name of the alarm. The object that generated the event notification. For example: If the event is caused by an alarm entering the Level alarm condition (a condition-related event), the event source would be the alarm name, such as Tank1Level. If the event is caused by an event the system is tracking, such as an operator changing a setpoint value, the event source would be the tag name, such as FIC101.
Condition Name	Applies to condition-related events only. A name that describes the alarm condition. Condition names vary by event category. For example, Level (available to Logix analog instruction alarms, Logix tag-based alarms, analog alarms by a Tag Alarm and Event Server, OPC UA alarms): LO, LOLO, HI, HIHI Discrete (available to Logix tag-based alarms, discrete alarms, and OPC UA alarms): TRIP, TRIP_L, S_TRIP Deviation (available to Logix tag-based alarms, deviation alarms served by a Tag Alarm and Event Server, and OPC UA alarms): DEV_LO, DEV_HI Event (available to server-based event conditions): EVENT, EVENT_L System : STATUS, SHORTCUT Configured (also known as Logix tag-based alarms): TRIP, HIHI, LOLO, HI, LO, ROC_POS, ROC_NEG, DEV_HI, DEV_LO, TRIP_L, HIHI_L, LOLO_L, HI_L, LO_L, ROC_POS_L, ROC_NEG_L, DEV_HI_L, DEV_LO_L Rate of Change (available to Logix analog instruction alarms, Logix tag-based alarms, and OPC UA alarms): ROC, ROC_POS, ROC_NEG OPC UA (specific to OP UA alarms): AC, DISCREPANCY, DISCRETE, S_TRIP, TRIP, IDIAG, SDIAG, CERTIFICATE, LIMIT, LIMIT_HIHI, LIMIT_HI, LIMIT_LO, LIMIT_LOLO, HIHI, HI, LOLO, LO, DEV_HIHI, DEV_HI, DEV_LOLO, DEV_LO, ROC_POS, ROC_NEG, UDT
Message	The text that describes the event.
User Name	Applies to condition-related events and tracking-related events only. For condition-related events, the User Name field is not used in this release and is always blank. For tracking-related events, the User Name is the name of the component or user that initiates the action resulting in an event. For example, an operator modifies a tag value.
Computer	Applies to condition-related events and tracking-related events only. For condition-related events, the Computer field is not used in this release and is always blank. For tracking-related events, the name of the computer from which a component or user initiates the action resulting in an event. For example, an operator acknowledges an alarm.
User Comment	Applies to condition-related events and tracking-related events only. For condition-related events, the User Comment field is not used in this release. For tracking-related events, a comment associated with the operation that resulted in the alarm changing state. For example, an operator may choose to enter a comment when acknowledging an alarm.
Current Value	Applies to condition-related events only. The value of the tag that is being monitored for alarms when the alarm condition changed state.
Limit Value Exceeded	Applies to condition-related events only, for alarms whose event category is Level or Deviation only. The value which, when the tag value exceeds it, triggers an alarm.
Tag 1 Value	Applies to condition-related events only. Value of the associated tag parameter 1.
Tag 2 Value	Applies to condition-related events only. Value of the associated tag parameter 2.
Tag 3 Value	Applies to condition-related events only. Value of the associated tag parameter 3.
Tag 4 Value	Applies to condition-related events only. Value of the associated tag parameter 4.
Alarm Class	Applies to condition-related events only. A classification string that is associated with an alarm when it is defined. The Alarm Class provides a user defined string that can be used for filtering and sorting alarms.
Event Type	There are three types of events: Condition-related. An event associated with a change in the state of an alarm. For example, an alarm condition becoming active, acknowledged, inactive (returning to normal) or disabled. Tracking-related. An event associated with monitoring or auditing changes to the system. For example, an event describing the modification of a tag value by an operator. Simple. Any event describing a simple occurrence in the system. For example, failure in accessing a computer or device. Simple events are not currently supported.
Event Category	The category, defined by the alarm server, to which the event belongs: For condition-related events. Level, Discrete, Deviation, Event, System, Configured, Rate of Change, and OPC UA For tracking-related events. Operator Action For simple events. Not supported
Condition Quality	Applies to condition-related events only. Indicates the quality of the tags or input on which the condition is based. See Extended Quality Values for detailed information.

Alarm and Event Log Viewer

Provide Feedback

Have questions or feedback about this documentation? Please submit your feedback here.