Dynatrace Hub - latest extensions

Mulesoft Cloudhub (Extension v2) 3.1.1

Thu, 01 Oct 2026 16:46:26 +0000

Fixed in this version:

Issue when CloudHub API returns null for some responses was not handled.

PostgreSQL 3.2.9

Thu, 01 Oct 2026 13:08:46 +0000

Bugfixes

Fixed bug where schema data would not be correctly associated with the DB_DATABASE_POSTGRES nodes.

⚠️ This version requires ActiveGate version 1.341.0 or higher.

Cisco Catalyst SD-WAN Manager (Viptela) 2.2.2

Thu, 01 Oct 2026 10:01:36 +0000

New in this version

Alarm reporting improvements. Cisco SD-WAN raises a new alarm every day for a lasting problem, such as an expired certificate, and for many alarm types it never clears one. The extension now groups alarms by the condition they describe, so one condition raises one problem instead of one per alarm record. The problem stays open while the condition keeps being reported, and closes when the alarm clears or when it stops being reported. Each closing log record says which of the two happened.

Note: Cisco SD-WAN alarms carry no correlation ID, so the extension works out which alarms belong to the same condition on a best-effort basis. If the grouping does not match what you expect, rely on the alarm log records: they hold the alarm payload exactly as Cisco SD-WAN Manager reported it.
Certificates. A new optional certificates feature set reports how many days are left before each device certificate expires. It covers controllers and edge routers.

| Metric | Description | | --- | --- | | cisco.sdwan.device.certificate.days_remaining | Days left until this device certificate expires |

It is split by fabric_infra, system_ip, host_name, site_id, site_name, device_model and device_type.

A negative value means the certificate has already expired. For example, -30 means it expired 30 days ago.

Three alert templates come with it: Certificate Expired, Expiry Imminent (7 days) and Expiring Soon (30 days). They do not overlap, so one certificate raises only one problem.

The new Certificate Collection Frequency setting controls how often certificates are queried: every 30 minutes by default, from 15 to 1440 minutes.
Site names and coordinates on Smartscape nodes. You can now group a Smartscape segment by a readable site name instead of a site ID. Devices and sites also carry map coordinates, so you can place them on a Dynatrace map with no extra work.

⚠ Breaking change. The coordinate fields were renamed from latitude and longitude to geo.location.latitude and geo.location.longitude. Update any query or dashboard that reads the old names. Classic entities and the site screen are not affected.
Device control plane. A new optional device_control_plane feature set turns ten control-plane values into metrics. Each total has a matching up counter — compare the two to find a session that is down. Until now these values were only static device properties. You can now chart them, alert on them and use them in SLOs.

| Metric | Description | | --- | --- | | cisco.sdwan.device.control_plane.control_connections | Total control connections this device has to vSmart, vBond and vManage | | cisco.sdwan.device.control_plane.control_connections_up | Control connections that are currently up | | cisco.sdwan.device.control_plane.vsmart_control_connections | Control connections to vSmart controllers | | cisco.sdwan.device.control_plane.expected_vsmart_connections | Control connections to vSmart controllers this device should have | | cisco.sdwan.device.control_plane.omp_peers | Total OMP peers of this device | | cisco.sdwan.device.control_plane.omp_peers_up | OMP peers that are currently up | | cisco.sdwan.device.control_plane.bfd_sessions | Total BFD sessions of this device | | cisco.sdwan.device.control_plane.bfd_sessions_up | BFD sessions that are currently up | | cisco.sdwan.device.control_plane.total_tloc_num | Total transport locators (TLOCs) of this device | | cisco.sdwan.device.control_plane.up_tloc_num | Transport locators that are currently up |

All ten are split by fabric_infra, system_ip, host_name, site_id, site_name, friendly_site_name, device_model and device_type.

New charts show them on the device and SD-WAN infrastructure screens.

These are totals for the whole device. The Circuit availability metrics count similar sessions per transport, so the two sets of numbers do not add up to each other. That is expected.

⚠ Existing monitoring configurations must enable Device control plane before the metrics start to flow. New configurations have it on by default.
SD-WAN events as log records. Cisco SD-WAN Manager reports events as single points in time. Each one is now a Dynatrace log record with its severity, component, name, device and site, shown in a new SD-WAN Events card on the SD-WAN infrastructure, site and device screens. Events never become Dynatrace problems.

⚠ Collection is off by default. Turn on Report SD-WAN Events as Logs in the monitoring configuration, and set the SD-WAN Event Severity Filter before you do. All severities are collected unless you narrow it, and Minor events such as logins and logouts can be very frequent. Cisco SD-WAN Manager applies the filter itself, so excluded events are never transferred.

The new SD-WAN Events Collection Frequency setting controls how often events are queried: every 15 minutes by default, from 5 to 360 minutes. It also sets how often the event count metric below is reported.
Event volume metric. A new optional events feature set, shown as SD-WAN events, counts the events Cisco SD-WAN Manager reports, so you can chart and alert on event volume.

| Metric | Description | | --- | --- | | cisco.sdwan.device.event_count.gauge | Number of SD-WAN events reported for this device, per severity and per 5-minute interval |

Note: In DQL, use the key cisco.sdwan.device.event_count, without .gauge. The FAQ Why do some metric keys end in .gauge or .count, and which key do I use in DQL? in the extension documentation explains why.

It is split by fabric_infra, system_ip, host_name, site_id, site_name, friendly_site_name, device_model, device.address and event_severity.

A new SD-WAN Events by Severity chart shows it on the SD-WAN infrastructure, site and device screens.

⚠ It is off by default and adds one API call per collection cycle. Existing monitoring configurations must enable SD-WAN events before the metric starts to flow.

⭐ Reporting SD-WAN events as log records is a separate thing and is not affected by this feature set. Log records are controlled only by the Report SD-WAN Events as Logs configuration property. You can have the log records without the metric, or the metric without the log records.
Davis event Smartscape enrichment. Every Cisco SD-WAN alarm Davis event is now enriched with the Smartscape source properties (dt.smartscape_source.id, dt.smartscape_source.type, dt.smartscape.ext_network_device) so that the event links to the correct EXT_NETWORK_DEVICE Smartscape node for RCA and entity-centric views. The node ID is computed deterministically with smartscape_id() from dt-ppx-utils.

Changed in this version

⚠ The alarm count metric now reports one data point per time interval, timestamped with the interval it covers. Charts now line up with the alarm histogram in Cisco SD-WAN Manager, and intervals missed during a short outage are filled in afterwards. Please re-check any dashboard or alert built on this metric — it produces fewer data points than before.

The interval is set by Alarm Count Resolution, 15 minutes by default. This setting was previously called Alarms Collection Frequency, which was misleading: it never changed how often alarms are collected. Renamed only, the behaviour is the same.

Alarm log records and alarm-driven Dynatrace problems are not affected.
The alarm filter field Rule Name is now called Alarm Type, the name Cisco SD-WAN Manager uses in its alarms table. Renamed only: existing filters keep working.
Alarms and SD-WAN events are now grouped into tabs on the SD-WAN infrastructure, site and device screens, instead of five cards stacked down the page.
The alarm distribution charts are now stacked columns over time.

Fixed in this version

⚠ TLOC octets are now reported as a delta metric. cisco.sdwan.tloc.rx_octets and cisco.sdwan.tloc.tx_octets count the bytes received and sent, so they are now reported as a delta instead of a gauge.
- Latest Dynatrace (Grail): no impact.
- Dynatrace classic (Data Explorer, classic dashboards and screens): after the upgrade, newly collected data points must be accessed using the keys cisco.sdwan.tloc.rx_octets.count and cisco.sdwan.tloc.tx_octets.count. Use these keys in Data Explorer and in your own charts; the extension's screens already use them. Data from before the upgrade is not lost: read it in Data Explorer with cisco.sdwan.tloc.rx_octets and cisco.sdwan.tloc.tx_octets.
An invalid Friendly Site Name Pattern no longer breaks collection. Patterns are checked when the extension starts and any problem is reported as a warning.
TLOC Smartscape node name fixed. It now reads host:colour:protocol — for example SDW_BR4:biz-internet:IPSEC. Existing nodes are renamed on the next entity report; no new TLOC nodes are created.
Lower memory use. The extension now needs less memory to collect statistics. This avoids the ActiveGate python memory limit. Nothing changes about which metrics are reported, or their values.

If you still see memory problems, lower the page size in the expert settings. A smaller page needs less memory. But it also sends more requests to Cisco SD-WAN Manager, so you may need a longer metrics collection frequency. The FAQ in the documentation explains how to choose a value.

VMware (remote monitoring) 4.5.0

Wed, 30 Sep 2026 16:49:04 +0000

4.5.0

Updated error handling
Adds vCenter tags to VMware Smartscape Nodes.
- See explanation in the Monitoring vCenter Tags/Custom Attributes section of the monitoring configuration.

SSL Certificate Monitor 2.2.1

Wed, 30 Sep 2026 13:03:18 +0000

Changelog

2.2.1

This version requires a minimum Dynatrace version of 1.343.0 and a minimum EEC version of 1.318.0

Added

Added options to handle self-signed certificates and a new self_signed attribute appears on all certificate entities and UA screens (with a column and filter). Users can also configure the extension to either exclude self-signed certificates from all monitoring or suppress alerts only while retaining metrics and log events.
Added support for custom event properties: users can now configure a list of key-value pairs that are attached to all certificate problem events.

Fixed

Fixed crash in Windows Certificate Store scan when a certificate has a NotAfter date that cannot be parsed (e.g. "never expires" set to 9999-12-31); such dates are now correctly parsed. Other parsing errors cause certificates to be skipped with a warning log rather than aborting the entire scan.

Oracle Database 4.3.0

Wed, 30 Sep 2026 11:09:55 +0000

✨ New in this version:

Add a database-level com.dynatrace.extension.sql-oracle.datafile.max_parameter metric that contains the value of the DB_FILES database paramater. This metric, in combination with com.dynatrace.extension.sql-oracle.datafile.status, can be used to alert on when the number of datafiles is approaching the maximum.

🪲 Fixed in this version:

Fixed issue where execution plan collection would throw an error on RAC setups.

VMware (remote monitoring) 4.4.0

Tue, 29 Sep 2026 14:44:59 +0000

4.4.0

Updated vCenter Events to be ingested with correct severity.
- Also added the ability to change event severities via the configuration.

Dell iDRAC 2.1.1

Mon, 28 Sep 2026 12:36:13 +0000

2.1.1

Add credential vault support for 'Session Token' authentication method.

Stonebranch Universal Automation Center 2.0.12

Mon, 28 Sep 2026 11:45:27 +0000

New in this version:

This extension is now using all rich visualization features of Grail within Infrastructure & Operations App and the dashboards

Proxmox 1.2.0

Fri, 25 Sep 2026 14:12:07 +0000

Version 1.2.0

Initial release of the Proxmox extension

Couchbase 4.0.0

Fri, 25 Sep 2026 13:49:14 +0000

Release 4.0.0

WARNING: Possible breaking changes and warnings - PLEASE READ before upgrading

This version requires a minimum Dynatrace version of 1.343 and a minimum EEC version of 1.318.

New in this version

Local deployment of the extension has been revamped.

What's changed

Two local deployment scenarios of the extension now have enhanced support: One node per host in a multi-node cluster and multiple nodes on a single host. When a Couchbase cluster node is monitored by the OneAgent, local deployment of the extension offers fast, efficient monitoring.

Impact

Monitoring configurations that were utilizing the previous, "Multiple nodes are deployed on a single host" configuration will have to recreate those configurations. This affects a very small number of configurations and will be apparent when upgrading the extension. All remote configurations are unaffected by this change and can upgrade without any impact.

Microsoft Active Directory monitoring 6.2.4

Fri, 25 Sep 2026 12:12:54 +0000

Improved in this version:

Fix issue with DNS Zone Transfer Status metric using the last zone transfer time instead of the last SOA check
Fix issue with creating some Directory Service event ID ingest rules

Microsoft Exchange Server 2.0.3

Thu, 24 Sep 2026 16:56:34 +0000

Release 2.0.3

This version requires a minimum Dynatrace version of 1.345.0 and a minimum EEC version of 1.318.0.

New in this version

Added 2nd and 3rd generation alert templates for "High priority, high length, external queues". Use this template to alert only on high priority external queues or easily modify the template to alert on other queue priorities or queue types.

Generic Cisco Device 4.1.4

Thu, 24 Sep 2026 02:12:42 +0000

✨ New in this version:

Alert templates enriched with:
- dt.source_entity for classic entities
- dt.smartscape_source.id for 3rd-gen Smartscape nodes
Configurable polling interval added:
- Default of 5 minutes for interface metrics
- Default of 1 minute for all other metrics
- Can be adjusted in the extension configuration with Polling interval for interface metrics (minutes) and Polling interval (minutes) ℹ️ This version requires a minimum Dynatrace version of 1.345.0 and a minimum ActiveGate EEC version of 1.339.0.

IBM MQ 4.3.4

Thu, 24 Sep 2026 01:57:45 +0000

New in this version:

Gateway mode now allows for comma-separated multi-host gateway for multi-instanced or failover set up.

Fixed in this version

Issue sending topology to Settings API when it's a new entry.
Issue when collecting SYSTEM events that would cause it to repeat them if no new events were found.
Issue with filters in inventory screens were not showing.
Issue where Problem events were not linking to new Smartscape entities.

HPE Integrated Lights-Out (iLO) 2.2.1

Thu, 24 Sep 2026 00:45:30 +0000

Changes in this release:

Increased number of endpoints allowed per monitoring configuration, up to 20,000.

NOTE: Please be sure to size your ActiveGates accordingly. Number of endpoints in a monitoring configuration will proportionally consume more resources.

Qualys 1.2.1

Wed, 23 Sep 2026 18:50:03 +0000

Requires Dynatrace and EEC (ActiveGate) version 1.310.0

Features:

Included log metric configuration (log.qualys_vulnerability_count) and related classic dashboard for use in Managed environments
Include tags on ingested findings
Added qualys.qid field to vulnerability findings

Fixes:

Improved retry behavior
Handle missing KnowledgeBase entry

AWS Cloud Monitoring 1.2.1

Wed, 23 Sep 2026 13:36:08 +0000

Version 1.2.1

What's new:

Added support for metrcis for AWS/Bedrock (runtime inference), AWS/Polly, AWS/Rekognition, AWS/Route53Resolver, AWS/SES, AWS/SSM-RunCommand, AWS/Textract, AWS/Transfer, AWS/TrustedAdvisor, AWS/Usage and AWS/WorkSpaces namespaces.
Added FreeStorageCapacity metric in AWS/FSx namespace
Added support of FileSystemId dimension for StorageCapacityUtilization metric in AWS/FSx namespace
AWS/VPN metrics are now polled with the [VpnId] dimension set in addition to [VpnId, TunnelIpAddress], enabling data collection for VPN connections that publish metrics without the TunnelIpAddress dimension
Added PeakLCUs and ReservedLCUs to recommended metrics for AWS/ApplicationELB.

Bug fixes:

Fixed linking of AWS/ApiGateway metrics to ApiGateway RestApi V1 entities
AWS/Neptune metrics are now linked to AWS::RDS::DBCluster and AWS::RDS::DBInstance resource types instead of non-existent AWS::Neptune::DBCluster and AWS::Neptune::DBInstance.

MongoDB Atlas 4.2.6

Wed, 23 Sep 2026 11:38:55 +0000

Fixes and Improvements

Fix a bug where the database metric lookback period was too low.

Apache Kafka 3.1.4

Wed, 23 Sep 2026 08:15:12 +0000

Properly categorize Kafka under Messaging instead of Application.
Added smartscape node extraction to Anomaly Detection Templates.