Mike Moniz

Members
  • Content Count

    181
  • Joined

  • Last visited

  • Days Won

    31

Community Reputation

50 Excellent

3 Followers

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'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
  2. 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
  3. 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.
  4. 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
  5. 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.
  6. 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,
  7. 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
  8. 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.
  9. Just to keep in mind and for others searching the forums, Host Status will tell you if a device stop responding to the collector, not necessarily if the server rebooted. It's possible you can get a host down alert due to something like a network issue, especially if you have to monitor over a vpn connection. The Uptime check can be used to alert on real reboots since it reports the time since the last reboot and you can alert if the uptime is less then X seconds for example. This can also catch situations where you VM reboots very quickly (< 1 minute) where it's possible monitoring will not
  10. I'm looking at options to provide the external IP address that a device has. Basically I would normally query a WhatIsMyIP.net like service to get the external IP address, but I'm wondering if LogicMonitor provides a simple webservice on *.logicmonitor.com that can provide the external IP so I don't have to worry about getting a 3rd party site whitelisted with our customers?
  11. It will rely on ICMP and other things too... "...the idleinterval datapoint within the HostStatus DataSource measures the amount of time in seconds since the LogicMonitor Collector was able to collect data from your host via built-in collection methods (SNMP, Ping, WMI, ESX, etc.)... Note that data collected by script DataSources does not affect the value of the idleinterval datapoint." https://www.logicmonitor.com/support/logicmodules/datasources/creating-managing-datasources/host-status-host-behavior/
  12. You can nest if's together in the same kinda way you do in Excel. This is just off the top of my head and untested, but you would do something like: if(snmpDown,1,if(un(upTime),0,1))
  13. Check the system.collectordesc property on the INFO tab for that device and make sure it's pointing to a valid working Collector. If it's not, then Manage the device and change the collector assignment there. Either way if this device use to be a collector, then you likely want to remove the "collector" category also.
  14. That's the basic idea. You can't make complex datapoint via groovy so snmpDown would be a normal datapoint which you can then refer to it in PeerDown. Also I think you can just wrap the snmp.get/walk line or section in a try/catch and that will let you know the snmp request failed.