Meraki extension
- Latest Dynatrace
- Extension
- Published Oct 27, 2025
Monitor your network devices and topology information through the Meraki API.
Monitor Meraki network devices and topology to ensure visibility and performance across sites.
Get started
Overview
This extension uses Meraki Dashboard APIs to fetch device topology, metadata and metrics.
Use cases
-
Monitor availability of Meraki network devices.
-
Access organization, network, and device metadata.
-
Collect network data without polling individual devices.
Compatibility information
This extension makes use of the Meraki Dashboard API Python Library: meraki.
Activation and setup
Activate the extension in your environment using the in-product Hub. Provide the required configuration settings such as the Meraki API token, for details on Meraki API, see:
Details
This extension calls the following Dashboard Organization APIs:
- Topology and metadata for Organizations, Networks and Devices.
- Organizations: get-organizations
- Networks: get-organization-networks
- Devices: get-organization-devices
- Metrics
- Device and Power supply status: get-organization-devices-statuses
- Device Uptime (recently restarted only) get-organization-devices-boots-history
- Device Memory Usage get-organization-devices-system-memory-usage-history-by-interval/
- MS Device get-organization-switch-ports-clients-overview-by-device/
- MX Device Uplink loss and latency: get-organization-devices-uplinks-loss-and-latency
- MX Device and Z Device Uplink usage: get-organization-appliance-uplinks-usage-by-network/
- MX Device CPU Usage get-organization-summary-top-appliances-by-utilization/
The extension also collects and reports generic network metrics as per: Generic Network Topology. This means that Meraki devices and data are available in the Network tab of the Infrastructure and Operations App.
Feature sets
When activating your extension using monitoring configuration, you can limit monitoring to one of the feature sets. To work properly the extension has to collect at least one metric after the activation.
In highly segmented networks, feature sets can reflect the segments of your environment. Then, when you create a monitoring configuration, you can select a feature set and a corresponding ActiveGate group that can connect to this particular segment.
All metrics that aren't categorized into any feature set are considered to be the default and are always reported.
A metric inherits the feature set of a subgroup, which in turn inherits the feature set of a group. Also, the feature set defined on the metric level overrides the feature set defined on the subgroup level, which in turn overrides the feature set defined on the group level.
| Metric name | Metric key | Description |
|---|---|---|
| Meraki Device Memory Used | meraki.device.memory_used | Meraki Device Memory Used kB |
| Meraki Device Memory Free | meraki.device.memory_free | Meraki Device Memory Free kB |
| Meraki Device Memory Total | meraki.device.memory_total | Meraki Total Device Memory Provisioned kB |
| Meraki Device Memory Usage | meraki.device.memory_usage | Meraki Device Memory Usage Percent |
| Metric name | Metric key | Description |
|---|---|---|
| — | com.dynatrace.extension.network_device.sysuptime | — |
| — | com.dynatrace.extension.network_device.cpu_usage | — |
| — | com.dynatrace.extension.network_device.cpu_ratio | — |
| — | com.dynatrace.extension.network_device.memory_used | — |
| — | com.dynatrace.extension.network_device.memory_free | — |
| — | com.dynatrace.extension.network_device.memory_total | — |
| — | com.dynatrace.extension.network_device.memory_usage | — |
| — | com.dynatrace.extension.network_device.if.bytes_in.count | — |
| — | com.dynatrace.extension.network_device.if.bytes_out.count | — |
| Metric name | Metric key | Description |
|---|---|---|
| Meraki Device Status | meraki.device.status | Current status of the Meraki Device: online, alerting, offline or dormant |
| Metric name | Metric key | Description |
|---|---|---|
| Meraki Device Power Supply Status | meraki.powersupply.status | Current status of the Meraki Device Power Supply: available, connected, disconnected, powered, powering or standby |
| Metric name | Metric key | Description |
|---|---|---|
| Meraki Uplink Loss Percent | meraki.uplink.lossPercent | Meraki MX Device uplink loss percentage |
| Meraki Uplink Latency | meraki.uplink.latencyMs | Meraki MX Device uplink latency (milliseconds) |
| Metric name | Metric key | Description |
|---|---|---|
| Meraki Uplink Sent Bytes | meraki.uplink.sent.count | Meraki MX Device uplink bytes sent |
| Meraki Uplink Received Bytes | meraki.uplink.received.count | Meraki MX Device uplink bytes received |
| Metric name | Metric key | Description |
|---|---|---|
| Meraki SwitchPort Clients | meraki.switchport.clients | The number of clients for all switchports with at least one online client |
| Metric name | Metric key | Description |
|---|---|---|
| Meraki Appliance CPU Usage | meraki.device.cpu_usage | CPU Usage collected for the top MX devices |
| Metric name | Metric key | Description |
|---|---|---|
| Meraki API Connectivity | meraki.api.connectivity | Was Dynatrace able to poll the Meraki API without errors? |
| Meraki Monitored Organizations | meraki.monitoring.organizations | The number of organizations that Dynatrace is monitoring through Meraki |
| Meraki Monitored Networks | meraki.monitoring.networks | The number of networks that Dynatrace is monitoring through Meraki |
| Meraki Monitored Devices | meraki.monitoring.devices | The number of devices that Dynatrace is monitoring through Meraki |
| Metric name | Metric key | Description |
|---|---|---|
| Meraki Device Uptime (seconds) | meraki.device.uptime | Time since the last device boot - MS devices only. Note: this only tracks recently rebooted device uptimes (within 1 day) due to Meraki API limitations |
