Anybody else disabling Meraki instances by default?

I’m not experiencing this on a completely unrelated custom datasource. I built this ds because we needed a single DS that reported on collector disk usage whether or not we were monitoring the collector via ssh/wmi, so it only applies to collectors. Here’s the discovery script:

try {
    def sout = new StringBuilder(), serr = new StringBuilder()
    if (hostProps.get("system.collectorplatform") == "windows"){
        def proc = 'powershell -command "Get-CimInstance Win32_LogicalDisk | Where{$_.DriveType -eq 3} | Format-Table -Property DeviceID, Size, FreeSpace -HideTableHeaders"'.execute()
        proc.consumeProcessOutput(sout, serr)
        proc.waitForOrKill(1000)
        // println("stdout: ${sout}")
        sout.eachLine{
            splits = it.tokenize(" ")
            if (splits[0]){
                println("${splits[0].replaceAll(':','')}##${splits[0].replaceAll(':','')}")
            }
        }
        return 0
    } else {
        def proc = 'findmnt -D -t nosquashfs,notmpfs,nodevtmpfs'.execute()
        proc.consumeProcessOutput(sout, serr)
        proc.waitForOrKill(1000)
        sout.eachLine{
            splits = it.tokenize(" ")
            if (splits[0] != "SOURCE"){
                println("${splits[0]}##${splits[6]}######type=${splits[1]}&size=${splits[2]}")
            }
        }
        return 0
    }
} catch (Exception e){
    println(e)
    return 1
}

I can’t see any reason the instances would not show up, especially given that the hardware hadn’t changed.

I know for a fact that the instance disappeared and reappeared. For one, there was a no data alert that opened a ticket in my ticket system yesterday. The collection script didn’t gracefully handle a “-” in a place where it was expecting a number. So, i disabled the instance. When i click on the link to go to the alert today, it shows the alert (as cleared). However, if i try to drill into the instance from the alert, i’m taken to the root of the account (this is what happens when the target of a link doesn’t exist anymore). 

However, if i navigate to the device, i can see the instance (enabled!) and can see no historical data before 9pm last night. 

I’ve had a case open with support since last year about this behavior on Meraki but they eventually closed out the ticket saying the new modules might fix the issues.

I guess I’m just saying, keep an eye out for any instances that disappear and reappear.

LogicMonitor’s Meraki DataSources are frankly not fit for purpose when it comes to monitoring large Meraki estates.

For those that need this, please do check out our Meraki DataMagic product ( Google: meraki datamagic ).  There is a free tier and an unlimited free month trial.  All you need are an Azure AD account and a Meraki API key.  Setup takes under a minute.

This gets all data into a staging database, ready for reporting in LogicMonitor.  We provide free DataSources so that you can query that data.

Making the script was a bear, but only 264 lines. I might have made it simpler by doing PUTs instead of PATCHs, but I didn’t want to PUT for all ~1200 meraki devices. Instead, i pull the whole list from LM and compare with my system of record and only do PATCHs for the ones that are different.

We are pretty aware that the "automatically delete instance" setting isn't supported until now. But how should we then keep track of all the changes that are made to our Meraki networks? Currently we monitor approx. 100 Meraki networks with LM, including more than 1200 access points - how can we make sure that we monitor "actual devices" rather than orphaned DataSource instances? We have similiar business needs as Stuart - to write a custom script for comparing LM monitored with actual Meraki devices and delete orphaned instances would be the last straw for us to fit our business needs.

nevertheless, we are glad to hear that you guys are actively trying to improve this modules 🙏

@klamir -- Can you please share with me (in a private DM) your support ticket number? I want to make sure we have full scope over which customers are currently experiencing this.

@Stuart Weenig -- I just picked up your follow-up on our previous case. We still have an active internal ticket with our Software Engineering team regarding this, so please allow me some time to see where we are and what we can do at this time.

I do want to emphasize for all who may be reading this post -- our core (LM created) Meraki DataSources are configured with auto-delete instances disabled (“Automatically Delete Instance”). Any change to this setting is considered custom and therefore unsupported by our Support and SWE teams. At this time, this is not a supported feature for these modules.

That said, as mentioned above, our SWE team is actively investigating potential improvements to our suite of Meraki LogicModules. 

I opened a ticket with support on December 1, 2022 and they couldn’t do between then and now what you appear to have done in a few days, with actual proof. Would you please bring this up with support? They adamantly denied any kind of 429 errors and also claimed that if any 429s were experienced that the discovery would exit unsuccessfully, thus causing LM to ignore the output of the discovery. 

Since there is now proof that this is happening, perhaps they can reopen the case.

None of our meraki networks have that many devices. Couple hundred per network tops. Average is probably 30-50 per network.

I don’t know how you are setup but when this occurs is it happening on one Meraki device with a ton of instances or multiple devices with instances?

Have had a case open since December 1 with LM Support. Their final response: 

[We] really appreciate your continued patience while our teams thoroughly investigate. At this time, our Collector and Monitoring Engineering teams have reached a stopping point and there isn't anything further for them to investigate. The additional logging is showing that there is no issue with the core module behavior and we're processing the full response from the API with proper checks to ensure we've collected all data and paginated where necessary.

Supposedly they checked for pagination issues with the API, rate limiting, and I would assume batchscript output limits.