Mike Moniz

  • Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

56 Excellent


About Mike Moniz

  • Rank
    Thought Leader

Recent Profile Visitors

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

  1. You can use the !posh DEBUG command on the collector: https://www.logicmonitor.com/support/collectors/collector-troubleshooting/using-the-collector-debug-facility
  2. I've discovered an issue with the new SNMP_Network_Interfaces DataSource if it finds that a device returns MAC addresses in STRING (binary) format instead of the more typical HEX-STRING ("xx:xx:xx:xx:xx:xx") format. You can see the issue if you walk . and see MAC addresses that look like "Lr 3a#". We found this was happening to only a very few Cisco switches out of hundreds but when it happens the interface instance doesn't show up in LogicMonitor. I was able to add some code to the DataSource AD script to account for the problem as shown below. We have not yet implemented a
  3. You can check your collector version under Support > Collectors. Appears this feature requires an EA (early release) Collector version.
  4. LogicMonitor doesn't prevent multiple protocols per device, many devices might use lots of different protocols, but instead LM uses "AppliesTo" conditions to determine what checks get applied. Some of them may have !windows() to they don't apply to Windows servers but like in this case, Windows or it's apps can support SNMP. I would just disable the duplicate checks at the device or group level.
  5. @Andrey Kitsen I'm unable to load the two PropertySources as they report "LogicModule belongs to another private repository". I was able to load the DataSources though. Thanks!
  6. You can't, it's specifically blocked to prevent loops. What are you trying to implement? There might be some tricks like the system.staticgroups mentioned below. https://www.logicmonitor.com/support/devices/device-groups/device-groups-overview
  7. You're right. It's documented in the older APIv1 documentation at https://www.logicmonitor.com/support/rest-api-developers-guide/v1/devices/about-the-device-resource . The old documentation is still important even for v2 context. sdtStatus: This parameter has three values separated by ‘-‘. The first value indicates whether there is an active SDT for a group the device belongs to, the second value indicates whether there is an active SDT for the device itself, and the third value indicates whether there is an active SDT for a datasource or instance on the device
  8. Respecting RBAC would fix this issue for me as none of the users adding devices have access to root group. I'm basically forced to ban people from using the wizard as a policy but I can't enforce it and so still happens once in a while.
  9. Please stop having the wizard add snmp and esxi and other properties to the root group when using the Add Device Wizard or respect RBAC permissions for users running the wizard. We try to use SNMP v3 when possible with all our customers and that doesn't uses the snmp.community property. But if someone uses the wizard for a completely different customer for v2c, it sets snmp.community on root and via inheritance to all other customer's devices and it breaks them. We or our customers then get a bunch of false No Data alerts as LM switch over to using v2c, even with v3 creds provided or our
  10. You can always add the "Linux_SSH" category to the devices or groups manually if you don't want to remove existing categories or modify the propertysource.
  11. I don't believe LM has device detection that uses SSH so wouldn't fill in the system.sysinfo and the like. I ended up just adding !hasCategory("Linux_SSH") to the my Minimal monitoring check AppliesTo to exclude them when I have to use SSH for Linux. https://www.logicmonitor.com/support/devices/adding-managing-devices/how-does-logicmonitor-know-what-to-monitor-for-a-device "When a resource is added into monitoring, LogicMonitor immediately runs a series of queries using WMI and SNMP to determine basic system information about the resource such as operating system version, IP address,
  12. DataSources are really designed for numeral performance or status data. I would suggest you look at PropertySources instead. That provides a method to store strings as "auto properties" that you can find in the INFO tab. https://www.logicmonitor.com/support/logicmodules/propertysources/creating-propertysources
  13. When I lasted looked at it SN didn't have the built in hash function to implement the auth needed for LM. If you install the "LogicMonitor Incident Management Integration" add-on from the ServiceNow store, It provides some supporting script includes functions you may be able to use.