All Activity

This stream auto-updates     

  1. Yesterday
  2. Correct! That's the incentive of monitoring it the way @Mike Moniz mentioned.
  3. Thanks Guys! One further question i would have then is referring to licensing... If I am only monitoring one Cloud Access Controller then that would mean i am only burning one device license at that point correct?
  4. When you add snmp.meraki.com to LogicMonitor, with the correct SNMP details from the cloud website, LogicMonitor should pull in all the devices hosted in that cloud account. It will look something like below. You can also add the devices directly, assuming the collector is on the same network, which provides a bit more detail like listing each interface for switches, but also some overlap with the cloud version. I would suggest setting the cloud version first, then perhaps add local versions of each type of device and review differences. You can always do both and disable checks that overlap if needed. Also note that if you have multiple Meraki Cloud accounts, they each need to be on their own collector OR you can use DNS tricks like discussed here: Meraki Multiple Organizations https://www.logicmonitor.com/support/monitoring/networking-firewalls/meraki-cloud-wireless-access-controllers/
  5. You can monitor Meraki Devices individually by adding each device and using the Interface VLAN IP for each site on the MX. The interface needs to be available by the LogicMonitor Collector which is most likely the case if the remote sites are connected back to HQ via VPN. This is assuming your LogicMonitor Collector is located at HQ. Meraki MX > Security & SD-WAN > Addressing & VLANS > Use either Management or Data Interface VLAN IP If you use templating on the Meraki Portal, make sure your MX template has a configuration for SNMP Users. So navigate to the Meraki MX Template and go to Network Wide > General > Scroll down to SNMP Users and configure a Username and Passphrase if using SNMPv3 and this will push the configuration to all your MX's. Lastly, on the LM side you might need to specify snmp.priv custom property as DES specifically as there might be issues in collecting, but AES might work as well. In addition you can go to Organization > Configure > Settings > and scroll down to the SNMP section and enable SNMPv2 or SNMPv3. Enter your preferred Authentication/Privacy Password and Mode. You can also lock the IP Restrictions down to your Collector IP's. Hope this helps!
  6. Hello, I was wondering if anyone out there would be able to help me out with the proper way to monitor multiple Meraki devices. The use case will be to have the ability to monitor one Meraki Firewall and multiple Meraki switches in multiple sites. However from my understanding they are under one cloud access URL. What would the best coarse of action to monitor these devices to get individual device statistics? Thanks in Advance
  7. My ability to edit the previous post timed out (annoying)... here's the final thing I was going for: if (get-date -format HH -eq 10) { if ( test-path "\\servername\C$\Path\To\File.txt" ) { write-output "1" } else { write-output "0" } } Just checks the 24hr Hour to see if it's 10. Have it fire once an hour.
  8. I don't specifically have a ready made one, but if you make a DS that "AppliesTo" a system.hostname=="oneOfYourCollectors" (make sure it's in the same domain as the resource with the UNC path you want to check). Then something like: if ( test-path "\\servername\C$\Path\To\File.txt" ) { write-output "1" } else { write-output "0" } as a powershell script should do the trick.
  9. Does anyone has any readymade datasource available? If so can you please share?
  10. Last week
  11. With the issues we've been having with collector resource exhaustion, I've been thinking about ways to reduce the amount of dataSources that run on the collectors at any given time. It occurs to me that if there is a host down, all of the datasources are still trying to run against it and having to await timeout before releasing their resources on the collector. I'd like to submit that a Host down status should issue a partial SDT for the device that would prevent all but the host status datasources from running against that device. The host status change could then remove the SDT once it has cleared. This would prevent devices in environments that spin them up / down based on load rather than a schedule from taking up too many collector system resources during their down time. It would also help alleviate strain during larger outages while still providing just the actionable information necessary to address the situation.
  12. The use of screen real estate is horrible too. On my 15" Macbook Pro I can only see a handful of alarms at one time and clicking into the alarms is very tough to use since it uses that same small area for the alarm details. Need to find a way to hide the filter and move more of that stuff up on the screen.
  13. There are at least two reasons why not to use LMConfig. First is cost -- it is a premium feature and as applicable as it might be here, it is insane to invoke an extra charge to get this basic concept implemented. Second (more important) is that LM does not actually tell you what changed. We work around this via the API to download, commit to a git repo and use a hook to get email on changes. That could also work, but again seems like a lot to ask of users. The file storage method could work, but if there is a collector failover or change you lose state. Building redis or similar into the toolset would help with this sort of thing.
  14. Some possible workarounds: I think LM Config might be the better option for this, although I haven't played with it personally yet. It's designed for config files, but I don't see why the "config" file can't just be the version info. Also rather than attempt to use properties to store state, you can try using a file on the collector, for example "../tmp/firmware_${hostname}.LastRun" then it would be easy to read in the script. There might be an issue if resource bounces around collectors though. You might also be able to using Auto Discovery Instances with DataSources, which lets you set auto properties, but that might be tricky to implement.
  15. I am trying to get an eventsource that reports when the firmware version has changed (this is something other tools "just do"). To do this, my "applies to" for auto.firmware_version works great, but then the script needs to use this logic: if auto.firmware_version != auto.firmware_version.prev then generate event that says "firmware version has changed from old to new" set auto.firmware_version.prev to auto.firmware_version end I imagine I could use the API for the "set" operation, but using the API in logicmodules always makes me cringe due to lack of library support. I detest maintaining the same code across many different modules as it is error-prone. If there could be a hostProps.set method, that would be very helpful. I understand this could be dangerous, so if it must have the same restrictions as propertysources, I can live with that.
  16. I just tried this as well and it is definitely cumbersome. There is no completion when you start with ! and if you use completion, there is no opportunity to prepend the !. I would hope with such a major revamp that a complex expression editor would be part of the upgrade
  17. @Ron - we have some "beta" Rubrik datasources that are available - I would suggest reaching out to your customer success manager and they can help facilitate adding those to your account. I'm not seeing anything for Cohesity but it looks like they have an SNMP agent available, so you could potentially tackle it that way. *Edit - I saw your other post, the beta datasources do use the Rubrik API (and not SNMP.)
  18. or for sites that place dashboards up on big NOC displays at the front of a call center.
  19. No such luck... could you verify that this is the correct URL structure for this @Forrest Evans - LM? https://companyname.logicmonitor.com/santaba/rest/device/devices/9999?opType=replace Even being really pedantic about it still isn't taking it: https://companyname.logicmonitor.com/santaba/rest/device/devices/2469?opType=replace&patchfields=autoBalancedCollectorGroupId,preferredCollectorId same error: Invoke-RestMethod : {"errorMessage":"custom property name cannot be predef.externalResourceID\ncustom property name cannot be predef.externalResourceType\n","errorCode":1404,"errorDetail":null} At C:\Scripts\Balance-LMABCG.ps1:51 char:24 + $response = Invoke-RestMethod ` + ~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand
  20. Thank you Forrest. As always, a font of great information. I assume from the reading that the default is "refresh" From the link above (to save folks some clicking): "opType=replace indicates that the properties included in the request payload will be added if they don't already exist, or updated if they do already exist, but all other existing properties will remain the same" I'll be putting this in place to day and I'll report back... hopefully with a new $data block for the script and calling it done!
  21. Hi Cole, predef.* attributes are used by our Topology Service and can't be updated through the API, only through LogicModules. They aren't specific to Azure as they may be applied to standard devices as wel To update a device with Properties and not affect others you'll want to update the device using PATCH command documented here: https://www.logicmonitor.com/support/rest-api-developers-guide/v1/devices/update-a-device/#PATCH. Pay particular attention to the customProperties opType option. Note: I haven't looked through the code. I'm just offering this based on the last two posts. ~Forrest
  22. A dark theme would be my preference. Much easier on the eyes, especially for night shifts.
  23. One day we might get a dark theme... 😀
  24. Hi @Linus, thanks for looking into this further. I can confirm that if I use !(*Test) in the new UI it now excludes correctly. Weird that !(Test) worked fine in the old UI though.
  25. If your are not aware you should be able to edit the soap xml values to fill in whatever fields you need. I don't use Autotask myself but it looks very similar to other Integrations. When you setup an integration, you will fill some values on the top half and then click on a Generate button. This will then auto-populate the HTTP Delivery section based on your values. You can edit the various parts of the HTTP Delivery section and modify the default Soap XML request to add in any other field you want to add. You can use various LM Tokens or hard-coded values.
  26. No updates from LM on this last point. It's the last piece I've got on this. I'm going to put it in place anyway as it works on the other ABCGs in our environment and doesn't do anything to the other when it fails due to the azure resources being REST API incompatible due to naming convention issues with their properties. I suspect it's just a miss and will magically start working at some point. (Again, this is where I point out that we're not liable if you implement this and it doesn't work in your environment). customProperties : {@{name=predef.externalResourceID; ... hopefully they get this sorted out soon.
  1. Load more activity