2 Replies Latest reply: Mar 12, 2012 12:59 PM by Walter Reich RSS

    removedServiceList with wildcard or regexp

    Walter Reich

      Running Patrol Agent 3.7.x - 3.9.x eg. BMC performance manager for servers on MS Windows sever.

      I want to dissable a Service from Service Monitoring on Windows Server running different OS Versions. Using PCM

       

      lets take the Service:   Microsoft NET Framework NGEN <version> --> short: clr_optimization_<version Number>

      for Example: clr_optimization_v4.0.30319_32

       

      every MS-Patch,64 or 32 bit OS ----> another version Number in service name --> the service might have 20 different Names, still growing. Not want to roll out every 20 Names to all our windows servers, every 2 weeks again with a new 'name' = 'new version' added.

      I want to add someting like  .../removedServiceList="clr_optimization_.*" to dissable them all including future versions!

      E.g. using wildcard or regular Expression with that Patrol Agent variable:

            /PSX__P4WinSrvs/PWK__PKMforMSWinOS_config/ServiceMonitoring/removedServiceList

       

      I have not found anything in BMC Doku or Solution Base.

       

      Any hints? Anyone tried that?

       

      thanks

       

      Walter Reich

        • 1. Re: removedServiceList with wildcard or regexp
          Garland Smith

          I'm pretty sure the removedServiceList only works with actual names,

          not regular expression.  However, you can filter the service instances

          using an exclusion list (/AgentSetup/.filterList).  The

          exclusion list works off PatrolAgent native filtering.  The filtering

          that you mentioned is KM-specirfic.

           

          Regards,

          Garland Smith

          • 2. Re: removedServiceList with wildcard or regexp
            Walter Reich

            The first step to solutin was this:

                 However, you can filter the service instances

                 using an exclusion list (/AgentSetup/.filterList).  The

                 exclusion list works off PatrolAgent native filtering

             

            Ended up with this setting.

             

            "/AgentSetup/NT_SERVICES.filterList" = { MERGE = "SERVICES_clr_optimization_.*" }

             

             

            That works immediatly the second you send that to server via PCM.

             

             

            Only one disadvantage  --> the NT Service KM allows switching ON/OFF of monitoring a NT-Service via KM-Commands in the PCO. This Service is actually invisible in PCO -> but stll might be "excluded" from monitoring.

             

            Any more testing and feedback is welcome.

             

            On other Hand --> that is the solution

             

            Regards & Thank you to Garland Smith for the hint

            Walter Reich