Dynatrace Hub - latest extensions

JFrog 1.0.7

Wed, 24 Jun 2026 13:03:16 +0000

Add proxy support for JFrog connection

Qualys 1.1.0

Tue, 23 Jun 2026 16:55:02 +0000

Requires Dynatrace and EEC (ActiveGate) version 1.310.0

Features:

Includes a configuration to ingest findings as logs instead of security events
- This enables support for Managed Dynatrace environments (without Grail)
- Note that all of the features and dashboards that require the latest Dynatrace (with Grail) do not have equivalents for Managed environments in this version
- You can find these findings logs by filtering for the log.source of "extension:com.dynatrace.extension.qualys" and the security.event.kind of "SECURITY_EVENT". Log processing rules can be used in Managed environments to help with better searching, creating metrics based on the finding logs, and generating problem events.

Generic Cisco Device 4.0.9

Tue, 23 Jun 2026 14:35:08 +0000

Requires Dynatrace version 1.338.0 and EEC (ActiveGate) version 1.333.0

Fixes:

Adjusts the DQL query definition used in several latest Dynatrace screens to avoid showing data for other devices when viewing a specific Cisco device

IBM Informix 3.0.2

Tue, 23 Jun 2026 12:47:23 +0000

Bugs Fixed:

Resolved divide by zero bug in tables feature set

IBM DB2 for LUW (remote monitoring) 3.0.1

Mon, 22 Jun 2026 14:24:03 +0000

Requires Dynatrace version 1.338.0 and EEC (ActiveGate) version 1.318.0

Improvements:

Appropriate timeouts set on all queries aligned with their execution interval to avoid 'overlapping' open queries and connections if their is a DB slowdown

PostgreSQL 3.1.0

Mon, 22 Jun 2026 13:41:45 +0000

Improvements

Queries now run conditionally depending on detected Postgres database version.

⚠️ This version requires ActiveGate version 1.339.0 or higher.

Wiz 1.0.0

Mon, 22 Jun 2026 09:15:23 +0000

What's new:

Initial integration release.

Black Duck 1.2.1

Mon, 22 Jun 2026 09:15:05 +0000

What's new:

Initial integration release.

JFrog 1.0.5

Mon, 22 Jun 2026 09:14:48 +0000

What's new:

Initial integration release.

IBM MQ 4.0.4

Fri, 19 Jun 2026 14:59:55 +0000

New in this version

TLS verification toggle on Dynatrace API calls for self-signed certificates.

Fixed in this version

SYSTEM.AUTH.DATA.QUEUE is removed from resultset when Bulk mode is off since it is a protected queue.
Issue where queues were not returned in Gateway mode in certain conditions.
Issue with Auto-defined cluster-sender channels not displaying.

MongoDB Atlas 4.1.1

Thu, 18 Jun 2026 06:07:23 +0000

Fix and improve existing unified analysis screens
Update Smartscape node names

Cloudflare (extension) 2.0.1

Wed, 17 Jun 2026 17:24:05 +0000

Requires Dynatrace and EEC (ActiveGate) version 1.338.0

Fixes:

Removes a connection diagnostic method from the fastcheck that could cause fastcheck failures in certain scenarios where a proxy is used.

GitHub Advanced Security 1.3.11

Wed, 17 Jun 2026 14:46:33 +0000

Requires Dynatrace and EEC (ActiveGate) version 1.333.0

Fixes:

Fix bug in pagination that would cause second page calls to have an extra slash resulting in 404s

Improvements:

Better surface issues with reporting of security events in the reported statuses

Apigee 5.0.2

Tue, 16 Jun 2026 23:18:24 +0000

Improve existing unified analysis screens

Azure Cloud Monitoring 1.1.8

Tue, 16 Jun 2026 16:19:32 +0000

Version 1.1.8

Added EntityName dimension to IncomingMessages, OutgoingMessages, ServerErrors, and UserErrors metrics for Microsoft.EventHub/namespaces

F5 BIG-IP 3.0.6

Tue, 16 Jun 2026 13:50:10 +0000

Fixed in this version:

Corrected typo in Infrastructure & Operations app for displaying Connections chart group on LTM Profile entities.

Cisco ACI/APIC 2.0.4

Tue, 16 Jun 2026 11:54:43 +0000

⚠️ WARNING ⚠️️: Possible breaking changes and warnings — PLEASE READ before upgrading

This version requires a minimum Dynatrace version of 1.338.0 and a minimum EEC version of 1.333.0.
This version includes a possible breaking change for Dynatrace on Grail.
- With the inclusion of OpenPipeline processing rules, any metrics ingested from the extension will be processed by a dedicated OpenPipeline pipeline instead of the default pipeline.
- This means that any custom dynamic rules you created will no longer apply to metrics from this extension. To keep enforcing them, please create pipeline groups.
- Additionally, some field names are handled differently in OpenPipeline (e.g. capitalization). Please double-check any custom dashboards and alerts you created for this extension.
- You must opt-in to OpenPipeline configuration via Settings API — see the documentation.
The apic dimension/property is deprecated and will be discontinued in a future release. Note that this dimension doesn't identify an APIC controller — its value reflects the monitored fabric infrastructure name as defined in the extension's monitoring configuration (the configuration name). The new fabric_name property carries that exact value under an accurate name. apic is still reported for backward compatibility. Please base any custom dashboards, notebooks, alerts, and DQL queries on fabric_name instead of apic.
The following fault log event properties have been renamed for consistency. Both old and new names are present in this release. The old names will be removed in the next release — update your DQL queries and log processing rules to use the new names.

| Old name | New name | |---|---| | code | fault_code | | cause | fault_cause | | severity | fault_severity | | type | fault_type | | lifecycle | fault_lc |

This applies to both fault_info and fault_record log event types (filtered by cisco_aci_event_type).

New in this version

Smartscape on Grail. This extension will populate new Smartscape nodes and edges via OpenPipeline extraction.
Added vendor, software_revision, and serial_number properties to fabric node discovery log events, surfaced as entity attributes on cisco_aci:fabric_node.
Added if_name property to management interface discovery log events.
New fabric_name dimension/property identifying the monitored ACI fabric (one per monitoring configuration). It is present on all metrics and log events, on the classic cisco_aci:* entities, and on the Smartscape nodes. It carries the same value as the existing apic dimension.
Report fault records without matching fault instance (expert config): when enabled, fault records (faultRecord) are reported even when no matching fault instance (faultInst or faultDelegate) is reported. Default: disabled. Useful when fault instances are filtered out due to APIC security domain restrictions (e.g. Report Fault Instance Only combined with an APIC user that only sees faultDelegate entries).
Primary tags and Primary fields (monitoring configuration): two new optional sections on the APIC endpoint, planned for an upcoming release.

Improved in this version

Extension runtime upgraded to Python 3.14. Requires ActiveGate or OneAgent EEC version 1.333 or later (released March 2026).
Gen3 dashboards no longer contain navigation links to Gen2 entity screens.
Feature sets now include recommended flags to guide installation defaults.
Fault collection now uses a two-window approach: full Max age of Fault Infos and Fault Records window on first cycle to warm the cache, then a shorter Fault subsequent collection window (hours) + collection frequency window on subsequent cycles to reduce APIC API load.
Fixed faultInst deduplication: fault_info log records are now re-reported only when the fault's lc (lifecycle), severity, or cause properties actually change. Previously, APIC's ~5-minute heartbeat on lastTransition caused the same fault to be re-reported ~288 times/day. The occur (occurrence count) change is intentionally not considered a re-report trigger as it represents the same periodic re-evaluation, not a meaningful state change.

VMware (remote monitoring) 4.1.1

Mon, 15 Jun 2026 18:06:40 +0000

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

This version requires a minimum Dynatrace version of 1.338.0
This version includes a breaking change for Dynatrace on Grail.
- With the inclusion of OpenPipeline processing rules, any logs ingested from the extension will be processed by a dedicated OpenPipeline pipeline instead of the classic log pipeline.
- 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 OpenPipeline rules.
- Additionally, some field names are handled differently in OpenPipeline, e.g. capitalization. Please double-check any custom dashboards and alerts you have created for this extension.
- You must opt-in to OpenPipeline configuration via Settings API – see the documentation.

New in version 4.1.1:

Added support for Smartscape on Grail
Added feature set metadata for recommended metrics
Better handling of different metric ids in vCenter
Convert IPv6to4 Addresses from IPv6 to IPv4
Inject related VM information to Host in Infrastructure & Operations App
Update column names for VM table in the I&O App
Better handling of invisible characters in Datastore names
Updates to SAME_AS relationship creation between VMs & OneAgent Hosts
Better mapping of ingested logs to their respective entities

Remote Unix Monitoring 2.0 3.0.7

Mon, 15 Jun 2026 16:00:55 +0000

Fixed in this vesion:

Pinned dependency to restore ability to connect with legacy key-exchange methods:
- diffie-hellman-group-exchange-sha1
- diffie-hellman-group14-sha1
- diffie-hellman-group1-sha1

Improved in this version:

Add id_classic field to REMOTE_UNIX_HOST_GROUP and REMOTE_UNIX_HOST Smartscape nodes.

RabbitMQ (Management API) 3.0.0

Mon, 15 Jun 2026 15:08:17 +0000

Version 3.0.0

Adds Smartscape on Grail support.

This version introduces Smartscape on Grail support, with the following nodes and edges:

RABBITMQ_CLUSTER (was rabbitmq:cluster in the classic topology)
RABBITMQ_NODE (was rabbitmq:node in the classic topology)
- runs_on RABBITMQ_CLUSTER
RABBITMQ_VHOST (was rabbitmq:vhost in the classic topology)
- runs_on RABBITMQ_CLUSTER
RABBITMQ_QUEUE (was rabbitmq:queue in the classic topology)
- runs_on RABBITMQ_NODE
- belongs_to RABBITMQ_VHOST

Notes

This feature is only relevant to SAAS customers.
This version requires a minimum Dynatrace version of 1.340 and a minimum ActiveGate/OneAgent version of 1.338.
You must have migrated OpenPipeline configurations to the Settings API, the extension can't be installed otherwise.
The existing classic entities still exist and are supported.