AlarmCntBySeverity Attribute doesn't store values for the highest level area in model view, even when theres alarms in the galaxy

Hello,

Basically I'm trying to configure the SA_Alarm_Runtime Banner to show all the alarms in the galaxy at any time. The alarm client bit works and shows the details of the alarms but with the counters at the top, they don't show any values when the highest level of area (which contains all other areas & objects) and when I look in the object viewer, the area that contains everything has no values in the AlarmCntBySeverity attribute, where as the area which all the objects are deployed into does show values in the AlarmCntBySeverity. Not sure if this is a bug or if this is something that can't be done. I just wonder if theres some work around someone knows, to be able to show the count of all the types of alarms in a galaxy. 

Parents
  • Hi Melinda, the 'top most' area in your model view should reflect all available alarms in you galaxy.

    Could you please verify the structure in your galaxy, and perhaps, if you changed it recently, perform a redeploy of your platform and objects?

    In my example here, you can se that 'Enterprise' is my top level.

    And the structure should be reflected in object viewer, and in the AlarmCntBySeverity.

    Based on your own structure, does your second top most areas, list the top level area as value in .Area and .Container?

    As you can se in my example, Site_A, Site_B and GalaxySystem have a value of Enterprise in Area and Container, and Enterprise, does not have a value since it is the top most level.

    Line_1 reflect the structure by listing Site_A as value.

    Also please verify so that you have the correct setting on you area object, Default value for Aggregate Alarms is Checked

    If this is Not checked, then AlarmCntBySeverity will only contain zeros on that area.

    Would be interesting to check this before troubleshooting further.

  • Hiya yes it was due to an area containing the area of objects which wasn't deployed, once i deployed it, it has fixed the issue

Reply Children