SUM_Alert - _act_state and _act_state_prior attributes

Discussions about product bugs & problems!
Note: This is no replacement for the Official ETM Support!
Search

Post Reply
4 posts • Page 1 of 1
AMRPatricio
Posts: 50
Joined: Mon Dec 12, 2016 3:43 pm

SUM_Alert - _act_state and _act_state_prior attributes

Post by AMRPatricio » Mon Dec 02, 2019 2:56 pm

Hi all,

Do the _act_state and _act_state_prior work in similar manner when used in a dpConnect?
1. I do have a Sum_Alert with a DP list of 100 DPs.

2. One dpConnect to the _act_state of the SUM_Alert :
(dpConnect("check", "W.:_alert_hdl.._act_state");

3. One dpConnect to the _act_state_prior of the SUM_Alert:
(dpConnect("check2", "W.:_alert_hdl.._act_state_prior")

“Check” function is executed each time the sum_alert state it changes (as I do expect). However “Check2” function is executed each time one of the 100 DPs is executed.
In other words, if I do change the 100DPs at same time, Check function is executed one time, check Check2 is executed 100times.
Is it normal?
As I am connected to a sum_alert, I do not understand the behavior of the Check2 function.

Best regards,
Antonio Patricio

User avatar
leoknipp
Posts: 2031
Joined: Tue Aug 24, 2010 5:28 pm

Re: SUM_Alert - _act_state and _act_state_prior attributes

Post by leoknipp » Thu Dec 05, 2019 8:42 am

Maybe the following explanation helps to understand the behvaiour,
A summary alert can have several states, similar to a single alert: no alert, came unacknowledged, came acknowledged, ....
If the state changes the work function for _act_state is called.

The priority of the summary alert is defined by the alerts which are referenced by the summary alert.
Even if the state of the summary alert does not change possibly the priority may change. Therefore you get an update for _act_state_prior every time.

Here is an example:
-- The summary alert is raised by a referenced single alarm with priority 40
The state is "came unacknowledged" with priority 40.
-- A single alert is set with a priority 60
The state is still "came unacknowledged" but now with priority 60.

Best Regards
Leopold Knipp
Senior Support Specialist

AMRPatricio
Posts: 50
Joined: Mon Dec 12, 2016 3:43 pm

Re: SUM_Alert - _act_state and _act_state_prior attributes

Post by AMRPatricio » Fri Dec 06, 2019 9:12 am

Hi Leopold,
I understood what you said., and that it was my conclusion. I decided then to create a sum alert for each priority. However the behavior it is the same. Is it normal?

Best regards,
Antonio Patricio

User avatar
leoknipp
Posts: 2031
Joined: Tue Aug 24, 2010 5:28 pm

Re: SUM_Alert - _act_state and _act_state_prior attributes

Post by leoknipp » Fri Dec 06, 2019 1:06 pm

Even if you define a summary alert filtered exactly for one priority you will have the same behavior for the a dpConnect to _act_state_prior.

Best Regards
Leopold Knipp
Senior Support Specialist

Post Reply
4 posts • Page 1 of 1