Matthew Dunham

LogicMonitor Staff
  • Content Count

  • Joined

  • Last visited

Everything posted by Matthew Dunham

  1. Hi @Cole McDonald - The LogicMonitor Collector runs jobs using the permissions it has inherited from the Collector. Where the Collector is run as a privileged user so will the jobs that it's launched. Regardless of which Collector permissions model you adopt, as a best practice we recommend using our role-based access controls to limit "Manage" access to your Collectors. You can do so by assigning individuals that don't need Collector Debug functionality the "manager" role rather than the "administrator" role. This allows you to effectively limit the scope of your end-users ba
  2. Thanks @mnagel -- this is indeed the recommended approach. And yes, we're working on getting a frequency scheduler attached to PropertySources. Coming soon....
  3. Hey Jamie - Good point. As a workaround, you can create a Complex Datapoint ( to do what you need. We maintain the datasource pollling interval as a token you can substitute into your complex datapoint expressions. Provided your units are per-second (or converted as such) you can translate your "rate datapoint" into a "difference datapoint" using something like: rate_datapoint * ##POLLINTERVAL## A little more detail on substitution tokens available in datasources creation are
  4. You should be able to find it in our "core" repository, which you can access from DataSources => Add => From LogicMonitor Repository. We're in the process of streamlining this process. Apologies for the confusion.
  5. An octet is really just a fancy name for a "byte". So if you multiply this number by 8 you get bits -- that solves part of your question. The other trick is that you need to convert the point-in-time octets measurement to a rate with units of octets/sec (and eventually bps). In LogicMonitor you can do so by using the "counter" or "derive" datapoint type. See for details, but the short version is that these two datapoint types subtract the current value from the previous value and then divide
  6. Note that LogicMonitor does not endorse running Collectors with the EnforceLogicMonitorSSL configuration item set to "false". This setting disables certificate verification the Collector uses to authenticate our service platform before sending sensitive data. By disabling this, you risk exposing the data your Collector sends upstream to a man-in-the-middle attack. Where a decryption proxy is in use, we recommend that you disable proxying for Collector traffic as Mike specifies above.
  7. Hi Joe - Thanks for the suggestion. That's maybe a reasonable improvement to the Collector Properties feature set. We designed Collector Properties primarily to assist in the diagnosis and identification in the context of Collector Down notifications, so we wouldn't have expected a use-case by which they're used to store credentials or other sensitive information. Would you mind explaining your use-case so we can get some additional context?
  8. Thanks Eric! I have been attempting to engage with the Microsoft mothership on this issue for some time and getting the brick wall. We'll investigate this solution and integrate into our Windows Collectors as appropriate.
  9. LogicMonitor Collectors don't yet support Raspian OS. Our Collector has been built for the x86 CPU architecture, and there are a few tricks to get it to run on the ARM processors found in Raspberry Pi devices.
  10. The LM Config™ features are licensed separately from our core product. Reach out to our support team to learn how to get it enabled.
  11. The issue here could be that some of your Windows systems are defaulting to connect to LogicMonitor endpoints using TLS 1.0, which we no longer support. You can ensure your scripts are using a more recent version of TLS by prepending the following line of code: [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.SecurityProtocolType]::Tls11 -bor [System.Net.SecurityProtocolType]::Tls12; Hope this helps.
  12. Our apologies -- this is a product bug related to some Cisco devices sending non-standard syslog data. We're working on a fix.
  13. Eminently possible, but we don't do this out-of-the-box. You'd need to write your own custom datasource. See the example at, as well as the preceding info about writing scripted datasources, for details.
  14. We've done some in-house research into the right-sizing of the appropriate permissions for polling WMI/PDH from a remote system. Our own experience has been that we can indeed craft a set of non-administrative permissions carved out for this use-case for a given OS version + service-pack + patch-level. But that a subsequent patch may change these on any particular Patch Tuesday, which makes it pretty challenging for us to support -- or even recommend. We have an initiative in-flight with Microsoft Consulting by which we're attempting to get direct guidance from the proverbial "horse's mo
  15. Hey Matt - Note that we support monitoring of Office365 email availability & performance using our Email Service Monitoring datasources. Have a look at: for details. A number of other Office365 services can be monitored with custom service checks. More info at: -m
  16. Hi Thomas - I'd suggest having a look at to solidify the concept of "singleton" vs "multi-instance" datasources. Note that a singleton won't have an instance id, since there's only a single instance to monitor in that type of datasource. Once you have that under your belt, have a look at to understand scripted datasource modes of operation. Then follow with ht
  17. Hi Jeff - I assume you've seen our information on Collector sizing at: From a storage standpoint the Collector uses only a nominal amount of space -- only about 200MB. And disk storage is not used in normal operation because essentially all operations take place in-memory. Where the Collector may use disk is to cache collected data in case of a temporary outage between the Collector and the LM mothership. In this (typically rare) case the Collector will write collected data to disk until connectivity wi
  18. Hi Joe - Active Discovery wasn't designed for this purpose. Instead you might consider repurposing your AD script as a Data Collection script that reports the number of instances, and use the "delta" alert threshold to notify you when your instance count has changed. Hope this helps....
  19. At this time none of LogicMonitor's "core" LogicModules employ WinRM services for device polling. Although it's possible that your account may have custom (PowerShell) datasources that might use WinRM, these are likely not supported by LogicMonitor
  20. We've been working on a number of features to overhaul and streamline the LogicModule management process, including version maintenance, ease-of-import, and proactive updates. We expect to see these arrive in-product real soon. Stay tuned.....
  21. Note that LogicMonitor's RBAC system allows for the definition of any role you'd like with fine-grained detail. Feel free to create any role as appropriate for your environment.
  22. Yep -- we're working on exactly this feature, along with streamlining the overall LogicModule update process. Probably a few months out still; stay tuned....
  23. We have some Ruckus monitoring in beta. Contact support to get your hands on early-access modules.
  24. Hi Idan - In this case it sounds like what you'll want to do is create a datasource that uses JDBC-based Active Discovery to get the database name (e.g. something like "SHOW DATABASES") then use JDBC Data Collection to run your query. See: and respectively. You can then create datapoints with appropriate thresholds to generate alerts. To get the current value of the datapoint somewhere y
  25. Yup -- this has been painful as far back as when I was an LM customer a few years back. We're really excited to finally get to improve this area of the service.