Mike Moniz

  • Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

62 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. Does this work between collectors in ABCG? Like if a device balances to another collector or if there is a failover/failback?
  2. This is something we've also brought up with LM a few times. It seems that LM doesn't track SDT state along with the alert itself. This also makes alert reports difficult to review since we can't filter out alerts that occurred during SDT for the same reason.
  3. I agree with you, I would expect "clear" would reset to Any Time, which matches other parts of LogicMonitor also. If the link was "Reset" instead of "Clear" then I might have more of an expectation that it resets to a default set of filters/time.
  4. Also note that Datapoints can only be numbers, so you will not be able to assign a string directly like "OU=blahblah" to a Datapoint. Instead you can put that kinda data to an auto property via DataSource Active Discovery or PropertySources.
  5. Yeah, I think you need to use the custom Table type (instead of dynamic) which is much more of a pain to build and maintain.
  6. I was really looking forward for the new v.147 "Suppression Type" feature as it sounds like it will be able to filter out alerts that was suppressed and didn't generate a notification. But I was then disappointed to learn it is only available in the new Alerts page. I know it's brand new but are there any plans to expand this functionality to more places especially to reports? It would really help if we were able to generate a report for say all the alerts that occurred last week and have it exclude alerts that were in SDT at the time. Currently it can only filter out alerts that are still in
  7. You can use the !posh DEBUG command on the collector: https://www.logicmonitor.com/support/collectors/collector-troubleshooting/using-the-collector-debug-facility
  8. 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
  9. You can check your collector version under Support > Collectors. Appears this feature requires an EA (early release) Collector version.
  10. 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.
  11. @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!
  12. 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
  13. 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
  14. 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.