What do (Persisting) and (Persisting-NoData) mean in a MainView Alarm Manager message?

Version 2
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    MainView Infrastructure


    APPLIES TO:

    MainView Alarm Manager



    QUESTION:

    What do (Persisting) and (Persisting-NoData) mean in a MainView Alarm Manager message?


    ANSWER:

    In MainView Alarm Manager, the persistence option is used to specify how many times the same condition is true during evaluation before an alarm can be generated.

    The Evaluation is done based on the Evaluate Frequency that the user specified in an alarm definition. For example::

    Schedule
    Evaluate every 60    (multiples of 5) seconds for the following

    If you have specified 60 seconds, then the evaluation will be done 5 times in 5 minutes (5 samples)

    With a persistence option of:

    Total Samples : 5 ; warning samples:3 major samples:5
    Warning >90%
    Major > 95%

    This means that if a warning condition is true for more than 3 times in the last 5 evaluations, then a warning alarm will be generated.

    In this example, the Alarm log will show that the alarm was generated at 5 minute intervals (Evaluate Frequency specified is 60 seconds, with 5 evaluations done during this 5 minutes interval):

    19:21:55 WAR AW-A       STA BMFSYSCPUS00      DQBA DB2Target: DQBA (TotalCPU % > 90)
    19:27:02 WAR AAW-A     CON BMSYSCPUS00      DQBA DB2Target: DQBA (TotalCPU % > 90) (Persisting)
    19:32:17 WAR AAAW-A   CON BMSYSCPUS00      DQBA DB2Target: DQBA (TotalCPU % > 90) (Persisting)
    19:37:16 WAR -AAAW-A  CON BMSYSCPUS00      DQBA DB2Target: DQBA (TotalCPU % > 90) (Persisting)
    19:42:14 WAR --AAAW-A CON BMSYSCPUS00      DQBA DB2Target: DQBA (TotalCPU % > 90) (Persisting-NoData)
    19:47:12 WAR ---AAAW-  END BMSYSCPUE00      DQBA DB2Target: DQBA End of Alarm Condition

    The (Persisting) in the alarm text, indicates the severity of the alarm is the same as the previous reported alarm.

    (Persisting-NoData) means that the current evaluation for the same condition is not true. However, when the current evaluation is combined with the results of previous (in this case 4) evaluations, the alarm definition matches the persistence definition (3 samples out of 5 samples) at the same severity as the previously reported alarm.


    Article Number:

    000117913


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles