Overview
Monitor the status of your Control-M Jobs.
Details
Metrics
- Jobs - Ended OK
- Jobs - Wait Condition
- Jobs - Executing
- Jobs - Wait Resource
- Jobs - Wait User
- Jobs - Ended Not OK
- Jobs - Unknown
- Jobs - Not in AJF
Events
For each job that ends in โEnded Not OK", an event is sent to Dynatrace with the details:
- Job Name
- Job ID
- Execution Start Time
- Execution End Time
- Status
- Number of executions
Each Control-M monitored will consume ~4204.8 DDUs/year
Installation
Requirements
- Control-M Automation API at
/automation-api/run/jobs/status
reachable.
- User permissions
- Category: Client Access
- Control-M Automation API: Full
- Active Authorizations
- For accessing jobs run information. Active Privileges filter need to allow access to the jobs
- Environment ActiveGate server - Extract the extension zip file to the plugin_deployment folder of the remote plugin module
- In a default installation this is done with
unzip -o -d /opt/dynatrace/remotepluginmodule/plugin_deployment Filecustom.remote.python.controlm.zip
- Adjust the path if the Activegate was installed somewhere other than
/opt/dynatrace
- Browser - Upload the same extension zip file to your tenant
Settings > Monitored technologies > Custom extensions > Upload extension
Configuration
Create an endpoint for each cluster you would like to monitor. This is done in `Settings > Monitored technologies > Custom extensions > ControlM.
The parameters are:
- Control-M URL
- e.g.
https://<IP_or_HOSTNAME>:8443
- Control-M Username
- Control-M Password
Troubleshooting
Extension Logs
The logs under %PROGRAMDATA%
(windows) or /var/lib
(linux) give us more details in case of failures
The full path is /var/lib/dynatrace/remotepluginmodule/log/remoteplugin/custom.remote.python.controlm/ControlMPlugin.log
or
C:\ProgramData\dynatrace\remotepluginmodule\log\remoteplugin\custom.remote.python.controlm/ControlMPlugin.log