8 Replies Latest reply on Apr 8, 2015 11:43 PM by Robert Dyer

    Has CPUCpuUtil top process annotation been removed/disabled?

    Robert Dyer

      BPPM for Unix/Linux used to annotate high CPU process information to CPUCpuUtil graphs in both PATROL Central and in ProactiveNet. For our Sys Admins who are generally spoilt for product/tool choice it was a useful selling point. Annotations happened when CPU Warning and Alarm thresholds were breached. Recently I've noticed newer installs don't annotate (specifically release 9.12 Version 16.16, 16.17) .. I've raised a support request but they've suggested the annotation has been removed because of customer complaints about size of annotation data. Can anyone confirm whether or not the annotation of the top processes to the CPUCpuUtil parameter has been removed/disabled ? We're supposed to create an IDEA for most other development activity requests .. has anyone seen an IDEA asking for us to vote to remove/disable this functionality 'out of the box'? Do others think there is still value in this 'top processes' annotation feature/function?

        • 1. Re: Has CPUCpuUtil top process annotation been removed/disabled?
          Tony Boman

          I have just checked the latest CPU.km file in version 9.12.00 and the annotate recovery action is still there. I will test it.

           

          Regards,

          Tony

          • 2. Re: Has CPUCpuUtil top process annotation been removed/disabled?
            Tony Boman

            Okay, interesting. The auto_annotate_ps() function is still in the code and still exists in the unix_misc_lib.lib library file. However, in my testing, this does not seem to be working.

             

            I will try to see if this is a known issue, but I can say that the functionality has not been removed on purpose.

             

            Regards,

            Tony

            1 of 1 people found this helpful
            • 3. Re: Has CPUCpuUtil top process annotation been removed/disabled?
              Robert Dyer

              Hi Tony, latest response from support contact: "confirmed with dev team, the annotation feature is disabled in version 9120 for CPUCpuUtil for some reasons. Our dev team is considering if necessary to re-enable it in the next version or next patch." Quite weird that such an important feature was disabled. :-(  I'll try and find out the Product Managers contact details and ask why they asked for such a great feature to be disabled; surely dev can't make such decisions for themselves.

              • 4. Re: Has CPUCpuUtil top process annotation been removed/disabled?
                Tony Boman

                Thanks for the information Robert. Be interested in the response from the Product Manager.

                 

                Regards,

                Tony

                • 5. Re: Has CPUCpuUtil top process annotation been removed/disabled?
                  Jonathan Coop

                  Of course it would be possible to put this feature in yourself by using a recovery action that grabs the contents of the parameter /PROCESS/PROCESS/PROCTopProcs and running the annotate function.

                   

                  The nice thing about event manager Km recovery actions is that they can be stored in a pconfig variables and easily sent out to all the agents you want using PCM or make a policy in bppm, bad news is that there has to be a state change for it to be run so there must be a change from OK to Warning or Alarm.

                   

                  Something like the following, could be put into a ruleset and then sent out to the agents,

                  I think you'll then have to restart the agents.

                  PATROL_CONFIG

                  "/AS/EVENTSPRING/CPU/CPU/CPUCpuUtil/arsAction" = { REPLACE = "2" },

                  "/AS/EVENTSPRING/CPU/CPU/CPUCpuUtil/arsCmdType" = { REPLACE = "PSL" },

                  "/AS/EVENTSPRING/CPU/CPU/CPUCpuUtil/arsCommand" = { REPLACE = "annotate(\"/CPU/CPU/CPUCpuUtil\",\"\",nthlinef(get(\"/PROCESS/PROCESS/PROCTopProcs/value\"),\"2-\"));" }

                   

                   

                  Hope this helps

                  • 6. Re: Has CPUCpuUtil top process annotation been removed/disabled?
                    Robert Dyer

                    Or, as supplied by customer support as a workaround,

                     

                    PATROL_CONFIG
                    "/AS/EVENTSPRING/CPU/CPU/CPUCpuUtil/arsAction" = { REPLACE = "2" },

                    "/AS/EVENTSPRING/CPU/CPU/CPUCpuUtil/arsCmdType" = { REPLACE = "PSL" },

                    "/AS/EVENTSPRING/CPU/CPU/CPUCpuUtil/arsCommand" = { REPLACE = "if(exists(\"/PROCESS/PROCESS/PROCTopProcs\") && get(\"/PROCESS/PROCESS/PROCTopProcs/status\") != \"OFFLINE\"){ top_procs = get(\"/PROCESS/PROCESS/PROCTopProcs/value\"); top_procs = nthlinef(top_procs,\"2-\"); } else { top_procs = \"/PROCESS/PROCESS/PROCTopProcs not available\"; } if(exists(\"/PROCESS/PROCESS/PROCNumProcs\") && get(\"/PROCESS/PROCESS/PROCNumProcs/status\") != \"OFFLINE\"){ num_procs = get(\"/PROCESS/PROCESS/PROCNumProcs/value\"); } else { num_procs = \"/PROCESS/PROCESS/PROCNumProcs not available\"; } annotate(\"/CPU/CPU/CPUCpuUtil\", \"%Text\", top_procs.\"\\n\\n\".num_procs.\" processes total\" ); " }

                    • 7. Re: Has CPUCpuUtil top process annotation been removed/disabled?
                      Jon Trotter

                      Robert, did you get this implemented yet?  We have a similar situation we are trying to implement and just curious if anyone has tried this so far or if there were any issues when configuring this with Unix/Linux.

                      • 8. Re: Has CPUCpuUtil top process annotation been removed/disabled?
                        Robert Dyer

                        Yes, the BMC Support work around is working fine. Though, I think it was BMC's intention to re-add the functionality for CPU process annotations into the latest KM's. I've not had time to check that it is in the latest Linux KM.