LogicMonitor Staff
  • Content Count

  • Joined

  • Last visited

Everything posted by Jeff.Woeber

  1. Hi All One of the latest portal updates appears to have broken this propertysource. The fix is to change this line println "LMStatus="[0].hostStatus.value to println "LMStatus="[0].hostStatus; No errors are any real concerns with the break, but the device will not report as dead without this fix.
  2. WARNING - This method will deleted all existing instances along with all historical data to any devices currently being monitored. DO NOT modify the original SNMP64_if datasource. Instead clone the SNMP64_if datasource or download my copy from the LogicMonitor Exchange RX4ZAG. It's recommended to run both the original SNMP64_if and modified SNMP64_if until historical data has accumulated. I needed to dynamically group interface instances based off the description. In this case, the interface description held details regarding the interface by including DIA, UPLS, or CID.
  3. This datasource monitors higher end graphic cards via Perfmon counters available on Github from Alexey Kamenv This generates great graphs for a "Gaming Machine Dashboard" so you can visualize your complete hardware overkill LM Exchange: HMXG2X
  4. I setup a Raspberry Pi with a Sense Hat so I can track the internal Temperature and Humidity of my living room in Logic Monitor. The data is accessable from running a python script on the Raspberry Pi itself, but I didn't want to install a collector on that device. The solution I decided on was using Extend Snmp. This guide can be used as a template for similar logicMonitor task. I used Steve Francis's "How to teach an old snmpd new tricks" Blog post as a guide. The first step was creating the python script. This script reads the humidity and temperature readings from the Se
  5. This datasource uses the Weather Underground API to monitor weather conditions for multiple locations. This will require a Free Weather Underground API key. This key should be added as a device properties weather.api.key The datasource exchange locator is KT6NLM I have an example setup to monitor Austin, TX, Jupiter, FL, and Santa Barbara, CA To get started, add a new device under Expert mode and in the “Link to a URL” box add in Once the URL has been added to LogicMonitor click on “Add Monitored Instance”. Add the weatherdeatails da
  6. This is a PropertySource which runs with active discovery and adds the property auto.lmstatus to the device properties with the current Hoststatus value. It does this using the REST API and It works great with Dynamic grouping, for example if you wanted to know which device in your portal were currently in a dead status you could create a dynamic group with the applies to of “auto.lmstatus=="dead". One advantage to using a property source is if the device comes back on-line, Active Discovery will immediately run and change the property to "normal" removing the device from the group. A copy