8 Replies Latest reply on Feb 20, 2019 6:30 PM by Brendan Murray

    dup_detect policy

    Chaitanya Gokhale
      Share:|

      Team,

      I have create one custom class 'eGInnovation'. For this class only we need to create dup_detect policy with below condition :-

       

      if below slots value is common append the new event on older event. (Ignore other slots.)

       

      mc_long_msg

      mc_object

      mc_object_class

      mc_parameter

       

      any idea how to achieve this?

       

      Thanks

      Chaitanya

        • 1. Re: dup_detect policy
          Kaushik KM

          Hi Chaitanya Gokhale,
          Please find the below definition sample :

           

          MC_EV_CLASS : MYCLASSNAME ISA EVENT

          DEFINES

          {

              patrolAccountName : STRING;

              mc_host_class : STRING, dup_detect=yes;

              mc_host : STRING, dup_detect=yes;

              mc_object_class : STRING, dup_detect=yes;

              mc_object : STRING, dup_detect=yes;

              mc_parameter : STRING, dup_detect=yes;

              mc_tool_class : STRING, dup_detect=yes;

              mc_tool : STRING, dup_detect=yes;

          };

          END

           

          you can replace the slots which you want and remove the others..

          Please let me know if you were looking for something else.

           

          Thanks,

          Kaushik KM

          1 of 1 people found this helpful
          • 2. Re: dup_detect policy
            Chaitanya Gokhale

            Hi Kaushik KM

             

            Thanks for update. Just one doubt , this all are default slots, still i can use it?

             

            Thanks

            Chaitanya

            • 3. Re: dup_detect policy
              Chaitanya Gokhale

              Hi Kaushik KM

               

              Also what will be the case if i receive OK alarm.  In that case also it will apply dup_detect?

              • 4. Re: dup_detect policy
                Brendan Murray

                Hi Chaitanya,

                 

                Yes, if you create a subclass of the EVENT class you can change the slot facets (such as dup_detect) in the subclass. Kaushik's example defines a subclass called MYCLASSNAME.

                 

                Regards,

                 

                Brendan

                • 5. Re: dup_detect policy
                  Brendan Murray

                  Hi Chaitanya,

                   

                  Yes, OK events will be treated as duplicates if you don't set dup_detect to 'yes' on the severity slot. OK events that match the mc_long_msg, mc_object, mc_object_class, mc_parameter slots of events of other severities will be considered duplicates.

                   

                  If you want to de-duplicate only events of the same severity, either set dup_detect=yes in your subclass or set the selector of your recurrence policy to exclude OK events. Note that if you use the selector approach, if you get multiple OK events for the same mc_long_msg, mc_object, mc_object_class and mc_parameter values, they will not be de-duplicated.

                   

                  Regards,

                   

                  Brendan

                  2 of 2 people found this helpful
                  • 6. Re: dup_detect policy
                    Chaitanya Gokhale

                    Hi Brendan Murray , Kaushik KM

                     

                    Thanks for your help. Its working now as expected.

                    Just one update. When I updated only in class file it didn't work. Then I created reoccurrence policy & it works.

                     

                    Both the things needed to manage duplicate alarms? Class file changes as well as creation of reoccurrence policy?

                    hope I am doing correct.

                    • 7. Re: dup_detect policy
                      Chaitanya Gokhale

                      One more question here,

                      We have integrated truesight with remedyforce for ticketing.

                      With duplicate policy its updating severity (I didn't consider severity in dup_detect). Client wants to updates same event only if there a change is severity.

                      So we are considering only below slots for dup_detect.

                       

                      mc_long_msg,

                      mc_object,

                      mc_object_class

                      mc_parameter

                      mc_host.

                       

                      Now if any critical events come its generate a ticket in remedyforce. once utilization reduce it generate major alert which appends the previous event & increase repeat count as 1.

                      But in this case ticket in remedyforce not getting closed. (Client only wants critical tickets should be logged in remedy force)

                      • 8. Re: dup_detect policy
                        Brendan Murray

                        Hi Chaitanya,

                         

                        Yes, you are correct. You must set the dup_detect facets on the slots you want to use for de-duplication and then you must create a recurrence policy to turn on de-duplication for the set of events defined by the selector of the recurrence policy. Just setting the dup_detect facet on its own does nothing.

                         

                        Regards,

                         

                        Brendan

                        1 of 1 people found this helpful