How to stop classifier to trigger pattern for each process?

[nicks8850]

I have a scenario. For IBM DB2 there are multiple db2sysc process running on servers which are numbered like db2sysc 0,db2sysc 1, db2sysc 2 ....and so on.

Now the problem in ootb classifier and pattern are triggering pattern for each numbered process and creating a CI for each. However technically there is only 1 DB server running on the node. 

My requirement is that I need to find a way using which pattern triggers only once(either using script in Process classifier or something in pattern itself) and not for each matching db2sysc process. I Raised a support case as well and to my surprise they are not able to understand the issue yet.

Process on server

pattern execution for the same server.

[doug_schulze]

Is there a primary process that will always be there? Im thinking disable the OOB Classifier, create your own and define tighter classification criteria if the builds across the environment matches the same...And remember you can have multiple classifiers for the same class that are in the order you want them to catch. 

[nicks8850]

Thanksyou Doug for your reply. Unfortunately there is not anything more on the process to tighten the matching criteria. That was something I thought about at first and spent sometime finding it.

I could think of removing TCP port from the identifier to make it work which seems to be working with our test in our environment. However, I am not sure of the rationale to add TCP port to the identification for this this class. This seems to be the problematic one. Your thoughts?

[its_SumitNow]

Hi @nicks8850 

Go in your classifier (discovery_classy_proc_list.do) ---> Then Choose your Process classifier which is trigger --> Under Related list Triggered Probes remove entry for the pattern being triggered

This will work 🙂

Regards

Sumit

[its_SumitNow]

Hi @nicks8850 

I hope you got time to review my solution , if it worked then kindly Mark Helpful & Accept as Solution 🙂

Regards

Sumit