Control-M integration

[gustavodutra]

Hey everyone, I need some help with the Control-M extension. I want to monitor jobs that have ended with a status of "Ended not ok" in Control-M and display this information on a dashboard and create an alert for it.

I noticed that Dynatrace has an extension that does "exactly" that, but the documentation is terrible and poorly explained. In the first field, it asks for an API URL. But which API should that be?

I pointed it to the URL of my environment, and it says the integration status is ok, but it's not providing any information. Can anyone help me with configuring this?

Below are the attachments stating the status is ok, but I can't get information about anything.

I would just like an indication of which URL this would be and where to get it.

Link for documentation:
https://www.dynatrace.com/hub/detail/control-m-jobs-v2/

[Miguel_RinconG]

Hi @gustavodutra ,

Please run the activegate diagnostics. Then checking logs control-m extension.

[gustavodutra]

And after running, where are the logs?

[gustavodutra]

In the extension, it asks me for a URL. What URL would that be? Would it be the URL of my API?

Example:

https://{my-endpoint}/automation-api/

If so, I need to provide login, password and a token to pull these logs. However, Dynatrace does not accept me configuring this in the extension's JSON.

How could I do this?

[gustavodutra · Accepted solution]

Hey guys. 

I identified that my ActiveGate server was unable to communicate with my Control-M server.

After applying the appropriate security rules, I managed to return data just by specifying the previous endpoint.

[Ahmedrahbi]

hi gustavodutra, 
Is it possible to add the last execution time of a each job to the Control-M dashboard?

thanks

ahmed

[gustavodutra]

Você diz a última execução com sucesso? Se for isso, creio que não. Ele só nos trás informações da última execução com erro.

[Edit from Moderator with Google translation:

Are you referring to the last successful execution? If so, I don't think so. It only gives us information about the last execution with an error.]

[Ahmedrahbi]

yes, I mean that, what is the option available then? 

[Shea0410]

Hey! 

We had a bit of a different error. We got a 404 when the extension made the connection. We mistakenly included the automation-api/ path in the url of the host.
Thus causing this https://xxx.xxx.xxx.xxx:39533/automation-api/automation-api/session/login

Once we removed that, worked like a charm. Additional context for that stupid edge case one day! 😄

[gustavodutra]

Obrigado pela resposta.

Eu acabei desistindo de utilizar o Dynatrace para fazer essa tarefa, mas se me recordo, precisei remover o /automation-api também.

[Edit from Moderator with Google translation:

Thanks for the reply.

I ended up giving up on using Dynatrace for this task, but if I remember correctly, I had to remove /automation-api as well.]