Webhook Event Collection & Cisco Meraki
As a Cisco Meraki Strategic Technology Partner, we are always looking for ways to make our integration the best that it can be, so you can get the most out of your investments with Cisco and LogicMonitor. So, today we kicked off R&D planning for [safe harbor statement] the ability to collect webhook events from Cisco Meraki with the following objectives. Mitigate Cisco Meraki Dashboard API rate limiting. Enable [near] real-time alerts for things like camera motion, IoT sensor measurement threshold breach (or automation button press), power supply failure... Facilite sending webhook events from Cisco Meraki to LogicMonitor I have the following assumptions. Customers want to be alerted on most, but not all webhook events. Customers want to have multiple inbound webhook configurations, i.e. for different tenants/customers or different Cisco Meraki organizations. Cisco Meraki is the first but not the only platform that customers will want to use to send webhook events to LogicMonitor. If you had a magic wand and could make such an integration do exactly what you wanted, what would be your number one ask? Thank you!48Views3likes0CommentsMeraki Cellular Gateways and Sensors
We’re planning R&D that “aims” to monitor Meraki MG Cellular Gateways and MT Sensors and to give them their own Topology Map graphics. Please DM me if youuse either of these types of Meraki devices and would like to participate in the R&D process.123Views30likes5CommentsCisco Meraki Environmental Sensor Monitoring
Today, new modules are available in LM Exchange to monitor Cisco Meraki MT-Series Environmental Sensors. These fully support Resource Explorer and include a new (IoT) Sensor Topology Graphic. If you are subscribed, these devices count toward the Wireless Access Points SKU.49Views11likes0CommentsFirst real attempt at using the new Meraki DataSources
As mentioned before, we probably won’t be using the new Meraki monitoring due to the significant increase in license cost. However, there are several benefits to that increase in cost: Meraki devices are devices instead of instances, so they’ll be able to do everything regular devices can do. That includes putting them into location specific groups. There are a few additional metrics provided that weren’t fetched before. Not sure if it wasn’t possible or if it just wasn’t added in. Local monitoring: since they’ll be devices, existing LogicModules can apply to them. That’s good because things like Ping can be used to distinguish between “device down”,“device not connected to Meraki controller”, and some of the false positives we would get from the Meraki troubleshooter DS. Not sure, but it looks like the monitoring is all (or mostly) done via the API. I’m still trying to work on why the netscan needs the community string if it’s coming via the API but it’s difficult to tell what the modules are going to do (and how). The module toolbox->exchange has the option of pulling in a package but doesn’t treat it as a package once it’s installed. I’ve not found a way of filtering by package so that Ican look at what each of the modules do. To give these benefits a try, I decided to give it a chance in my sandbox. Here are my findings: License count is per device instead of network. Thischanges the way the licensing works making certain networks financially equivalent to the old method from a monitoring perspective. For example, today, if we have a customer that has one network per retail store with one device in it, but has a thousandretail stores, the cost is pretty significant. We are paying for 1000 networks. That simply won’t work. However, if we have a customer with one network with 1000 devices in it, we are paying for one network. With the new model, 1000 networks with 1 device each costs the same as 1 network with 1000 devices. The cost for the retail customer doesn’t change, but all other networks increase in cost. You can filter by network ID within the NetScan by setting a credential property, not by setting anything in the filter section of the NetScan. You cannot exclude certain network IDs from the NetScan. You can only include, excluding everything else. For our use case, this is the exact opposite of what we need. If you want the discovered devices to be monitored by other than the collector running the netscan, you have to upload a CSV file to the collector. Why isn’t there a UI for this? Why isn’t there a wizard that lets you manage your Meraki cloud the same way you manage your AWS cloud account? If this were built, you could 1) test credentials, 2) ensure the right networks/devices are included, 3)handle collector mapping in much the same way AWS collector mapping happens, 4) not have to make sure you spell the 18 property names correct, 5) not have to copy and paste 475 lines of code into a NetScan, 6) preview the group structure (or opt out) I didn’t even get to the point where I tested the netscan. When juggling a couple windows, i accidentally closed the tab where i was building the netscan. I didn’t get a warning using the onbeforeunload event. For these reasons, I’ll have to wait another 3-6 months to see if LM can come up with any improvements.Solved297Views27likes5CommentsMeraki Monitoring
Recently we have discovered Meraki devices by using Advanced Netscan. We are facing 2 issues 1)while monitoring the Access Point/Switch Performance & Port capacity. Under the Raw data Tab i am seeing No Data. Even i change the Threadpool under bactchscript timeoutof 20 to 40 Sec. after doing this also i am not seeing any data. I Tested the script fromthe data source level also checked but we are not seeing data. earlier it was showing Serial Number was missing, I am seeing the Serial Number under Custom Properties. We are not added manually. instead of seeing in Auto properties. It is showing under Custom Properties. 2)There is issue with Netscan where it is not adding devices to desired path, I mentioned the Desired Path under the Netscan Properties but still it is showing under the parent group. If i moved manually when i run the netscan again it will come under parent group. Please guide me how to resolve this Issue ?443Views15likes5CommentsNew Cisco Meraki Datasources Dropped
Has anyone implemented these? I imported the Meraki Camera Health DS just to have a look at it and the Technical Notes read as follows: Requires **Cisco_Meraki_API** DataSource to collect data. Reports normal system.hoststatus when device is online. This module applies to LM Envision resources that represent discrete Meraki devices. These modules are not in-place upgrades from legacy Meraki modules that applied to LM Envision resources which represent a Meraki Org or Meraki Network. Each LM Envision resource that this module applies to will consume a LogicMonitor license. Prior to implementing, check with your administrator to ensure you have sufficient LM Envision licenses. For more information about migration from legacy modules and onboarding of discrete Meraki devices, see [Cisco Meraki Monitoring](https://www.logicmonitor.com/support/cisco-meraki-monitoring) product documentation. I don’t know what an LM Envision License is. The tech notes also reference what appears to be some new internet facing collectors possibly called “LM Envision Collectors”. I have no clue what those are. I have almost 500 Meraki Networks currently in monitoring. Am I supposed to migrate? Opened a support ticket for some clarity but in the meantime figured I’d get a thread started here to see what everyone else is doing.251Views16likes8CommentsCisco Meraki
This week, in addition to launching a new suite of Cisco Meraki modules, updating our integrations page, and creatinga new set of product docs, LogicMonitor is now in the Cisco Meraki Marketplace. Cisco Meraki Marketplace: https://apps.meraki.io/en-US/apps/420402/logicmonitor-%7C-lm-envision Cisco Meraki Integrations page: https://www.logicmonitor.com/integrations/meraki New Cisco Meraki Monitoring Product Docs page: https://www.logicmonitor.com/support/cisco-meraki-monitoring249Views18likes6CommentsMeraki monitoring within Logic Monitor
Hi all, I am attempting to monitor a Meraki MX appliance from LM, I have setup the API but can only see connected clients and connected status.. Is there a way to monitor the up/down status or packet loss of an MX device through LM? Thank youSolved548Views13likes3CommentsAnybody else disabling Meraki instances by default?
If you are, I’d like to know if you’re experiencing the problem we are that LM has tried and failed to troubleshoot: For some random reason, a number of meraki instances disappear from LM during one discovery cycle and reappear during the next discovery cycle. This isn’t normally a big problem since they instances aren’t set to delete until 30 days. Normally, they’d just show back up and have a gap in data. However, in our casewe have a business need to have the instances disabled on discovery (we charge the customer per Meraki device we actively monitor). This means that instances that have been discovered and enabled for monitoring randomly disappear and reappear as disabled instances. Also, any customer instance level properties that were added to the instance also are not present on the rediscovered instance. In the last 3 hours, there have been 3,577 instances (out of somewhere around 18,000) that disappeared and reappeared in this way. The problem was so pervasive that I had to write a script to loop through all instances and enable them based on a master billing sheet.Solved350Views14likes11CommentsMeraki Cloud Devices doesn't get pulled for monitoring when using api or snmp, need help!
Hello all, Going all by the book, following each step on LM support page for meraki cloud monitoring, but no lock getting the devices listed. snmp v2c, v3 no luck, providing api key from the dashboard just gives me the organizations and their device counts but no luck seeing devices. Tried using previous existing environment we have, i still can’t get this setup for the customer specifically. Any help? I also keep getting snmp community connection error, where it says it couldn’t communicate with snmp.Solved795Views3likes10Comments