Skip to main content

Loggers - Alarming

Aaron Palas
  • Updated

This article covers loggers related to Alarming that were introduced in Ignition version 7.9.X.

Loggers in this article:

alarm.Execution

  • Monitors alarm event transitions due to setpoint triggers. Replaced 7.8’s Alarming.Execution.
    • DEBUG log capturing the event of an alarm triggered to an active state:
      (prov:default:/tag:Testing/Alarming/Boolean Alarm Tag:/alm:Test Boolean Alarm High : 390912338) Registered live event '6d5ef5f0-c3d9-436e-bc08-c246cde4836f', state: Active, Unacknowledged. Outstanding events: 3
    • TRACE log capturing two events for a single tag alarm. Tag alarm was first set to cleared, unacknowledged due to a value change outside the alarm setpoint. Then, the same tag alarm's value was changed back to within the alarm setpoint:

      (prov:default:/tag:Testing/Alarming/Boolean Alarm Tag:/alm:Test Boolean Alarm High : 390912338) Begin transition event to 'Clear'

       

      (prov:default:/tag:Testing/Alarming/Boolean Alarm Tag:/alm:Test Boolean Alarm High) Continuing transition to state 'Clear', generating event data.

       

      ...

       

      (prov:default:/tag:Testing/Alarming/Boolean Alarm Tag:/alm:Test Boolean Alarm High : 390912338) Begin transition event to 'Active'

       

      (prov:default:/tag:Testing/Alarming/Boolean Alarm Tag:/alm:Test Boolean Alarm High) Continuing transition to state 'Active', generating event data.
    • TRACE log returning periodic checks for each configured alarm. Will report the current state of the qualified value being monitored by the alarm setpoint every 1 second. 
      (prov:default:/tag:Testing/Alarming/Boolean Alarm Tag:/alm:Test Boolean Alarm Low) Alarm will not be evaluated - enabled is set to false, the bound value for 'enabled' has bad quality, or the value is invalid for the alarm condition. Value: [true, Good, Fri Apr 29 10:00:53 PDT 2022]

alarm.Manager.StateManager

  • Provides full detail of all tag alarms and their events when they have been created, triggered, acknowledged, changed, or removed. Replaced 7.8’s Manager.StateManager.
    • DEBUG log for created/edited alarm configuration on a tag:
      Registering alarm: prov:default:/tag:Boolean Alarm Tag:/alm:Test Boolean Alarm High
      alarm-source=prov:default:/tag:Testing/Alarming/Boolean Alarm Tag:/alm:Test Boolean Alarm High
      Updating alarm 'prov:default:/tag:Boolean Alarm Tag:/alm:Test Boolean Alarm High' with initial state from 'existing tag'.
      Initial events: [f296329a-4eda-4d3a-8d5a-97006310c868/Active, Unacknowledged]
      alarm-source=prov:default:/tag:Testing/Alarming/Boolean Alarm Tag:/alm:Test Boolean Alarm High
    • DEBUG log for state changes in the alarm event. In this case, the state change came from triggering the alarm’s setpoint:
      Updating alarm event. From update: true, event:
      {Source: 'prov:default:/tag:Boolean Alarm Tag:/alm:Test Boolean Alarm High', Display Path: '',
      UUID: 'f296329a-4eda-4d3a-8d5a-97006310c868', Current State: 'Active, Unacknowledged', Priority: 'Low',
      Active Data: {setpointA=1.0, eventValue=true, name=Test Boolean Alarm High, eventTime=Tue Sep 07 07:27:17 PDT 2021},
      Clear Data: null, Ack Data: null, Runtime Data: {isInitialEvent=true}}
      alarm-source=default/Testing/Alarming/Boolean Alarm Tag/Test Boolean Alarm High, alarm-name=Test Boolean Alarm High
    • TRACE log for alarm events that are removed from the system. Typically seen when the Live Event Limit has been exceeded. Here on 7.9, we are provided the alarm-source:
      Remove event '69e8ef2d-7a2d-4e41-87ff-a3c94d5975b6' alarm-source=default/Testing/Alarming/Boolean Alarm Tag/Test Boolean Alarm High,
      alarm-name=Test Boolean Alarm High

Back to top

alarm.JournalManager

  • A series of loggers that monitor the process of inserting alarm events into an existing alarm journal profile. Replaced 7.8’s Alarming.JournalManager.
  • alarm.JournalManager will notify the gateway when an alarm event is being stored to an existing journal.
    • TRACE log showing a notification from the gateway when an alarm event is being stored to an existing journal:
      Will store event '3f6bef64-7e70-4e39-889e-db32ae3703de/Active' to the configured alarm journals.
      alarm-source=default/Testing/Alarming/Boolean Alarm Tag/Test Boolean Alarm High, alarm-name=Test Boolean Alarm High

Back to top

alarm.JournalManager.DatabaseJournal.AlarmJournalSFData

  • Monitors the process of inserting alarm events into an existing alarm journal profile’s database/store and forward. Replaced 7.8’s Alarming.JournalManager[Journal[{AlarmJournalProfileName}]].
    • TRACE log showing a successful, default insert into the alarm journal. Parameters unspecified on a tag’s alarm properties will be mentioned:
      Will store event '3f6bef64-7e70-4e39-889e-db32ae3703de/Active' to the configured alarm journals.

      Sending log event for UUID '3f6bef64-7e70-4e39-889e-db32ae3703de' to store and forward system.

      Will not store event data for property 'setpointA': either the property is not the correct type,
      or the event type is not configured for storage. [setpointA]

      Will not store event data for property 'eventValue': either the property is not the correct type,
      or the event type is not configured for storage. [eventValue]

      Will not store event data for property 'activePipeline': either the property is not the correct type,
      or the event type is not configured for storage. [activePipeline]

      Will not store event data for property 'name': either the property is not the correct type,
      or the event type is not configured for storage. [name]

      Will not store event data for property 'eventTime': either the property is not the correct type,
      or the event type is not configured for storage. [eventTime]
      Stored event to alarm journal (prov:default:/tag:Boolean Alarm Tag:/alm:Test Boolean Alarm Low, ,
      3f6bef64-7e70-4e39-889e-db32ae3703de, 0, 0, [{eventValue=false, name=Test Boolean Alarm Low, eventTime=Tue Sep 07 07:55:05 PDT 2021}])

Back to top

alarm.Notification.PipelineManager

  • Monitors alarm pipelines that have been activated from either existing alarm tags or pipeline tests. Replaced 7.8’s Notification.PipelineManager.
    • DEBUG log showing the an alarm event calling an existing alarm pipeline 'Email Pipeline':
      Sending alarm event '65c938f1-e15f-457d-aa51-df1f1a7a3e33' to pipeline 'Email Pipeline'
      (Source: prov:default:/tag:Boolean Alarm Tag:/alm:Test Boolean Alarm High)
      alarm-source=default/Testing/Alarming/Boolean Alarm Tag/Test Boolean Alarm High, alarm-pipeline=Email Pipeline,
      alarm-name=Test Boolean Alarm High

      Processing alarm event 'prov:default:/tag:Boolean Alarm Tag:/alm:Test
      Boolean Alarm High:/almevt:65c938f1-e15f-457d-aa51-df1f1a7a3e33' against pipeline 'Email Pipeline'
      alarm-source=default/Testing/Alarming/Boolean Alarm Tag/Test Boolean Alarm High, alarm-pipeline=Email Pipeline,
      alarm-name=Test Boolean Alarm High
    • DEBUG log showing a response to a pipeline test from the Ignition config page:
      Processing alarm event 'sys:configpage:/alm:**TEST:/almevt:4dae953c-142a-4f74-bd49-137a99ebc032' against pipeline 'Email Pipeline'

Back to top

alarm.Notification.EmailNotificationProfile

  • Monitors the status of sending an alarm event to the defined SMTP profile or credentials under the Ignition config. Provides information of the email being sent and the smtp server being used. Replaced 7.8 Notification.EmailNotificationProfile[{AlarmNotificationProfile}].
    • TRACE log of pipeline monitoring the email being prepared for be sent to a defined smtp profile:
      Using SMTP profile, rechecking profile info. alarm-pipeline=Email Pipeline, alarm-notification-profile=Email,
      alarm-source=default/Testing/Alarming/Boolean Alarm Tag/Test Boolean Alarm High, alarm-name=Test Boolean Alarm High

      [hostname=<null>,port=25] Creating email session with SMTP profile. alarm-pipeline=Email Pipeline,
      alarm-notification-profile=Email, alarm-source=default/Testing/Alarming/Boolean Alarm Tag/Test Boolean Alarm High,
      alarm-name=Test Boolean Alarm High

      [hostname=<null>,port=25] Setting mimeType to plain text alarm-pipeline=Email Pipeline,
      alarm-notification-profile=Email, alarm-source=default/Testing/Alarming/Boolean Alarm Tag/Test Boolean Alarm High,
      alarm-name=Test Boolean Alarm High
    • DEBUG log that also appears during an attempt to activate the email notification pipeline. Provides details of the smtp server defined in the Ignition config. The defined Subject and Message of the email from the alarm pipeline is also being shown:
      [hostname=<null>,port=25] Email settings: hostname = smtp.gmail.com, port = 465, timeout = 10000, useSsl = true, useStartTls = false,
      userName = aaron.palas@gmail.com, password exists = true, authRequired = true alarm-pipeline=Email Pipeline,
      alarm-notification-profile=Email, alarm-source=default/Testing/Alarming/Boolean Alarm Tag/Test Boolean Alarm High,
      alarm-name=Test Boolean Alarm High

      [hostname=<null>,port=25] Sending email to user '{schedule=Always, firstname=Aaron, notes=null, language=null, user.pin=,
      internal-db-id=3, username=apalas, lastname=Palas}'.

      Subject: Ignition Alarm Notification

      Message: At 09:46:46, alarm "Test Boolean Alarm High" at "" transitioned to Active. alarm-pipeline=Email Pipeline,
      alarm-notification-profile=Email, alarm-source=default/Testing/Alarming/Boolean Alarm Tag/Test Boolean Alarm High,
      alarm-name=Test Boolean Alarm High

Back to top

Was this article helpful?
0 out of 0 found this helpful
Return to top

Related articles

Comments

0 comments

Article is closed for comments.

This article has 0 comments.