Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
LogicMonitor’s out-of-the-box monitoring for Cisco Meraki monitors:
Perform the following steps to ready the Cisco Meraki Dashboard API:
See Cisco’s Meraki Dashboard API documentation for instructions on enabling the API and generating a key.
SNMP v2c or v3 must be enabled on the Meraki Cloud Controller. See Cisco’s SNMP Overview and Configuration documentation for instructions.
From the Resources page, create a Meraki device group and assign it the following properties:
For more information on creating device groups, see Adding Device Groups.
Add your Cisco Meraki hosts into monitoring. As discussed next, 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.
You can automatically add all Meraki networks, organizations, and a main api.meraki.com device via an advanced NetScan. For general instructions on creating and running an advanced NetScan, see Creating NetScans.
Ensure the following configurations are in place for the NetScan:
Note: Be sure to substitute the INSERT API TOKEN HERE placeholder text located at the top of this script with your actual API token.
INSERT API TOKEN HERE
/******************************************************************************* * © 2007-2020 - LogicMonitor, Inc. All rights reserved. ******************************************************************************/ import com.santaba.agent.groovyapi.http.HTTP import groovy.json.JsonSlurper def token = "INSERT API TOKEN HERE" def hostname = "api.meraki.com" def httpClient = HTTP.open(hostname, 443) try { orgs = httpGet(httpClient, token, "/organizations") orgs.each { org -> def orgId = org.id def orgName = org.name def networks = httpGet(httpClient, token, "/organizations/${orgId}/networks") def devices = httpGet(httpClient, token, "/organizations/${orgId}/devices") networks.each { network -> def networkId = network.id // Check if this network has any devices and avoid reporting deviceless networks. def networkDevices = devices.findAll{it.networkId == networkId} if (networkDevices.size() == 0) { return } def networkName = network.name def networkTags = network.tags def hostName = "${orgName.replaceAll('\\W', '')}.${networkName.replaceAll('\\W', '')}.invalid" def displayName = "Meraki Network: ${networkName}" println "${hostName}##${displayName}##meraki.org.name=${orgName}##meraki.org.id=${orgId}##meraki.api.key=${token}##meraki.network.id=${networkId}##meraki.network.name=${networkName}##meraki.network.tags=${networkTags}" } println "${orgName.replaceAll('\\W', '')}.invalid##Meraki Org: ${orgName}##meraki.org.name=${orgName}##meraki.org.id=${orgId}##meraki.api.key=${token}" } println "api.meraki.com##api.meraki.com##meraki.api.key=${token}" } finally { httpClient.close() } return 0 def httpGet(httpClient, token, endpoint, previousResponse = null) { JsonSlurper slurper = new JsonSlurper() def headers = ["X-Cisco-Meraki-API-Key": token.toString(), "Accept": "application/json" ] def url = "https://api.meraki.com/api/v0${endpoint}" httpClient.get(url, headers) def statusCode = httpClient.getStatusCode() def rawResponse = httpClient.getResponseBody() if ([200, 429].contains(statusCode)) { def response = slurper.parseText(rawResponse) if (previousResponse) { response += previousResponse } if (statusCode == 200) { def links = httpClient.getHeader('link') if (links) { links.split(',').each { link -> rel = link.split(';')[1].split('=')[1] if (rel == 'next') { nextEndpoint = link.split('/api/v0')[1].split('>')[0] return httpGet(httpClient, token, nextEndpoint, response) } } } return response } else if (statusCode == 429) { def retryIn = httpClient.getHeader('Retry-After').toInteger() sleep(retryIn * 1000) return httpGet(httpClient, token, endpoint, previousResponse) } } println "Error occurred." println "Status Code: ${statusCode}" println "Response Body: ${rawResponse}" return null }
As an alternative to running an advanced NetScan, you can manually add your Meraki devices into monitoring. There are three types of Meraki devices that can be added:
When adding these devices, assign them to the device group previously created, as discussed in the Create a Meraki Device Group section of this support article. For instructions on manually adding resources into monitoring, see Adding Devices.
The network device reports per-device and per-interface data for a specific network.
The organization device reports per-network device counts and API Usage statistics for a specific organization.
The Meraki API device reports per-network device counts and API Usage statistics for all organizations on the account.
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.
meraki.api.key
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.
*Ensure that you set the X-Cisco-Meraki-API-Key header to your API key when running any API requests from https://developer.cisco.com/meraki/api.
X-Cisco-Meraki-API-Key
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.
In June of 2020, LogicMonitor released a new suite of Cisco Meraki DataSources. The new DataSources offer several advantages, including expanded monitoring coverage and improved efficiency for future scalability and support.
The release of these new DataSources serves to deprecate the following legacy Meraki DataSources:
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.
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.
system.categories
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.
In This Article