Matthew Dunham

LogicMonitor Staff
  • Content Count

    60
  • Joined

  • Last visited

Community Reputation

100 Excellent

2 Followers

About Matthew Dunham

  • Rank
    Participant

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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. 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
  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. 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.
  5. 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.
  6. The LM Config™ features are licensed separately from our core product. Reach out to our support team to learn how to get it enabled.
  7. 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.
  8. Our apologies -- this is a product bug related to some Cisco devices sending non-standard syslog data. We're working on a fix.
  9. 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.
  10. 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 ht
  11. 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 wi
  12. We have some Ruckus monitoring in beta. Contact support to get your hands on early-access modules.