Matthew Dunham

LogicMonitor Staff
  • Content count

    57
  • Joined

  • Last visited

Community Reputation

100 Excellent

About Matthew Dunham

  • Rank
    Community All Star
  1. Converting Octets to Mbps/Kbps

    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.
  2. Converting Octets to Mbps/Kbps

    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 https://www.logicmonitor.com/support/datasources/creating-managing-datasources/normal-datapoints/ for details, but the short version is that these two datapoint types subtract the current value from the previous value and then divide by the configured polling interval to give you a measurement in units/sec. Then to do the multiplication above, you can use a Complex Datapoint to translate bytes/sec (octets/sec) to bps https://www.logicmonitor.com/support/datasources/creating-managing-datasources/complex-datapoints/. LogicMonitor graphs can auto-scale for you, so we'll handle the Kbps / Mbps / Gbps conversion for you as needed. For Fortinet gear, you might also have a look at our "Fortinet Fortigate Interfaces" LogicModule -- it does all this for you (and more).
  3. 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.
  4. 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?
  5. PSA: Collect from windows systems without admin rights

    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.
  6. 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.
  7. Using ConfigSource

    The LM Config™ features are licensed separately from our core product. Reach out to our support team to learn how to get it enabled.
  8. 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.
  9. Cisco Syslog will not work

    Our apologies -- this is a product bug related to some Cisco devices sending non-standard syslog data. We're working on a fix.
  10. ns_lookup

    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 https://www.logicmonitor.com/support/datasources/groovy-support/dns-scripting-methods/, as well as the preceding info about writing scripted datasources, for details.
  11. Read only agent / collector

    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 mouth" on how best to right size these permissions in a future-proof (or at least future-resistance) way. Stay tuned....
  12. Office 365 Monitoring in LM Cloud

    Hey Matt - Note that we support monitoring of Office365 email availability & performance using our Email Service Monitoring datasources. Have a look at: https://www.logicmonitor.com/support/monitoring/applications-databases/email-service-monitoring/ for details. A number of other Office365 services can be monitored with custom service checks. More info at: https://www.logicmonitor.com/support/services/adding-managing-services/adding-a-web-service/ -m
  13. What is my Instance ID?

    Hi Thomas - I'd suggest having a look at https://www.logicmonitor.com/support/devices/device-datasources-instances/device-datasources-instances-overview/ 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 https://www.logicmonitor.com/support/datasources/data-collection-methods/scripted-data-collection-overview/ to understand scripted datasource modes of operation. Then follow with https://www.logicmonitor.com/support/terminology-syntax/scripting-support/external-scripting/ which provides a simple example of putting together a scripted datasource. Hope this helps. -m
  14. Collector Sizing

    Hi Jeff - I assume you've seen our information on Collector sizing at: https://www.logicmonitor.com/support/settings/collectors/collector-capacity/ 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 with our service platform is restored, at which point this cache will be flushed such that any consumed storage will be freed.
  15. 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....