DX Unified Infrastructure Management

  • Private Community

  • 1.  Is there a limit for Pre-Processing rules created using NAS Auto operator

    Posted Mar 29, 2018 07:42 AM

    I have created AO rules in NAS to suppress alarms when the end devices go in Maintenance mode. To be precise, I have created 36 similar pre-processing rules to exclude any alarm from being generated. Each pre-processing rule is supposed to stop 100s of Servers from creating alarms. The problem I face is 'few' of these rules (random, not the same) do not work and when this happens, alarms get generated which in turn creates tickets in Service Desk tool. This  gets very frustrating as these unwanted alarms creates 100s of unwanted tickets.

     

    I can assure you there is no issue in the AO rules I have created and as mentioned above, the issue happens randomly on any created rule. Is there a limit for Pre-processing rule or something? The issue is very critical for us, any input is greatly appreciated.

     

    For your information, my nas release is 8.42.



  • 2.  Re: Is there a limit for Pre-Processing rules created using NAS Auto operator

    Posted Mar 29, 2018 09:22 AM

    I'm not aware of a limit in terms of number, but yes in terms of load there is a break point at which alarm_enrichment can't keep up. One way to deal with that is to offload some rules to second tier nas instances, that is when applicable. Another thing that can help is to set to rule for Action Mode, something other than upon arrival. 

     

    It is recommended to get off uim 8.4 to something still supported. At least update to the current nas, and the robot and hub updates available in the archive.  



  • 3.  Re: Is there a limit for Pre-Processing rules created using NAS Auto operator

    Posted Mar 29, 2018 03:51 PM

    You interleave "preprocessing" and "AO Profile" as if the words are interchangeable. They are not.

     

    You ask about load and in my experience the number of AO profiles should have little impact on performance. After all the total impact of an additional profile is evaluating one more profile for a match. If you had 99 profiles and added one more it would only increase the cost of finding a match by a percent.

     

    So, what's important when adding profiles is that you make sure the match is easy to evaluate and that a profile doesn't match too much.

     

    Obviously if you are in a situation where you have a profile that matches everything and then add a second profile that also matches everything, that's a significantly different impact than just having a lot of individual profiles that only match a unique non-overlapping set of messages.

     

    You mention some unpredictableness of the results and that can be the result of not paying attention to the actual impact of overdue age and on arrival processing. consider what happens if you have two profiles set to 5 seconds and 10 seconds overdue age and your nas is 15 seconds behind. Both profiles are then equally eligible to be run and nas does so in the order you specified which, if you didn't intentionally order things, might not be the order you need. 

     

    Preprocessing rules are a bit different - nas only runs the first one that matches. So if you have 2 or 100, it is only going to evaluate matches till it finds one.

     

    It would be helpful to know more about why you have created 36 preprocessing rules - On the surface of things it would seem like you only need one.

     

    -Garin



  • 4.  Re: Is there a limit for Pre-Processing rules created using NAS Auto operator

    Posted Mar 30, 2018 10:02 AM

    Hi,

     

    Droping message is one of the feature on the roadmap of my probe Static_enrichment. (however i have to find a correct UIM Lab to work on the feature).

     

    GitHub - UIM-Community/static_enrichment: CA UIM - Static message enrichment 

     

    The next release should also include middleware functions (it will answers most needs completed today by AO).

     

    Best Regards,

    Thomas