Skip to technology filters Skip to main content
Dynatrace Hub

Extend the platform,
empower your team.

Popular searches:
Home hero bg
Cisco Catalyst Center (DNA Center)Cisco Catalyst Center (DNA Center)
Cisco Catalyst Center (DNA Center)

Cisco Catalyst Center (DNA Center)

Get insights into the Cisco Catalyst Center infrastructure (f.k.a. DNA Center).

Extension
Free trialDocumentation
Cisco Catalyst Center dashboardDevice characterization by Cisco Catalyst CenterCisco Catalyst Center inventory in Infrastructure and Operations appMetric timeseries retrieved from the Cisco Catalyst CenterCisco Catalyst Center sites in Classic viewCisco Catalyst Center site and site devicesCisco Catalyst Center device properties
  • Product information
  • Release notes

Overview

Cisco Catalyst extension uses Cisco Catalyst API to collect information about network managed by Cisco Catalyst Center.

The extension provides insight into configuration, location and health status of devices and their interfaces.

Analysis screens present data hierarchically, helping to quickly diagnose issues by site, role or by device platform.

Extension collects performance and health metrics as well as Cisco Catalyst issues/events. Basic statistics of client devices are also available.

This extension is intended for users, who:

  • Use Dynatrace for infrastructure monitoring
  • Run Cisco Catalyst Center in their environment (Catalyst Center is formerly known as Cisco DNA)
  • Look to extend Dynatrace insights into the Cisco Catalyst platform

Use cases

  • Integrated operational monitoring of the infrastructure, including Cisco Catalyst and leveraging additional organization, network and device metadata.
  • Root cause analysis of network issues, in the light of the entire application and infrastructure landscape observed by Dynatrace.
  • Network infrastructure data collection without having to poll individual devices.

Get started

For more information on the installation and configuration, please see Cisco Catalyst Center (DNA Center) extension in the Dynatrace Documentation.

Details

Compatibility information

  • Network access from a Dynatrace ActiveGate to the Cisco Catalyst Center
  • Cisco Catalyst Center (DNA) version 2.3.7.6+
    • See Q&A section for more information on API compatibility
Dynatrace
Documentation
By Dynatrace
Dynatrace support center
Subscribe to new releases
Copy to clipboard

Feature sets

Below is a complete list of the feature sets provided in this version. To ensure a good fit for your needs, individual feature sets can be activated and deactivated by your administrator during configuration.

Feature setsNumber of metrics included
Metric nameMetric keyDescriptionUnit
Wired Clients Scorecisco.cc.site.client_health_wiredSite's Wired Clients Health ScorePercent
Wireless Clients Scorecisco.cc.site.client_health_wirelessSite's Wireless Clients Health ScorePercent
Clientscisco.cc.site.client_count.gaugeSite's Clients Summary CountCount
Wired Clientscisco.cc.site.wired_client_count.gaugeSite's Wired Clients Summary CountCount
Wireless Clientscisco.cc.site.wireless_client_count.gaugeSite's Wireless Clients Summary CountCount
Healthy Clientscisco.cc.site.client_good_health_percentageSite's Healthy Clients Summary PercentagePercent
Devicescisco.cc.site.network_device_count.gaugeSite's Devices Summary CountCount
Healthy Devicescisco.cc.site.network_device_good_health_percentageSite's Healthy Devices Summary PercentagePercent
Site Issuescisco.cc.site.issue_count.gaugePending Site IssuesCount
Metric nameMetric keyDescriptionUnit
Device Count Query Durationsfm.cisco.cc.get_devices_by_query_count.durationDuration of the get_devices_by_query_count API call used to determine total device count before paginated collection.Seconds
Device Count Query Errorssfm.cisco.cc.get_devices_by_query_count.errorNumber of errors during get_devices_by_query_count API call.Count
Device Query Page Durationsfm.cisco.cc.get_devices_by_query.durationDuration of a single paginated get_devices_by_query API call used to collect device data.Seconds
Device Query Page Errorssfm.cisco.cc.get_devices_by_query.errorNumber of errors during a paginated get_devices_by_query API call.Count
Device Discovery Count Query Durationsfm.cisco.cc.get_network_devices_count_by_params.durationDuration of the get_network_devices_count_by_params API call used to determine device count during BASIC discovery.Seconds
Device Discovery Count Query Errorssfm.cisco.cc.get_network_devices_count_by_params.errorNumber of errors during get_network_devices_count_by_params API call.Count
Device Discovery Query Page Durationsfm.cisco.cc.get_network_devices_by_params.durationDuration of a single paginated get_network_devices_by_params API call used for BASIC device discovery.Seconds
Device Discovery Query Page Errorssfm.cisco.cc.get_network_devices_by_params.errorNumber of errors during a paginated get_network_devices_by_params API call.Count
Physical Topology Query Durationsfm.cisco.cc.get_physical_topology.durationDuration of the get_physical_topology API call used to collect physical network topology data.Seconds
Physical Topology Query Errorssfm.cisco.cc.get_physical_topology.errorNumber of errors during get_physical_topology API call.Count
Site Count Query Durationsfm.cisco.cc.get_sites_count.durationDuration of the get_sites_count API call used to determine total site count before paginated collection.Seconds
Site Count Query Errorssfm.cisco.cc.get_sites_count.errorNumber of errors during get_sites_count API call.Count
Site Query Page Durationsfm.cisco.cc.get_sites.durationDuration of a single paginated get_sites API call used to collect site data.Seconds
Site Query Page Errorssfm.cisco.cc.get_sites.errorNumber of errors during a paginated get_sites API call.Count
Site Topology Query Durationsfm.cisco.cc.get_sites_topology.durationDuration of the get_sites_topology API call used to collect site hierarchy topology.Seconds
Site Topology Query Errorssfm.cisco.cc.get_sites_topology.errorNumber of errors during get_sites_topology API call.Count
Interface Count Query Durationsfm.cisco.cc.get_interfaces_by_query_count.durationDuration of the get_interfaces_by_query_count API call used to determine total interface count before paginated collection.Seconds
Interface Count Query Errorssfm.cisco.cc.get_interfaces_by_query_count.errorNumber of errors during get_interfaces_by_query_count API call.Count
Interface Query Page Durationsfm.cisco.cc.get_interfaces_by_query.durationDuration of a single paginated get_interfaces_by_query API call used to collect interface data.Seconds
Interface Query Page Errorssfm.cisco.cc.get_interfaces_by_query.errorNumber of errors during a paginated get_interfaces_by_query API call.Count
Interface Discovery Count Query Durationsfm.cisco.cc.get_intent_api_interfaces_count.durationDuration of the get_intent_api_interfaces_count API call used to determine interface count during Intent API discovery.Seconds
Interface Discovery Count Query Errorssfm.cisco.cc.get_intent_api_interfaces_count.errorNumber of errors during get_intent_api_interfaces_count API call.Count
Interface Discovery Query Page Durationsfm.cisco.cc.get_intent_api_interfaces.durationDuration of a single paginated get_intent_api_interfaces API call used for Intent API interface discovery.Seconds
Interface Discovery Query Page Errorssfm.cisco.cc.get_intent_api_interfaces.errorNumber of errors during a paginated get_intent_api_interfaces API call.Count
Network Health Query Durationsfm.cisco.cc.get_network_health.durationDuration of the get_network_health API call used to collect overall network health scores.Seconds
Network Health Query Errorssfm.cisco.cc.get_network_health.errorNumber of errors during get_network_health API call.Count
Client Health Query Durationsfm.cisco.cc.get_client_health.durationDuration of the get_client_health API call used to collect client health scores.Seconds
Client Health Query Errorssfm.cisco.cc.get_client_health.errorNumber of errors during get_client_health API call.Count
Site Health Summaries Query Durationsfm.cisco.cc.get_site_health_summaries.durationDuration of the get_site_health_summaries API call used to collect site-level health summary data.Seconds
Site Health Summaries Query Errorssfm.cisco.cc.get_site_health_summaries.errorNumber of errors during get_site_health_summaries API call.Count
Issues Query Durationsfm.cisco.cc.issues.durationDuration of the issues API call used to collect Catalyst Center issues data.Seconds
Issues Query Errorssfm.cisco.cc.issues.errorNumber of errors during issues API call.Count
Event Notifications Query Durationsfm.cisco.cc.events.durationDuration of the events API call used to collect Catalyst Center event notifications data.Seconds
Event Notifications Query Errorssfm.cisco.cc.events.errorNumber of errors during events API call.Count
Group Records Fetchedsfm.cisco.cc.group.records_fetched.gaugeTotal number of raw device or interface records fetched from the API for this reporting configuration group.Count
Group Entities Reportedsfm.cisco.cc.group.entities_reported.gaugeNumber of entities (devices or interfaces) reported to Dynatrace for this reporting configuration group.Count
Group Overlap Devicessfm.cisco.cc.group.overlap_devices.gaugeNumber of devices matching this group filter that are reported by a different reporting configuration. Only emitted when OVERLAP strategy is active and overlap count is greater than zero.Count
Metric nameMetric keyDescriptionUnit
-com.dynatrace.extension.network_device.cpu_usage--
-com.dynatrace.extension.network_device.memory_usage--
-com.dynatrace.extension.network_device.sysuptime--
-com.dynatrace.extension.network_device.memory_total--
-com.dynatrace.extension.network_device.if.status--
-com.dynatrace.extension.network_device.if.bytes_in.count--
-com.dynatrace.extension.network_device.if.bytes_out.count--
Metric nameMetric keyDescriptionUnit
Interface Countcisco.cc.device.total_interface_count.gaugeTotal Number of Interfaces for DeviceCount
Admin Statuscisco.cc.interface.admin_statusInterface's Admin Status (1: UP | 0: DOWN)State
Oper Statuscisco.cc.interface.oper_statusInterface's Status (1: UP | 0: DOWN)State
Speedcisco.cc.interface.speed-BitPerSecond
TX Ratecisco.cc.interface.txRate-BitPerSecond
TX Utilizationcisco.cc.interface.txUtilization-Percent
TX Discardscisco.cc.interface.txDiscards-Percent
TX Errorscisco.cc.interface.txError-Percent
RX Ratecisco.cc.interface.rxRate-BitPerSecond
RX Utilizationcisco.cc.interface.rxUtilization-Percent
RX Discardscisco.cc.interface.rxDiscards-Percent
RX Errorscisco.cc.interface.rxError-Percent
Metric nameMetric keyDescriptionUnit
Healthcisco.cc.device.healthDevice's HealthState
CPUcisco.cc.device.cpuDevice's CPU consumptionPercent
Memorycisco.cc.device.memoryDevice's Memory consumptionPercent
Average Temperaturecisco.cc.device.temperatureDevice's Avg TemperatureCelsius
Device Issuescisco.cc.device.issue_count.gaugePending Device IssuesCount
Reachabilitycisco.cc.device.reachabilityDevice's Reachability (1: Reachable | 0: Not Reachable)Count
Uptimecisco.cc.device.uptime.gaugeDevice Uptime in SecondsSecond
Issue Eventscisco.cc.device.issue_events.gaugeIssue events over selected timeframeCount
Metric nameMetric keyDescriptionUnit
Health score (Center)cisco.cc.center.health_scoreCisco Catalyst Network topology - Overall health scorePercent
Healthy devicescisco.cc.center.healthy_devicesCisco Catalyst Network topology - Healthy devicesCount
Unhealthy devicescisco.cc.center.unhealthy_devicesCisco Catalyst Network topology - Unhealthy devicesCount
Clients health scorecisco.cc.client.health_scoreCisco Catalyst Client - Overall client health scorePercent
Clients Countcisco.cc.client.client_count.gaugeCisco Catalyst Client - Clients countCount
Unique Clients Countcisco.cc.client.client_unique_count.gaugeCisco Catalyst Client - Unique Clients CountCount
Clients health score countcisco.cc.client.health_score_count.gaugeCisco Catalyst Client - Clients health score by score typeCount
Catalyst Center Notification Countcisco.cc.center.notification_count.gaugeNumber of Cisco Catalyst Center event notifications reported per collection intervalCount

Related to Cisco Catalyst Center (DNA Center)

Generic Cisco Device logo

Generic Cisco Device

Monitor Cisco devices using SNMP to feed Dynatrace with metrics and alerts.

Generic network device logo

Generic network device

Gain insights into the performance of your network devices.

SNMP Autodiscovery logo

SNMP Autodiscovery

Scan through your subnets and build an inventory of SNMP-enabled network devices.

Full version history

To have more information on how to install the downloaded package, please follow the instructions on this page.
ReleaseDate

Full version history

⚠️ 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.

Full version history

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.

Full version history

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

Full version history

Improved in this version

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

Full version history

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.

Full version history

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

Full version history

⚠️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.

Full version history

Patch level changes

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

Full version history

⚠️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.

Full version history

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.

Dynatrace Hub
Get data into DynatraceBuild your own app
Dynatrace Intelligence - Agentic Operations SystemThe Dynatrace Agentic AI ecosystem
All (915)Log Management and AnalyticsKubernetesAI and LLM ObservabilityInfrastructure ObservabilitySoftware DeliveryApplication ObservabilityApplication SecurityBusiness ObservabilityDigital Experience
Filter
Type
Built and maintained by
Deployment model
SaaS
  • SaaS
  • Managed
Partner FinderBecome a partnerDynatrace Developer

Discover recent additions to Dynatrace

Dynatrace Assist logo

Dynatrace Assist

Dynatrace Assist: Ask, analyze, and act with Dynatrace Intelligence.

Smartscape logo

Smartscape

Interactively explore and analyze topology and relationships in digital systems.

Compliance Assistant logo

Compliance Assistant

Track, manage, and automate compliance across your IT and business landscape.

Experience Vitals logo

Experience Vitals

Optimize UX with core vitals, frontend error tracking, and end-to-end visibility.

Error Inspector logo

Error Inspector

Discover, triage, and manage errors across all your frontends.

Users & Sessions logo

Users & Sessions

Discover how users and cohorts with common characteristics experience your app.

Analyze your data

Understand your data better with deep insights and clear visualizations.

Notebooks logo

Notebooks

Create powerful, data-driven documents for custom analytics and collaboration.

Dashboards logo

Dashboards

Transform complex data into clear visualizations with custom dashboards.

Investigations logo

Investigations

Fast and precise incident response on Grail data with DQL queries.

Smartscape logo

Smartscape

Interactively explore and analyze topology and relationships in digital systems.

Logs logo

Logs

Explore all your logs without writing a single query.

Problems logo

Problems

Detect, explain and triage problems automatically using Dynatrace Intelligence.

Automate your processes

Turn data and answers into actions, securely, and at scale.

Workflows logo

Workflows

Automate tasks in your IT landscape and move towards autonomous operations.

Jira logo

Jira

Open, update, and close Jira tickets automatically from Dynatrace Workflows.

Slack logo

Slack

Automate Slack messaging for security incidents, attacks, remediation, and more.

Secure your cloud application

See vulnerabilities and attacks in your environment.

Security Posture Management logo

Security Posture Management

Detect, prioritize, and remediate security and compliance findings with SPM.

Threats & Exploits logo

Threats & Exploits

Understand, triage, and investigate detection findings and alerts.

More resources

Observability for Developers on Cursor logo

Observability for Developers on Cursor

Get Real time Code-Level data directly to your Cursor IDE.

Documents logo

Documents

Manage Dashboards, Notebooks and other documents in your Dynatrace environment.

GitHub Copilot Coding Agent logo

GitHub Copilot Coding Agent

Automate vulnerability remediation and boost developer productivity.

GitHub Copilot Custom Agent logo

GitHub Copilot Custom Agent

Automate your development workflows with specialized agent definitions.

Observability for Developer on JetBrains logo

Observability for Developer on JetBrains

Get real-time code-level data directly to your Jetbrains IDE.

Metrics logo

Metrics

Browse, search, and manage all your metrics in one central catalog.

Pagerduty for Dynatrace Workflows logo

Pagerduty for Dynatrace Workflows

Streamline incident management with automated Pageruty workflows.

Cursor IDE logo

Cursor IDE

Boost developer productivity and get real-time, code-level insights into Cursor.

Observability for Developers on Windsurf logo

Observability for Developers on Windsurf

Get real-time code-level data directly to your Windsurf IDE.

Are you looking for something different?

We have hundreds of apps, extensions, and other technologies to customize your environment

Leverage our newest innovations of Dynatrace Saas

Kick-start your app creation

Kick-start your app creation

Whether you’re a beginner or a pro, Dynatrace Developer has the tools and support you need to create incredible apps with minimal effort.
Go to Dynatrace Developer
Upgrading from Dynatrace Managed to SaaS

Upgrading from Dynatrace Managed to SaaS

Drive innovation, speed, and agility in your organization by seamlessly and securely upgrading.
Learn More
Log Management and Analytics

Log Management and Analytics

Innovate faster and more efficiently with unified log management and log analytics for actionable insights and automation.
Learn more