All Activity

This stream auto-updates     

  1. Yesterday
  2. At LogicMonitor, we recognize that your business and infrastructures are under increased strain due to COVID-19. To assist you in monitoring your vital infrastructure, we would like to personally invite you to join us at 11am PST, Wednesday, July 29th, for another Live Training Webinar Office Hours. Have questions about how to best use LogicMonitor? LogicMonitor experts will be live to explain best practices and answer your questions. Register now!
  3. Back at it again, we're having another Live Training Webinar to introduce some new functionality in your LogicMonitor portal. We would like to invite you to join us at 11am PST (1pm CST), Wednesday July 22nd, for another "What's new at LogicMonitor" webinar. This release is all about our Early Warning System with phase two of the Dynamic Thresholds feature. Specifically, you'll learn how you can reduce the administrative overhead of tuning alert thresholds while still getting alerts for the right metrics at the right time, in many cases with issues being caught sooner and more accurately. Register here.
  4. Also, please give us your feedback at the following link:
  5. None exists that I know of. That could be built into a property source pretty easily i think.
  6. Last week
  7. Hi. I'd like to submit a feature request to monitor the HPe StoreOnce backup appliances. Specifically Model 5200 or newer.
  8. Currently the use of ssh identities used by SSH enabled Datasources do not take into account the use of passphrases to protect the private keys e.g jsch.addIdentity(cert) rather than jsch.addIdentity(cert,passphrase) I'd like to request an enhancement that an optional passphrase can be defined as a property (ssh.cert.pass ?) which if present is passed on the AddIdentity call
  9. @dcyriac - Try this OID:
  10. Thanks everyone for attending yesterday's LogicMonitor Basics Webinar! Here's the recording in case you missed it or would like to review it.
  11. We usually bind this check to a DC, so I don't think I have run into that before. I definitely have for other stuff, like DHCP. Can't hurt to warn folks in the technical note section!
  12. I'm looking at options to provide the external IP address that a device has. Basically I would normally query a like service to get the external IP address, but I'm wondering if LogicMonitor provides a simple webservice on * that can provide the external IP so I don't have to worry about getting a 3rd party site whitelisted with our customers?
  13. Got it. I'll differ this internally, because this could be an issue for us. We've clients that don't give us ICMP access on purpose (but then we've SNMP access). Thank you for the info!
  14. 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."
  15. Ok, so I ended up doing it like this: - if(eq(snmpDown,1),2,if(un(upTime),0,1)) It does the trick, thank you! I've disabled the SNMP on the device (to force the condition), however, LM doesn't see that device as dead. What's exactly needed for LM to consider the 'Device Dead'? It relies on ICMP as well?
  16. 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))
  17. Basically I want to do what the PeerDown expression currently does: Only if the snmpDown == 0, else, return 2 (or something != than 0)
  18. Ok so I've added that try, except on the actual script. So it pretty much returns 0 if the SNMP portion goes well & returns 1 if it catches the timeout exception. Just added the actual SNMP walk code into the try{} & added the one below as catch() So now we're able to know if SNMP isn't working. I'm kinda lost on what to do at the 'PeerDown' datapoint (in terms of expressions). Can you help? Never used the complex datapoint features before.
  19. 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.
  20. Hi Team, I was getting the "No Data" on a lot of the datasources. I went through the WMI troubleshooting and made the needed changes, I did this after I ran the "Poll Now" and got a permissions error. Now I can run "Poll Now" without the error but I am getting NaN and "No data collected from sbproxy" I'm not sure what else I need to do for the data to be collected. A collector did exist on this server but was moved to another server. Before the collector was moved we did not experience this issue. Any help would be appreciated.
  21. 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.
  22. After checking the OIDs I don't believe the upTime can tell that difference. I'll try to leverage that 'general' change & see if it works for us. That's a great idea! Basically we could just add a new complex datapoint (via groovy) & try to poll a basic OID. If it doesn't return data, then assume snmp isn't replying (snmpDown == 1). From there just tweak the actual PeerDown to actually have that value in mind before returning 0. Am I in the right path? Or you had something more simple in mind? Thank you anyway for the input on this !
  23. That is my understanding too, LM has server-side logic to declare a device dead after 6 minutes (but Host Status will alert after 5min), so any alerts that occur before those 6 minutes will cause notifications. PeerDown is using the un() function so it's specifically looking if it's NaN or not. I don't know how this particular DataSource or Cisco EIGRP works so I'm not clear if upTime can tell the difference between peer down or switch down, there might be a trick to do so. But in a more generic solution and since this is a script based DataSource, I likely would add a new DataPoint and code for something like snmpDown that reports 1 if snmp isn't working (aka device will be dead soon) and then modify the PeerDown to also check if snmp is working before alerting.
  24. Hello, We've noticed the Cisco EIGRP PeerDown alarm(s) aren't being suppressed if the actual device goes down on LM. When lost SNMP connectivity to one of our routers, it started returning PeerDown alarms (since SNMP wasn't responding, causing the 'NoData' condition at the 'upTime' datapoint). This becomes an issue because the actual datapoint that checks the Peer status, bases itself on the data retrieved by the 'upTime' datapoint (which at this point, is as 'NoData). Basically, if the 'upTime' doesn't return data (which happens if the actual device goes down) it'll trigger an alarm for the PeerDown instances (since it'll always return False). LogicMonitor only sees the actual device as 'down' after 5 minutes (when not retrieving data). This DS will alarm first (since the PeerDown will return an alarm on 2 consecutive tools - which means 3 minutes). As per the documentation, all the alarm(s) emanating from the host will be suppressed. My question here (just to make sure) is, this will only be the case for alarms that hit 'AFTER' the host down condition correct? If that's true, how can we surpass this without having to increase the time that 'PeerDown' alarms took to appear in the console? Is there any type of expression that we can use in that ComplexDatapoint (instead of the current one). Because, currently the fact of this device being down, caused 100 alarm(s) on the console (since it's a central point for our EIGRP routing). Thank you! Regards,
  25. I am a big believer in having the computer do the work for me, but for website checks humans are forced to do a lot of unnecessary work to find the cause. Generally, we set overall to critical and individuals to warning. My request is that there be a method to also send the individual alerts when the overall triggers. In the absence of a dynamic templating system, the best option I can think of here is to have a way to elevate individual contributors to critical when the overall status triggers. Or, change the behavior so that the individual details are added to the generic overall status alert. Or something else -- I just don't want to have to (or tell my clients they have to) dig through alerts in the UI to figure out what is wrong.
  26. Earlier
  27. One note to add to description: Need to install the Active Directory Powershell module on the LM collector that is monitoring the AD server you are applying the datasource to. @mnagelGreat datasource thank you!
  1. Load more activity