Dynatrace Hub - Cisco ACI/APIC latest releases

Cisco ACI/APIC 2.0.5

Fri, 21 Aug 2026 10:57:03 +0000

Fixed in this version

Fixed broken classic topology when monitoring more than one ACI environment: some entities (such as controllers and spines) were incorrectly merged or linked across fabrics. Each entity now stays within its own fabric.
Fixed the fabric filter on the currently monitoring count tiles of the Cisco ACI Fabric Overview and Cisco ACI Tenants Overview dashboards. Selecting a fabric now rescopes those counts to the selected fabric — previously they always showed the totals across all monitored fabrics, while the charts and tables on the same dashboards were filtered correctly.

Note: the fault log event properties renamed in 2.0.4 are still reported under both their old and new names. The old names — lifecycle, severity, type, cause, code — remain deprecated in favor of fault_lc, fault_severity, fault_type, fault_cause and fault_code. They will be kept until a future minor release, not removed in a bugfix release.

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.

Cisco ACI/APIC 1.2.0

Wed, 06 May 2026 10:44:36 +0000

Added

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).

Changed

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

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.

Deprecated

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).

Cisco ACI/APIC 1.1.5

Fri, 06 Mar 2026 09:56:13 +0000

Improved in this version

Improved entity topology handling in very large environments

Cisco ACI/APIC 1.1.3

Thu, 15 Jan 2026 15:33:51 +0000

Improved in this version

Fixed display issues with the single-value metric visualization in the Infrastructure & Operations application.

Cisco ACI/APIC 1.1.1

Fri, 17 Oct 2025 18:21:49 +0000

Patch level changes

Resolved an issue where the com.dynatrace.extension.network_device.sysuptime metric was calculated incorrectly.

Cisco ACI/APIC 1.1.0

Thu, 02 Oct 2025 12:02:45 +0000

This is the first generally available release of this extension.

Note to the early adopters of the pre-release version: monitoring configuration needs to be re-created from scratch, it won't upgrade. However, if you keep the same configuration name, your previously collected metrics will remain available.