<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Dynatrace Hub - Control-M latest releases</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>A list of extensions from Control-M</description><atom:link href="https://hub-manager.hub.central.dynatrace.com/api/v1/public-hub/feed/extensions/control-m-jobs-v2/" rel="self"/><language>en-us</language><lastBuildDate>Thu, 30 Jul 2026 14:14:10 +0000</lastBuildDate><item><title>Control-M 3.2.3</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;ul&gt;
&lt;li&gt;This extension is now using all rich visualization features of Grail within Infrastructure &amp;amp; Operations App.&lt;/li&gt;
&lt;li&gt;Fixed a bug where SmartScape Edges between job/folder and instance were not working.&lt;/li&gt;
&lt;li&gt;The extension does not monitor Sub-Tables as jobs anymore.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 30 Jul 2026 14:14:10 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 3.0.1</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;h3&gt;⚠️WARNING⚠️: Possible breaking changes and warnings - PLEASE READ before upgrading:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;This version requires a &lt;em&gt;minimum Dynatrace version&lt;/em&gt; of &lt;code&gt;1.338.0&lt;/code&gt; and a &lt;em&gt;minimum EEC version&lt;/em&gt; of &lt;code&gt;1.289.0&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;This version includes a breaking change for Dynatrace on Grail.
&lt;ul&gt;
&lt;li&gt;With the inclusion of OpenPipeline processing rules, any metrics ingested from the extension will be processed by a dedicated OpenPipeline pipeline.&lt;/li&gt;
&lt;li&gt;This means that any dynamic route configured to process any metrics from the extension will be dropped in favor of the dedicated pipeline. Please, refer to &lt;a href="https://docs.dynatrace.com/docs/platform/openpipeline/concepts/pipeline-groups"&gt;pipeline groups&lt;/a&gt; to continue using dynamic routes.&lt;/li&gt;
&lt;li&gt;With the inclusion of OpenPipeline processing rules, any logs ingested from the extension will be processed by a dedicated OpenPipeline pipeline instead of the &lt;a href="https://docs.dynatrace.com/docs/shortlink/lma-classic-log-processing"&gt;classic log pipeline&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;This means that classic rules will no longer be used on logs ingested from the extension. Please be sure to migrate any you still need to &lt;a href="https://docs.dynatrace.com/docs/shortlink/lma-openpipeline"&gt;OpenPipeline rules&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Additionally, some field names are &lt;a href="https://docs.dynatrace.com/docs/platform/openpipeline/concepts/processing#pipeline"&gt;handled differently&lt;/a&gt; in OpenPipeline, e.g. capitalization. Please double-check any custom dashboards and alerts you have created for this extension.&lt;/li&gt;
&lt;li&gt;You must opt-in to OpenPipeline configuration via Settings API – see the &lt;a href="https://docs.dynatrace.com/docs/shortlink/openpipeline-migration-settings"&gt;documentation&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;By updating to this version, any Control-M instance entity in the Classic Topology will change name from the full configured URL to only the hostname.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3&gt;New in this version:&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://docs.dynatrace.com/docs/platform/grail/smartscape-on-grail"&gt;Smartscape on Grail&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Added feature set metadata for recommended metrics.&lt;/li&gt;
&lt;li&gt;Added a new &lt;code&gt;controlm.connectivity&lt;/code&gt; metric which is captured by default.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 20 May 2026 13:04:20 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.5.2</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;p&gt;New in this version:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added keyword key value pairs to extension&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 17 Dec 2025 14:30:41 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.5.1</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;ul&gt;
&lt;li&gt;Add credential vault support for username and password&lt;/li&gt;
&lt;li&gt;Add new filtering parameters to use on the API call: host, host group, application and subapplication.&lt;/li&gt;
&lt;li&gt;Fix bug with invalid metric lines when parsing special characters&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 23 Oct 2025 10:14:48 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.4.1</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;h4&gt;🚀 Improved in this version:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Added &lt;code&gt;description&lt;/code&gt;, &lt;code&gt;cyclic&lt;/code&gt; and &lt;code&gt;number of runs&lt;/code&gt; as dimensions for all individual jon metrics&lt;/li&gt;
&lt;li&gt;Added &lt;code&gt;device.address&lt;/code&gt; dimension to all metrics as the IP corresponding to the configured hostname, when possible&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;✨ New in this version:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Add support for the &lt;code&gt;dt.security_context&lt;/code&gt; attribute&lt;/li&gt;
&lt;li&gt;Add new platform dashboard&lt;/li&gt;
&lt;li&gt;Add platform screens&lt;/li&gt;
&lt;li&gt;Added new metric &lt;code&gt;controlm.job.number_of_runs&lt;/code&gt; to monitor the number of runs for each job&lt;/li&gt;
&lt;li&gt;Added log ingestion for each job individually to track their metadata, start and end times
&lt;ul&gt;
&lt;li&gt;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 &lt;code&gt;Monitor start and end times as logs&lt;/code&gt; switch during configuration on.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;🐛 Fixed in this version:&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;Turning on the &lt;code&gt;Debug&lt;/code&gt; flag now properly changes the log level&lt;/li&gt;
&lt;li&gt;The extension does not capture folders as jobs anymore&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 31 Jul 2025 18:45:07 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.2.0</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;h2&gt;New features:&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Added a new folder name filter&lt;/strong&gt;. 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.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 14 May 2025 20:01:28 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.1.3</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;ul&gt;
&lt;li&gt;Fixed a bug where filtering for jobs and folders would not work correctly&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Fri, 25 Oct 2024 07:44:18 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.1.2</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;ul&gt;
&lt;li&gt;Fixed a bug where filtering was not working properly when only folder filtering rules where set.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 17 Oct 2024 13:27:21 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.1.1</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;p&gt;⚠️Despite not increasing the major version, this version brings in a breaking change and updating to this version will require you to re-create your monitoring configurations.&lt;/p&gt;
&lt;p&gt;New features:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Log capture for job executions is now optional based on a new configuration parameter. It defaults to &lt;code&gt;False&lt;/code&gt; if not set.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Order Date&lt;/strong&gt; is now captured for every job, if available, as a dimension of the job status metric and as a property of the job entity.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 08 Oct 2024 07:40:23 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.0.6</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;ul&gt;
&lt;li&gt;Fixed an issue where the status &lt;strong&gt;WAIT HOST&lt;/strong&gt; was not recognized and stopped the execution of the extension, creating missing data.&lt;/li&gt;
&lt;li&gt;Added a new metric for counting &lt;strong&gt;WAIT HOST&lt;/strong&gt; status jobs&lt;/li&gt;
&lt;li&gt;Added chart for said metric to the job's screen&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 20 Aug 2024 12:22:01 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.0.5</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;ul&gt;
&lt;li&gt;Fixed a bug that prevented metrics from coming in&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 07 Aug 2024 07:41:29 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.0.4</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Required minimum version increased to 1.289 for both the ActiveGate and the Dynatrace cluster&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;Error events generated by the extension now get attached to the corresponding Control-M job entity instead of to the environment&lt;/li&gt;
&lt;li&gt;The extension now avoids querying every single job for its log on the first execution and gets only the latest ones&lt;/li&gt;
&lt;li&gt;Aded a new &lt;strong&gt;server&lt;/strong&gt; parameter that filters API results by its value&lt;/li&gt;
&lt;li&gt;The extension now iterates through multiple paginated results when the amount of jobs returned by the API is greater than 10000&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 12 Jun 2024 07:30:13 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.0.2</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;ul&gt;
&lt;li&gt;Adapted the extension to use cases where all folders in a Control-M instance have the same ID to report all folders correctly.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Wed, 20 Mar 2024 09:36:51 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.0.1</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;ul&gt;
&lt;li&gt;Fixed a broken link in the built-in dashboard.&lt;/li&gt;
&lt;li&gt;Fixed a bug where monitoring the first execution of a job would break the extension.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Tue, 05 Mar 2024 11:19:01 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item><item><title>Control-M 2.0.0</title><link>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</link><description>&lt;p&gt;Converted extension to EF2.0:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added a new metric to monitor individual job status
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;controlm.job.status&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added feature sets to control metric ingestion&lt;/li&gt;
&lt;li&gt;Added custom topology for Control-M instances, folders and jobs and their relevant relationships&lt;/li&gt;
&lt;li&gt;Added UA screens for each one of the entities&lt;/li&gt;
&lt;li&gt;Added log monitoring for individual job run logs&lt;/li&gt;
&lt;li&gt;Added overview dashboard&lt;/li&gt;
&lt;li&gt;Added filtering in the configuration to filter out jobs/folders&lt;/li&gt;
&lt;/ul&gt;
</description><pubDate>Thu, 15 Feb 2024 10:29:04 +0000</pubDate><guid>https://www.dynatrace.com/hub/detail/control-m-jobs-v2/</guid></item></channel></rss>