Stuart Weenig

  • Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

3 Neutral

About Stuart Weenig

  • Rank
  • Birthday 02/29/1980

Recent Profile Visitors

245 profile views
  1. We recommend using Postman. This post describes what to do to get it setup in Postman, which is known to be secure.
  2. The Auth token for a shared widget cannot be used to make API calls. They are two completely separate sets of tokens. What you need to do is setup an API token that is associated with a user. All that said, what exactly is your goal? What are you trying to do?
  3. Haha, those are really nicely written functions, aren't they. 🙂
  4. Also! We will be including explanation and Q&A on how our Meraki monitoring has been enhanced.
  5. Just to be sure, you're not talking about downloading from the device to LM. You're talking about downloading from LM to your laptop. I thought the first until I saw @mnagel's response.
  6. There is a more LogicalMonitor way to do it. (see what i did there?) I believe we're working on getting information ready to present, but I think we're shifting the way LM monitors Meraki to utilize the API instead of SNMP (like you have done). I think it does something like breaking it up so each network is represented as a different device in LM splitting the monitoring across parallel tasks. Should skirt the 429 problem. How urgent is this for you?
  7. Q&A Transcript: Q: If I install a Collector as one size, and later re-size it, is there any difference whatsoever to what I would have had if I had added it that way at first? In other words... is the Size just a config file change, and 100% of all the other Collector components are the same no matter what is the size? A: That’s correct- the size just allows more resources to the collector agent to monitor more instances/devices concurrently Q: Are things like Collector on-disk file metadata (checksums, dates, sizes) all the same within a certain version? For example would a Tripwire profile for a Medium Collector be usable to validate a Large other than the config files and logs? By the way I know that's a fairly advanced use-case question, so feel free to drop me an email if there's no time today or if it's too advanced for this session! No rush on that one!! It's more of a nice-to-know for when we begin automating our Collector deployments later this calendar year. A: Follow-up expected from the product team shortly. Stay tuned. Q: How intrusive is all the polling on the devices. - specifically on large switches. A: Generally speaking, for a switch we’d be polling with SNMP, so very lightweight, but if you’re monitoring something like an ESX host with thousands of VM guests the batch script modules can use more resources while processing the requests. Q: As part of our regular alert review process, we pull a report of the open and closed alerts to check the alert trend at the device and the module level. However, some of these alerts would have got tiggered when the device or the instance was placed under SDT. Is there a way we can identify and filter out such alerts in our reporting when we pull the alerts report at the end of the week/month? Basically, the intention is to focus only such alerts that we worked upon and ignore those triggered during SDT. A: I don’t believe you can create an alert trend report that would exclude SDT alerts, but you should be able to manage this using the alert filtering options in a normal Alerts report- Under “More” select “SDT” and change the value to “No” Q: Is it possible to have a link in Logic Monitor between a "Network Switch" and "Devices" behind it? So when the "Network Switch" is down Network will receive an alert and the Server Team will received a list of devices falsely sees "down" with a reference to the "Network Switch" cause of the "Device down" A: Depending on your LM account level you may have access to the Root Cause Analysis/Dependency feature which enables this through our topology mapping
  8. More deliverables from this webinar coming soon. In the meantime, please fill out our feedback survey.
  9. Please check your direct messages here in the communities. Let's figure it out privately then post the working script back here for others to benefit from.
  10. Taking this conversation private.
  11. Looks like the token id and key you are trying to use doesn't match an existing token id/key. 9e266... is the one you're trying to use, but that API token doesn't exist. Perhaps update the device properties to the and key?
  12. Yeah, you have some Write-Host statements in the function that are being output along with the final output. The only output should be the actual property with its value. Instead of doing the Write-Host statements, you could maintain an "output" variable with all the debug messaging and then at the end output that in your final if/else statement.
  13. Any properties written using "Write-Host" will not be saved to the device, but the patch operation would be attempted. However, you're missing the Send-Request function definition, so nothing's being done.
  14. Hey, looking good. You should see the ip2dns.result property on the device now. It looks like you're trying to call the Send-Request function without actually having that function defined. It might be as simple as copying the Send-Request function from the script you were given. If that function is written properly, it should work.