1 2 Previous Next 27 Replies Latest reply: Nov 19, 2007 10:11 AM by Yvon Quere Go to original post RSS
      • 15. RE: Wildcards in rulesets ..... ?
        Steve Mundy

        Hi Laurent,

        the P for Windows solution will be 3.1.10.

        I've forwarded your comment to the powers that be....

        thanks, Steve

        • 16. RE: Wildcards in rulesets ..... ?
          Laurent Hemeryck

          Hello Steve,

          Thanks for the reply and the forwarding. May the power be with us all.

          Have a nice weekend.

          Regs,

          Laurent

          • 17. RE: Wildcards in rulesets ..... ?
            Steve Mundy

            Hi Laurent,

            thanks, and to you....

            rgds, Steve

            • 18. RE: Wildcards in rulesets ..... ?
              Steve Mundy

              Please don't shoot the messenger.....

              The P for Windows 3.1.10 solution that will contain PKM EM 2.7.00 has been delayed a few more days so that we can get a couple of important fixes into the Windows OS KM.

              Current scheduled date for GA is now 11th April.

              • 19. RE: Wildcards in rulesets ..... ?
                Barry Stern

                Does anyone know the format for using wildcards in Instances.  I am trying to set the thresholds for specific filesystems all starting with the same name and it is not working.

                (/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/FILESYSTEM/db-npower_tables*/FSCapacity":REPLACE:"1,1 0 100 0 0 0,1 98 99 0 0 1,1 99 100 0 0 2)

                • 20. RE: Wildcards in rulesets ..... ?
                  Laurent Hemeryck

                  Hello,

                  BMC has just published more information about the wildcards in the Release Notes of the latest version, namely 2.7.05.
                  Here are some details :
                  "When PATROL KM for Event Management attempts to find a match for an instance name listed in a rule, the KM uses the following order:
                  1. instance name (sid)
                  2. wildcard
                     A. — apply to all except for specific instances
                     B. . — apply to all but those containing a character or character set specified in another wildcard
                     C. h where h is a variable representing any character or set of characters — apply to all containing the designated character set
                  3. __ANYINST__"
                  Please note that the case B starts with a point before the '{' character.
                  Additionally, here are some rule examples :
                  "Rule 1 /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/NT_CPU/CPU_0/CPUprcrProcessorTimePercent
                  Rule 2 /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/NT_CPU/__ANYINST__/CPUprcrProcessorTimePercent
                  Rule 3 /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/NT_CPU/{re:*}2/CPUprcrProcessorTimePercent
                  Rule 4 /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/NT_CPU//CPUprcrProcessorTimePercent
                  Rule 5 /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/NT_CPU/./CPUprcrProcessorTimePercent"
                  So, for your case, that would give the following :

                  /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/FILESYSTEM/db-npower_tables{re:*}/FSCapacity



                  Regs,

                  Laurent

                  • 21. RE: Wildcards in rulesets ..... ?
                    Barry Stern

                    Thanks for the information. I found the documentation you are refering too. But I still can not seem to get it to work. I tried as your suggested.
                    /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/FILESYSTEM/db-npower_tables/FSCapacity
                    I tried
                    /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/FILESYSTEM/db-npower_tables/FSCapacity
                    /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/FILESYSTEM/db/FSCapacity

                    Non worked.

                    • 22. RE: Wildcards in rulesets ..... ?
                      Steve Mundy

                      Hi,

                      Make sure you also have the following defined:

                      /AS/EVENTSPRING/processWildCards=1



                      rgds, Steve

                      • 23. RE: Wildcards in rulesets ..... ?
                        ben shirley

                        Hello, does anyone know when this was fixed and in what release. We monitor a Log using the log km, it gets cycled ie.

                        log01.txt
                        log02.txt
                        log03.txt etc

                        We want the thresholds on the LogFileSize to remain the same, when patrol discovers the new latest log it doesn't keep the thresholds. If we used the __ANYINST__ option it would put the threshold on all new logs - not desired.

                        We need a ruleset like:

                        /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/LOGMON/Test_Logfile*/LOGFileSize

                        • 24. RE: Wildcards in rulesets ..... ?
                          Stuart Chandler

                          you need to put that intelligence in the file that you define , this thread is about wildcading the instances in the variable that manages the alert threshold.

                          I believe you can set the LOG km to do wildcard matches but you should check the LOG km docs to be sure.

                          • 25. RE: Wildcards in rulesets ..... ?
                            Adam Watson

                            Hi there i'm trying to use wildcards for the first time. My two rules so far are:

                            /AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/NT_LOGICAL_DISKS/&#123;re&#58;*&#125;mb2/LDldFreeSpacePercent<br />/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/NT_LOGICAL_DISKS/__ANYINST__/LDldFreeSpacePercent



                            but the agent is going strait to the anyinst rule.

                            I have my /AS/EVENTSPRING/processWildCards=1

                            Any one got any clues as to where i'm going wrong?

                            • 26. RE: Wildcards in rulesets ..... ?
                              Denis Peuziat

                              Hi,

                              I do have the same problem with VSM KM:

                              "/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/VSM_VM/NCESATURNV/Status" = { REPLACE = "1,1 0 3 0 0 2,1 2 2 0 0 1,1 3 3 0 0 2" },
                              "/AS/EVENTSPRING/PARAM_SETTINGS/THRESHOLDS/VSM_VM/__ANYINST__/Status" = { REPLACE = "1,0 0 0 0 0 0,0 0 0 0 0 0,0 0 0 0 0 0" }

                              and I have alos set /AS/EVENTSPRING/processWildCards=1

                              but the rule seem to take only the __ANYINST__ into account....

                              If someone knows what's wrong....or I'll open an incident to BMC...

                              Thanks

                              Denis

                              • 27. RE: Wildcards in rulesets ..... ?
                                Yvon Quere

                                "Hello, does anyone know when this was fixed and in what release. We monitor a Log using the log km, it gets cycled ie.

                                log01.txt
                                log02.txt
                                log03.txt etc

                                We want the thresholds on the LogFileSize to remain the same, when patrol discovers the new latest log it doesn't keep the thresholds. "

                                As Stuart mentionned, the LOG KM can use wildcards in file definition. In this situation, Patrol will take care of the more recent file matching the wildcard.

                                Example taken from an agent out there :
                                "/PMG/CONFIG/LogAppli_Database__/actName" = { REPLACE = "/applis/tlcp/valid/log/LOG.????" },


                                Sorry for being off-topic.

                                1 2 Previous Next