Cisco Meraki Monitoring

Last updated on 27 December, 2022

Use the LogicMonitor Cisco Meraki suite to monitor Meraki devices on a per-network level using a hybrid API/SNMP data collection approach. You can monitor API usage and device counts on a per-organization level.


Import the LogicMonitor_Collector_Snippets DataSource and apply it to your monitored collector resource to ensure that your collector supports the code in this monitoring suite, or update to EA Collector 32.100 or later.

API Configurations

You must enable access to the Meraki Dashboard API.

  1. In your Meraki environment, navigate to Organization > Settings > Dashboard API access
  2. Select the Enable access to the Cisco Meraki Dashboard API checkbox.
  3. Navigate to the My Profile page and generate an API key. The API key will be assigned to a property within LogicMonitor. Be sure to copy the API key in a secure location once it is generated.

See Cisco’s Meraki Dashboard API documentation for instructions on enabling the API access and generating an API key.

SNMP Configurations

SNMP v2c or v3 must be enabled on the Meraki Cloud Controller. See Cisco’s SNMP Overview and Configuration documentation for instructions.

Create a Meraki Device Group

From the Resources page, create a Meraki device group and assign it the following properties:

meraki.api.keyMeraki API key (key must be generated and API must be enabled as discussed in previous section)
snmp.versionBecause LogicMonitor is not querying the devices themselves, but rather the Cloud Controller, it is not able to automatically assign the SNMP version to this property as it typically does for other monitoring operations that leverage SNMP. Be sure to manually assign the corresponding SNMP version (either “v2c” or “v3”) to this property. (v2c only) (v3 only)
These values are generated by Meraki and start with “o/”.
Other SNMP credentials
The properties required to establish the remaining SNMP credentials vary depending on the SNMP version being used. For more information, see Defining Authentication Credentials.

For more information on creating device groups, see Adding Device Groups.

Add Resources Into Monitoring

Add your Cisco Meraki hosts into monitoring. You can either use NetScan to automatically add all relevant devices into monitoring (and auto-assign several required device properties), or you can manually add the devices into monitoring.

Adding Resources via NetScan

You can automatically add all Meraki networks, organizations, and a main device via an advanced NetScan. For instructions on creating and running an advanced NetScan, see Creating NetScans.

Ensure the following configurations are in place for the NetScan:

Select Upload a script or csv to discover devices from the Method field’s dropdown menu.

  1. Select Upload a script or csv to discover devices from the Method field’s dropdown menu.
  2. Select Embed a Groovy script from the scripting options that dynamically display
  3. Embed the following Groovy script:

Note: Substitute the INSERT API TOKEN placeholder text with your actual API token.

 *  © 2007-2022 - LogicMonitor, Inc. All rights reserved.
import com.santaba.agent.util.GroovyScriptShell
import com.logicmonitor.mod.Snippets

modLoader = GroovyScriptShell.getInstance().getScript("Snippets", Snippets.getLoader()).withBinding(getBinding())
meraki = modLoader.load("cisco.meraki", "0")

// Set this variable to meraki API token.
def token = ""

// Optionally, create a list of organizations (e.g. [1243,2343,3564,4355])
// Setting this variable will only discover networks on those orgs.
List<Long> orgsAllowed = null

orgsAllowed = orgsAllowed?.collect{ it.toLong() }

Boolean debug = false

orgs = meraki.cachedHttpGet(token, "/organizations")

orgs.each { org ->
    def orgId =

    // Filter in only allowed orgs if it's defined.
    if (orgsAllowed != null) {
        if (!orgsAllowed.contains(orgId.toLong())) {

    def orgName =
    def networks = []
    def devices = []

    try {
        networks = meraki.cachedHttpGet(token, "/organizations/${orgId}/networks")
        devices  = meraki.cachedHttpGet(token, "/organizations/${orgId}/devices")
    } catch (Exception error) {
            if (debug) println error.message

    networks.each { network ->
        def networkId =

        // Check if this network has any devices and avoid reporting deviceless networks.
        def networkDevices = devices.findAll{it.networkId == networkId}
        if (networkDevices.size() == 0) {

        def networkName =
        def networkTags = network.tags.join(",")
        def hostName = "${orgName.replaceAll('\\W', '')}.${networkName.replaceAll('\\W', '')}.invalid"
        def displayName = "Meraki Network: ${networkName}"
        println "${hostName}##${displayName}${orgName}${orgId}##meraki.api.key=${token}${networkId}${networkName}${networkTags}"

    // Only add orgs if they have networks.
    if (networks.size() > 0) {
        println "${orgName.replaceAll('\\W', '')}.invalid##Meraki Org: ${orgName}${orgName}${orgId}##meraki.api.key=${token}"

apiDevice = ["", "", "meraki.api.key=${token}"].join("##")
println apiDevice

return 0

4. In the Default Group field, which displays after the script text box, specify the Cisco Meraki device group you created in a previous step.

Note: Ensure your SNMP credentials and Meraki key are set as properties on this group before running the NetScan. For more information, see Create a Meraki Device Group

Manually Add Devices into Monitoring

You can manually add your Meraki devices into monitoring. There are three types of Meraki devices that can be added:

  • Network device
  • Organization device
  • Meraki API device

When adding these devices, assign them to the device group you created previously. For instructions on manually adding resources into monitoring, see Adding Devices.

Network Device

The network device reports per-device and per-interface data for a specific network.

  • The network device’s hostname (as entered into the IP Address/DNS name field) must end with “.invalid”.
  • Network-specific properties must be assigned to the device, as discussed in the Assign Properties to Resources section of this support article.
Organization Device

The organization device reports per-network device counts and API Usage statistics for a specific organization.

  • The organization device’s hostname (as entered into the IP Address/DNS name field) must end with “.invalid”.
  • Organization-specific properties must be assigned to the device, as discussed in the Assign Properties to Resources section of this support article.
Meraki API Device

The Meraki API device reports per-network device counts and API Usage statistics for all organizations on the account.

  • The Meraki API device’s hostname (as entered into the IP Address/DNS name field) must be “”.

Assign Properties to Resources

In addition to the SNMP and meraki.api.key properties (which we recommend assigning at the group level, as discussed in the Create a Meraki Device Group section of this support article), the following properties must also be set on the Meraki devices within LogicMonitor.

Note: If you added resources into monitoring via NetScan, these properties will already be assigned. If you added resources into monitoring manually, you’ll need to manually set these properties. For instructions on manually setting properties, see Resource and Instance Properties.

PropertyDescription this property on organization devices only. For a list of organizations and their respective IDs, visit!get-organizations.* this property on network devices only. For a list of networks and their respective IDs, visit!get-organization-networks. Be sure to enter the ​organization ID for the organization you wish to see networks on.*

*Ensure that you set the X-Cisco-Meraki-API-Key header to your API key when running any API requests from

Multiple Organizations

Some Meraki configurations can encompass multiple organizations with different SNMP credentials. In such instances, resources belonging to an organization can be grouped by creating a dynamic group for each organization and assigning the specific properties there.

Importing LogicModules

From the LogicMonitor public repository, import all Cisco Meraki LogicModules, which are listed in the LogicModules in Package section of this support article. If these LogicModules are already present, ensure you have the most recent versions.

Once the LogicModules are imported (assuming all previous setup requirements have been met), the suite of Meraki DataSources will automatically begin collecting data.

LogicModules in Package

LogicMonitor’s package for Cisco Meraki consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.

Display NameTypeDescription
Access Point InterfacesDataSourceMonitors Meraki Access Point interface data throughput and packet transmission on a per-network level.
Access PointsDataSourceMonitors Meraki Access Point client connections and operating status.
Gateway InterfacesDataSourceMonitors Meraki Teleworker Gateway interface data throughput and packet transmission on a per-network level.
GatewaysDataSourceMonitors Meraki Teleworker Gateway client connections and operating status.
Meraki API UsageDataSourceCounts Meraki API Usage on a per-org basis.
Meraki Device CountDataSourceCount of Meraki devices by organization on a per-network level as well as a total count.
Meraki Device CountDataSourceCount of Meraki devices by organization.
Meraki License StatusDataSourceReports licensing status of a given organization in Meraki.
Meraki LicensesDataSourceReports licensing status of a given organization in Meraki using the v1 API. This version supports per-device licensing.
Meraki TroubleshooterDataSourceValidates configuration of Cisco Meraki devices.
Security Appliance InterfacesDataSourceMonitors Meraki Security Appliance interface data throughput and packet transmission on a per-network level.
Security AppliancesDataSourceMonitors Meraki Security Appliance client connections and operating status.
SwitchesDataSourceMonitors Meraki Switch client connections and operating status.
Uplink Appliance StatusDataSourceLists the uplink status of every Meraki MX and Z series appliances in the organization.
Uplink Loss And LatencyDataSourceReturns the uplink loss and latency for every MX in the organization.
addCategory_Meraki_APIPropertySourceIdentifies if the host is configured for Meraki API access, adds various system auto properties and appropriate system category of based on whether it is an organization or network device. – Support Page:
addERI_MerakiPropertySourceAdds ERI’s for Meraki hosts. – Support Page: Requires collector version 30.000 or greater.
addERI_Meraki_DevicePropertySourceDiscover and add meraki specific ERI’s for meraki resources
addERI_Meraki_OrgPropertySourceAdds ERI’s for Meraki orgs. – Support Page: Requires collector version 30.000 or greater.
Meraki_Cloud_TopologyTopologySourceMap Meraki Cloud topologies.
Meraki_Org_TopologyTopologySourceMap Meraki Org topologies.

When setting static datapoint thresholds on the various metrics tracked by this package’s DataSources, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

Migration from Legacy DataSources

In June 2022, LogicMonitor updated the Cisco Meraki suite to use the Meraki API v1 and expand topology support for identifying Meraki devices. As part of this update, the Cisco_Meraki_Switch_Interfaces DataSource was deprecated. You can still monitor switch connection status and client count using the Cisco_Meraki_Switches DataSource. For more information, see Deprecated LogicModules.

In June 2020, LogicMonitor released a new suite of Cisco Meraki DataSources to expand monitoring coverage and improve efficiency for future scalability and support. The release of these new DataSources serves to deprecate the following legacy Meraki DataSources:

  • Meraki_CloudController_DeviceInventory
  • Meraki_MR_Interfaces
  • Meraki_MR_Stats
  • Meraki_MS_Stats
  • Meraki_MX_Interfaces
  • Meraki_MX_Stats
  • Meraki_Z_Interfaces
  • Meraki_Z_Stats

If you are currently monitoring Meraki devices using any of these legacy DataSources, you will not experience data loss upon importing the new DataSources. This is because DataSource names have been changed to eliminate module overwriting.

However, you will collect duplicate data and receive duplicate alerts for as long as both sets of DataSources are active. For this reason, we recommend that you disable the above-listed DataSources after importing the new set of DataSources and confirming that they are working as intended in your environment.

When a DataSource is disabled, it stops querying the host and generating alerts, but maintains all historical data. At some point in time, you may want to delete the legacy DataSources altogether, but consider this move carefully as all historical data will be lost upon deletion. For more information on disabling DataSources, see Disabling Monitoring for a DataSource or Instance.

In This Article