Meraki extension
- Latest Dynatrace
- Extension
Monitor Cisco Meraki network devices, topology, and uplink performance with metrics ingested via the Meraki Dashboard API.
Get started
Overview
This extension uses Meraki Dashboard APIs to fetch device topology, metadata, and metrics. For details, see the Meraki Dashboard API Python library.
Use cases
-
Monitor availability of Meraki network devices.
-
Access organization, network, and device metadata.
-
Collect network data without polling individual devices.
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 the 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 availabilities: get-organization-devices-availabilities
- Device uptime (recently restarted only): get-organization-devices-boots-history
- Device memory usage: get-organization-devices-system-memory-usage-history-by-interval/
- MS device switchport clients: get-organization-switch-ports-clients-overview-by-device/
- MS device switchport status: get-organization-switch-ports-statuses-by-switch
- MS device switchport usage: get-organization-switch-ports-usage-history-by-device-by-interval
- MX device uplink status: get-organization-uplinks-statuses
- 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/
- Power supply status: get-organization-devices-power-modules-statuses-by-device
- CG device uplink status: get-organization-cellular-gateway-uplink-statuses
- VPN status: get-organization-appliance-vpn-statuses
- VPN stats: get-organization-appliance-vpn-stats
- MR device channel utilization: get-network-network-health-channel-utilization
Licensing and costs
There is no charge to use the extension. You are only charged for the data that the extension ingests.
The Meraki extension ingests custom metrics, which consume Davis Data Units (DDUs) (Dynatrace classic license) or Metrics powered by Grail (DPS), according to your license model.
The following formula provides the approximate annual data points ingested, assuming all feature sets are enabled. Actual ingested metric data point volumes depend heavily on your specific Meraki environment.
((18 * # of MS devices)+ (8 * # of MS switchports)+ (20 * # of MX devices)+ (8 * # of MX uplinks)+ (3 * # of CG devices)+ (3 * # of CG uplinks)+ (15 * # of appliance VPNs)+ (7 * # of MR devices)+ (1 * # of power modules)+ (4 (self-monitoring)))* 60 minutes * 24 hours * 365 days data points per year
Dynatrace Platform Subscription
In the Dynatrace Platform Subscription, metric ingestion consumes Metrics powered by Grail according to the number of ingested metric data points.
For logs, regular consumption for Log Analytics applies. For details, see Log Analytics overview (DPS).
Dynatrace classic license
In the classic licensing model, metric ingestion consumes Davis Data Units (DDUs) at the rate of .001 DDUs per metric data point. Multiply the above formula for annual data points by .001 to estimate annual DDU usage.
For logs, regular DDU consumption for log monitoring applies. For details, see DDU consumption for Log Management and Analytics.
Connect Meraki webhooks to Smartscape nodes
To connect webhook payloads from Meraki to Smartscape 2.0 nodes, create a dynamic route in OpenPipeline that routes the entry to the Meraki extension's log pipeline.
-
Navigate to the Settings app in the tenant.
-
Go to the Process and contextualize section.
-
Select the OpenPipeline entry from the list.
-
Select the Logs entry from the list.
-
Select the Dynamic routing header.
-
Select Dynamic route to create a new dynamic route.
-
Name the dynamic route.
-
Enter the following matcher into the Matcher section of the dynamic route:
isNotNull(organizationId) andisNotNull(networkId) andisNotNull(deviceSerial) andisNotNull(deviceName) andisNotNull(deviceMac) -
Select Meraki as the pipeline.
-
Save the dynamic route.
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.
switchport-clients
| Metric name | Metric key | Description |
|---|---|---|
| Meraki SwitchPort Clients | meraki.switchport.clients | The number of clients for all switchports with at least one online client |
device-cpu
| Metric name | Metric key | Description |
|---|---|---|
| Meraki Appliance CPU Usage | meraki.device.cpu_usage | CPU Usage collected for the top MX devices |
self-monitoring
| 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 |
device-uptime
| 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 |
device-memory
| 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 |
default
| 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 | — |
device-status
| Metric name | Metric key | Description |
|---|---|---|
| Meraki Device Status | meraki.device.status | Current status of the Meraki Device: online, alerting, offline or dormant |
device-powersupply
| 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 |
device-uplink
| 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) |
device-uplink-usage
| 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 |
