Dynatrace Hub - Cisco Catalyst Center (DNA Center) latest releases

Cisco Catalyst Center (DNA Center) 3.1.0

Wed, 19 Aug 2026 11:41:07 +0000

New in this version

Added site hierarchy fields — cisco_cc.area, cisco_cc.building, cisco_cc.floor and cisco_cc.level_01_name through cisco_cc.level_04_name — to both the device and interface discovery log events. The EXT_NETWORK_DEVICE and EXT_NETWORK_INTERFACE Smartscape node attributes are extracted from those log fields by the logs OpenPipeline.
The start time of a reported Dynatrace event is now the timestamp when the issue data was first read from the Catalyst Center API. The Catalyst Center issue timestamp previously used for it is now reported as an event attribute instead.
To prevent one continuous Catalyst Center issue from creating repeated Dynatrace problems under some circumstances, events for active issues are now re-sent more frequently — every half of the new dt_event_timeout_minutes expert configuration property (default: 60, maximum: 360), capped by DT Event Refire Interval, which is every 30 minutes with the defaults. More events are ingested for long-running issues; existing configurations need no changes.

Fixed in this version

Interface description (alias) is now reported.
Devices excluded by the reporting configuration filters are no longer reported in log events, so they no longer appear as monitored entities.
Device reachability is now derived from the device communication state.

Cisco Catalyst Center (DNA Center) 3.0.3

Tue, 09 Jun 2026 13:47:17 +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.
This new extension configuration is incompatible with prior 1.x / 2.x versions.
- Action required: you must recreate all monitoring configurations.
cisco.cc.center.cc_events metric has been renamed to cisco.cc.center.notification_count.gauge. Historical data ingested under the old key is not retroactively renamed. Charts will show a data gap until new data arrives under the new key. The metric is a gauge reporting the notification count from the most recent collection interval; built-in pie chart DQL queries use arrayLast to visualize the actual last reported state. Limited impact: this metric is only collected when report_notifications: true is set (default: false); only explicitly opted-in configurations are affected.
- Action required: any metric alerts you created on cisco.cc.center.cc_events must be manually updated to reference cisco.cc.center.notification_count.gauge.
cisco.cc.device.memory_size.gauge and com.dynatrace.extension.network_device.memory_total metrics are no longer reported. No reliable API source is available for total device memory. Use cisco.cc.device.memory / com.dynatrace.extension.network_device.memory_usage instead. Memory Size chart tiles have been removed from device screens accordingly.
cisco.cc.device.cpu and cisco.cc.device.memory are suppressed by default when both the default and device feature sets are active (same values as com.dynatrace.extension.network_device.cpu_usage / memory_usage). To restore both namespaces, set enable_legacy_cisco_cc_metrics: true in the expert configuration.

New in this version

Smartscape on Grail. This extension will populate new Smartscape nodes and edges via OpenPipeline extraction.
Added 3 new device reporting strategies: Simple, Exclusive Groups, and Flexible Groups, which control how monitored devices are grouped into per-group queries to Catalyst Center. This lets you filter monitored devices, tune and reduce the number of API requests issued to the API endpoints per collection cycle, optimizing request load for environments of any size.
Interfaces without a real MAC address — port-channels, Loopback, Tunnel, and Firepower interfaces — are now reported with cisco.cc.interface.* metrics. Previously (2.x extension version) these interfaces were excluded from all reporting.
Added report_no_mac_interfaces_as_generic expert configuration toggle (default: false). When enabled, such interfaces are additionally reported as generic com.dynatrace.extension.network_device.if.* metrics using a synthetic MAC derived from the interface ID, allowing full monitoring at the cost of increased DPS/DDU.
Added chassis.mac dimension to all cisco.cc.device.* and cisco.cc.interface.* metrics and to device and interface discovery log events.
Added vendor property to device discovery log events (cisco.cc.device_discovery).
Added site_id dimension to interface metrics and interface discovery log events.
Added chassis.mac and site_id as cisco_cc:interface entity attributes.
Added self-monitoring metrics for event notifications data collection (sfm.cisco.cc.events.events.duration, sfm.cisco.cc.events.events.error).
Primary tags and Primary fields (monitoring configuration): two new optional sections on the endpoint configuration make this release ready to support the upcoming global entity tagging functionality.

Improved in this version

Device CPU and memory charts on cisco_cc:device and network:device screens now use com.dynatrace.extension.network_device.* metric keys.
Charts now connect data points across gaps when metrics are collected at longer intervals.
Interface filter configuration now reads "administrative status UP" instead of "UP interfaces", clarifying that it filters on configured (administrative) state.
Vendor enrichment prefers productVendor from the Data API over the Intent API BASIC endpoint; the BASIC value is used only as a fallback when the Data API value is absent.

Fixed in this version

Reported notifications not related to a device or site will no longer create new "ghost" no-named entities.
Device IP address now shows as "Device IP Address" in the metrics explorer. Previously the dimension had no display name.

Cisco Catalyst Center (DNA Center) 2.3.0

Tue, 05 May 2026 09:02:42 +0000

New in this version

Feature sets now show descriptions and recommended flags, making it easier to select the right feature sets during installation.

Improved in this version

Upgraded Python runtime from 3.10 to 3.14. Python 3.10 support ends October 2026; this release targets Python 3.14 as the sole runtime. Requires ActiveGate/OA 1.333 or later.
Fixed device IP address metric dimension and entity property extraction.
Fixed ghost device and site entities created from event notification logs without a device or site scope.

Cisco Catalyst Center (DNA Center) 2.2.1

Thu, 05 Mar 2026 10:17:57 +0000

New features

Ingest Cisco Catalyst Events (CC Events) from Catalyst Center and report them as log records and optionally as Dynatrace events.
- The extension polls Catalyst events from Catalyst Center using the event management API and records each event as a log entry.
- Relationships to the corresponding Catalyst site or device entities are automatically created when this information is available in the event payload.
- Events can optionally be ingested into Dynatrace as Dynatrace Events, based on configurable event-mapping rules.
- A complete catalog of Catalyst event IDs—including event type, category, and severity—is available here: Cisco Catalyst Center Event Catalog

Cisco Catalyst Center (DNA Center) 2.1.5

Thu, 15 Jan 2026 12:38:22 +0000

Improved in this version

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

Cisco Catalyst Center (DNA Center) 2.1.3

Fri, 28 Nov 2025 08:47:33 +0000

Patch level changes

Improved handling of Unicode characters in dimension values - only spaces, letters, numbers, and punctuation characters are retained.
Added a dedicated column for sorting by entity name in the Infrastructure and Operation Application when visualizing Cisco Catalyst Center entities.

Cisco Catalyst Center (DNA Center) 2.1.1

Mon, 29 Sep 2025 21:48:38 +0000

New features:

cc_issue_link attribute added to the log events imported from DNA, allowing for quick jump to the issue as reported by the CNA Center
Several Catalyst entity attributes extracted from logs and added to network device/interface entities properties, including memory_size_text, os_type, os_version, serial_number, uptime_text, reachability status, platform_id, family

Patch level changes

Improved handling of the device-interface relationships to address some DQL entity selection issues
Amended security_context tagging of the generic network entities created by this extensions

Cisco Catalyst Center (DNA Center) 2.1.0

Fri, 12 Sep 2025 09:16:32 +0000

⚠️IMPORTANT CHANGE: This extension release requires Dynatrace cluster version 1.313 or later.

New features

Updated Default Discovery Frequencies: Site and device discovery defaults have been adjusted to 60 and 30 minutes, respectively. More relaxed configuration ranges are now available in the expert settings.
New Gen3 Dashboards: Cisco Catalyst Center Monitoring Overview, Cisco Catalyst Extension Self-Monitoring
Self-Monitoring Metrics Metadata: Added metric metadata for the extension's self-monitoring metrics
If Catalyst issues are reported as Dynatrace events, the events for cisco_cc:device entities are also reported separately (duplicated) for the generic network:device entities

Patch level changes

Topology Fix: Resolved an issue with the topological relationship between Cisco Catalyst Device and generic Network Device entities
The dt.security_context attribute is now propagated to all entities created by the extension.
The DNA Center URL is reported as the device.address dimension for cisco.cc.center., cisco.cc.client., and cisco.cc.site.* metrics
Enhanced Q&A Section: Expanded with troubleshooting guidance tailored for large-scale monitored environments.

Cisco Catalyst Center (DNA Center) 2.0.1

Mon, 28 Jul 2025 08:28:05 +0000

Patch level changes

Fixed Windows ActiveGate deployment issue
Resolved race condition in aggressive site cache cleanup for deployments with thousands of devices

Cisco Catalyst Center (DNA Center) 2.0.0

Thu, 26 Jun 2025 15:12:54 +0000

⚠️Breaking Change

The extension configuration screen has been upgraded to support new features. As a result, a new configuration must be created. To ensure continuity of metric data and preserve existing entities, make sure to use the same Endpoint Name as in the previous configuration.

New features

Ingest issues from Catalyst Center and reporting them either as log messages or as Dynatrace events
Control how often metrics are reported for devices and interfaces based on Catalyst tags
Proxy support added for connections to the Catalyst Center

See hub tile text for more details on how to set up these new features.

Patch level changes

The number of dimensions for device and interface metrics has been reduced. Device and Interface attributes previously reported as metric dimensions are now reported to entities via log ingestion.
Memory optimizations have been made to better support environments with a large number of devices.
Interface metric dimension descriptions have been corrected, and the Device Family dimension is now properly reported.
When an issue is resolved or ignored, it is reported as a log message.

Cisco Catalyst Center (DNA Center) 1.0.0

Thu, 24 Apr 2025 13:57:29 +0000

New features:

This is the first release of the Cisco Catalyst Center extension
We look forward to your feedback on the enhancements that would make this extension better fitted to your environment. Post your Product Idea on Dynatrace community and let others up-vote it!

Note to those who have been running the private preview of the Cisco DNA extension in the past: this Catalyst Center extension supersedes the DNA extension. There is no migration path - please configure Cisco Catalyst Center extension from scratch and use it going forward. Deactivate and remove DNA extension, to conserve compute resources on ActiveGate, on Catalyst Center, and avoid unnecessary license consumption.