DX Infrastructure Manager

Expand all | Collapse all

after changing alarm treshold value from X to Y (for cdm), the alarm is still generated for the old X treshold

  • 1.  after changing alarm treshold value from X to Y (for cdm), the alarm is still generated for the old X treshold

    Broadcom Employee
    Posted 8 days ago
    Edited by Stefan Pivoda 8 days ago
    Hi,

    when I change the alarm treshold value for cdm for value (20) to value (10) via OC alarm policy, the alarm is still generated for the old treshold value (20) and not for the new one (10). even the cdm probe is restarted.
    have you ran into this issue/bug as well?
    so how can i change the treshold value without deleting the whole alarm policy?
    UIM 20.3.1.

    thank you,
    stefan


  • 2.  RE: after changing alarm treshold value from X to Y (for cdm), the alarm is still generated for the old X treshold

    Posted 7 days ago
    If you use enhanced mcs profiles your settings are written into the spooler of the robots
    see file: C:\uim\plugins\plugin_metric\pugin_metric.cfg


  • 3.  RE: after changing alarm treshold value from X to Y (for cdm), the alarm is still generated for the old X treshold

    Posted 7 days ago
    Hi Luc (^-^)>, Hi everyones,

    Currently the topic is Monitoring Policy on the Operating Console side. Therefore, it will not concern the Spooler probe, which is affected by the Enhanced MCS Template. Two elements attached, but not in this case XD

    Explanation: When you create a Monitoring Policy in Operator Console, alarms are centrally managed by a rather complex set of rules and enrichment (Trellis, EMS, Alarm Enrichment ...).

    It appears that these elements, for performance reasons, are based on "caches" and do not perform real-time queries on the database for each alarms. You will have that type of "delays" quite often. During our test phases, we sometimes restart the central server robot to "force" it to renew the whole thing with the new settings instead of waiting ...

    It would be interesting if Broadcom could provide documentation on how to set the renewal intervals of these "caches" (we only have to change the one-hour cycle of the alarm_enrochment probe to a 15-minute cycle), but this does not cover all cases. However, keep an eye on the load that this would imply for your database. If you do not have any custom rules in your alarm_enrichment probe, the impact of the setting will not be significant.

    Best regards,
    Jonathan

    ------------------------------
    Lead Monitoring Solution Architect
    AXA Investment Managers Paris
    ------------------------------



  • 4.  RE: after changing alarm treshold value from X to Y (for cdm), the alarm is still generated for the old X treshold

    Broadcom Employee
    Posted 7 days ago
    Hi stefan,

    Have a run across this issue and found this correction process fixes most times.

    https://knowledge.broadcom.com/external/article?articleId=198508