Manoj Kumar Behera
Hi Team,
I have a requirement to send out alert emails to management/business users on some process completion by a set of control-M jobs. I was able to do that successfully in control-M V7 but now after migrating to control-M V9 I was told an INCIDENT is a must to be associated with for any alert emails sent.
As a consequence we are getting many unwanted INCIDENTS generated in our GSD queue on a daily basis.
Can you help me provide a way where I can send those alert emails upon control-M job completions only to the email groups set up in Xmatters but don't want any associated INCIDENTs to be generated for each email alerts. As these alerts are not real INCIDENTs and they are only for information purpose.
Thanks,
Manoj Kumar Behera
0
Comments
Please sign in to leave a comment.
Hey Manoj!
Where are these Incidents being generated? I'm not too familiar with Control-M so I'm not sure if it can support incidents or you are saying these incidents are being created in another tool.
Anyway, if you are using this Control-M v9 integration, it looks like Control-M triggers the Integration agent via a command line call to IAHOME/APClient.bin(.exe), which is probably on the Control-M box. From there it runs the javascript in the IA's integration service for Control-M to map the payload to generate an event in xMatters.
So, if it is xMatters code triggering this Incident, it will likely be in there. Although note that there are no incidents created anywhere in the out of box integration, so someone may have modified the files for the business use cases at the time.
If you aren't sure how to make heads or tails of this, you can post the contents of the IAHOME/integrationservices/applications/controlm-401/controlm.js file which will probably be on the Control-M server. This file is just a code file and shouldn't have any credentials stored in it, but not a bad idea to give it a once over before posting on a public forum.
Let us know if you can't find it.
Happy Wednesday!
--- Travis