Control-M Jobs v2
- Product information
- Release notes
Overview
Control-M enables you to automate the scheduling and processing of your business workflows across various platforms and applications.
Monitor, understand and troubleshoot these business-critical assets with the Control-M extension.
Extension content
Content typeNumber of items included
screen layout
6
screen properties
2
list screen layout
3
document dashboard
1
screen chart groups
6
screen entities lists
5
screen actions
6
generic relationship
2
dashboards
1
generic type
3
metric metadata
11
screen logs cards
6
screen dql table
2
Feature sets
Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.
Feature setsNumber of metrics included
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Jobs waiting for condition | controlm.job_counters.wait_condition | Number of jobs with state "Waiting For Condition" | Count |
| Jobs ended ok | controlm.job_counters.ended_ok | Number of jobs with state "Ended OK" | Count |
| Jobs being executed | controlm.job_counters.executing | Number of jobs with state "Executing" | Count |
| Jobs waiting for resource | controlm.job_counters.wait_resource | Number of jobs with state "Waiting For Resource" | Count |
| Jobs waiting for user | controlm.job_counters.wait_user | Number of jobs with state "Wait User" | Count |
| Jobs waiting for host | controlm.job_counters.wait_host | Number of jobs with state "Waiting For Host" | Count |
| Jobs ended not ok | controlm.job_counters.ended_not_ok | Number of jobs with state "Ended Not OK" | Count |
| Jobs with unknown state | controlm.job_counters.unknown | Number of jobs with an unknown state | Count |
| Jobs not in AJF | controlm.job_counters.not_in_ajf | Number of jobs with state "Not In AJF(Active Job File)" | Count |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Job status | controlm.job.status | Metric that indicates the current status of each job. A value of 100 equals a job that ended correctly, a value of 0 indicates a job that ended incorrectly, was not found in AJF or has an unknown state. A value of 50 indicates a job in the middle of execution. A value of 25 indicates a job that is waiting. | Percent |
| Metric name | Metric key | Description | Unit |
|---|---|---|---|
| Job number of runs | controlm.job.number_of_runs | Number of runs that a job has individually had. | Count |
Full version history
To have more information on how to install the downloaded package, please follow the instructions on this page.
ReleaseDate
Full version history
New in this version:
- Added keyword key value pairs to extension
Full version history
- Add credential vault support for username and password
- Add new filtering parameters to use on the API call: host, host group, application and subapplication.
- Fix bug with invalid metric lines when parsing special characters
Full version history
🚀 Improved in this version:
- Added
description,cyclicandnumber of runsas dimensions for all individual jon metrics - Added
device.addressdimension to all metrics as the IP corresponding to the configured hostname, when possible
✨ New in this version:
- Add support for the
dt.security_contextattribute - Add new platform dashboard
- Add platform screens
- Added new metric
controlm.job.number_of_runsto monitor the number of runs for each job - Added log ingestion for each job individually to track their metadata, start and end times
- This new feature will be disabled by default as it will potentially heavily incur on the DDU consumption of the extension. It can be enabled by turning the
Monitor start and end times as logsswitch during configuration on.
- This new feature will be disabled by default as it will potentially heavily incur on the DDU consumption of the extension. It can be enabled by turning the
🐛 Fixed in this version:
- Turning on the
Debugflag now properly changes the log level - The extension does not capture folders as jobs anymore
Full version history
New features:
- Added a new folder name filter. Kept the original client side folder filter, but added a new filter that is query side filtering. Use this when your payloads are above the 10,000 object size limit.
Full version history
- Fixed a bug where filtering for jobs and folders would not work correctly
Full version history
- Fixed a bug where filtering was not working properly when only folder filtering rules where set.
Full version history
New features:
- Log capture for job executions is now optional based on a new configuration parameter. It defaults to
Falseif not set. - New parameter to configure how many threads the extension will spin up to capture the job's logs, if enabled. It defaults to 5 if not set.
- Order Date is now captured for every job, if available, as a dimension of the job status metric and as a property of the job entity.
Full version history
- Fixed an issue where the status WAIT HOST was not recognized and stopped the execution of the extension, creating missing data.
- Added a new metric for counting WAIT HOST status jobs
- Added chart for said metric to the job's screen
Full version history
- Fixed a bug that prevented metrics from coming in
Full version history
- Required minimum version increased to 1.289 for both the ActiveGate and the Dynatrace cluster
- Error events generated by the extension now get attached to the corresponding Control-M job entity instead of to the environment
- The extension now avoids querying every single job for its log on the first execution and gets only the latest ones
- Aded a new server parameter that filters API results by its value
- The extension now iterates through multiple paginated results when the amount of jobs returned by the API is greater than 10000
Full version history
- Adapted the extension to use cases where all folders in a Control-M instance have the same ID to report all folders correctly.
Full version history
- Fixed a broken link in the built-in dashboard.
- Fixed a bug where monitoring the first execution of a job would break the extension.
- Fixed a bug where the resource consumption of the ActiveGate running the extension would increase to unreasonable numbers based on the amount of jobs monitored.
Full version history
Converted extension to EF2.0:
- Added a new metric to monitor individual job status
- controlm.job.status
- Added feature sets to control metric ingestion
- Added custom topology for Control-M instances, folders and jobs and their relevant relationships
- Added UA screens for each one of the entities
- Added log monitoring for individual job run logs
- Added overview dashboard
- Added filtering in the configuration to filter out jobs/folders
