Forum Discussion

Anonymous's avatar
Anonymous
2 years ago

First 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 devic...
meraki
not ready yet
  • Joe_Williams's avatar
    Joe_Williams
    2 years ago

    The idea of the wizard/configuration tool like with AWS is actually awesome. That would make it alot easier to facilitate items like this.

Anonymous's avatar
Anonymous
11 months ago

Thanks to @shea.novy we have a solution. If you have this at the start of your netscan script:

import com.santaba.agent.util.GroovyScriptShell
import com.logicmonitor.mod.Snippets
modLoader = GroovyScriptShell.getInstance().getScript("Snippets", Snippets.getLoader()).withBinding(getBinding())

Replace it with this:

import com.logicmonitor.common.sse.utils.GroovyScriptHelper as GSH
import com.logicmonitor.mod.Snippets 
modLoader = GSH.getInstance()._getScript("Snippets", Snippets.getLoader()).withBinding(getBinding())

This just highlights how Meraki monitoring needs to be done by the LM cloud collectors (same as AWS, GCP, Azure, Zoom, Webex, Slack, Salesforce, O365, and the huge number of “lite” offerings.