Patrick_Rouse
Product ManagerJoined 4 years ago
User Profile
Product Manager
User Widgets
Contributions
Re: Webhook Event Collection
In our engineering environment, I am now actively getting real-time communications from the Cisco Meraki Dashboard into LM Logs via Webhook Event Collection. In the Meraki Dashboard I’ve setup a Webhook Template to format the messages the way I want and added a new Webhook Receiver that points to an API ingest URL for the specific LogicMonitor with a Bearer Token to for authentication. With this in place, alerts that used to go to my email can additionally or instead go to LM Logs. In my preliminary testing, the message delivery is fairly instantaneous.Re: What is up with Meraki API Modules?
Two netscan improvements are coming your way soon. 1. In portal version 220, if the Meraki Enhanced Script Netscan reports a different IP Address than is in system.hostname, it will automatically update the system.hostname and system.ips values on the associated devices in your portal. Currently, we rely on the IP address and device name, but this changes to using the meraki.serial as the device's unique identifier. 2. In Q2 (April-June), we're planning to implement a "test" button in the Enhanced Script Netscan, so you can see what it would do if you ran it.Re: What is up with Meraki API Modules?
I'm sorry you're struggling, but we'd be happy to help. Some key points. If something is affecting your ability to monitor, please contact LogicMonitor support. However, if it's not urgent or you're just looking to learn from others this is a great place to do that. The Cisco_Meraki_API DataSource is the module that collectors use to get all of the data from the Cisco Meraki Dashboard API. I'd advise that you not edit this module or change the polling frequency, as this module has internal timing that it uses to gather data that the other Meraki modules rely on. The current version of this DataSource is 1.31.0 and no longer uses any per-device API calls for Cisco Meraki Switches, which was a limiting factor for larger customers with thousands of switches. If you're getting no data for the client count in any of the performance modules, it'd because the meraki.snmp settings are invalid or your collector cannot access snmp.meraki.com on port 16100. That Meraki Cloud SNMP service only provides LM with the client count for the performance modules and send/receive data for the Meraki Interfaces modules (not Switch Interfaces). For the modules to work, you "need" the following properties on each device (set directly or inherited) meraki.serial (this is device specific) meraki.api.org (this is the organization ID for your Meraki org) meraki.api.network (this is the network ID for the Meraki devices at a given location) system.categories (if you don't add a value here, the PropertySource "addCategory_Cisco_Meraki_Device" will set this for you "when it runs"). The NetScan adds this for you, but if you add devices another way you can either let the PropertySource set this or you can set it manually based on the device type. The Resources Tab here has a PDF that shows what the Meraki Monitoring for each device type should look like -> Cisco Networking App Marketplace Screenshot from a device in my portal with the properties set. Resources: Cisco Meraki Monitoring product documentation Cisco Networking App Marketplace Create a LogicMonitor Support Case
