Jessie Bryan

Members
  • Content Count

    29
  • Joined

  • Last visited

  • Days Won

    4

Community Reputation

4 Neutral

1 Follower

About Jessie Bryan

  • Rank
    Community Whiz Kid

Recent Profile Visitors

561 profile views
  1. Extending alert information from LogicMonitor to other 3rd Party systems is pretty common for us, however, the available tokens today to describe the alert is missing a few bits of data (we feel). It would be incredibly helpful to have an alert token that contains the LM User responsible for Acknowledging the alert, and a separate token for the Ack comment. Having these tokens allows us to better map alerting details to upstream and downstream integrations.
  2. If you're using NET-SNMPd you can use IP-MIB::ipAdEntAddr and IP-MIB::ipConnState to obtain IPs and Port numbers that are in LISTEN state. The rest is pretty straight forward.
  3. Hello, It's come to my attention that when a host in LM is down, it's alerts are not cleared when a user deletes the host from the GUI. We rely on external alerting providers (OpsGenie, PagerDuty, etc.) and these Integrations have no knowledge of the host being removed, so the applicable alert(s) remain active. I am requesting LogicMonitor to send alertstatus = clear for any alerts attached to a down host once the host is removed from the system.
  4. The number of consecutive violations multiplied by the DS polling frequency will help map out firing an alert over X minutes in age. If you specify multiple severities in the dataPoint threshold, be advised- if the severities are "too close" to each other, then the calculation is reset if a polled value jumps into a new severity (this is true in both directions: warn->error->critical and critical->error->warn). For myself, I'd love to see thresholds updated to have a more structured scripting language so I can eval last X values to determine when to fire the alert. Zabbix NMS has this (https://www.zabbix.com/documentation/2.4/manual/config/triggers/expression)
  5. Matt is right, there is a simple SSLCerts- DS in the repository. For us, we needed to have a DS with multiple SSL instances and Active Discovery, since our servers have multiple websites/certificates. There are a few ways do to this. I wrote an Active Discovery script in groovy that SNMP Walk IP-MIB::ipAdEntAddr and IP-MIB::ipConnState of the server to automatically find websites based on common SSL Ports (We only use 443), then return the list for monitoring. We then built a dataPoint to fire when the number of days remaining on the given cert is 60 days or less.
  6. Hi Michal, I create do not alert on No Data for my dataPoints, with the exception of one dedicated dataPoint that is meant to tell us about SNMP. More info in here:
  7. I wanted to find out if any LM Admins have started using IPv6 to monitor your servers/apps/networks. AFAICT, LM Services are not IPv6 supported at this time, and Collection Reporting to LM Data Center is strictly IPv4. Just curious if anyone is actively using it, and what experiences you've had.
  8. Yeah, that something I investigated. It doesn't look like Java has native support, and a wrapper library is necessary. I'd prefer to code it agasint LogicMonitor's Ping library that already parses Windows and Linux Ping output, but if I have to I'll write my own. Thanks Matt!
  9. I've run into the same issues. At a minimum, I've asked LM to inform the operator that the rename may have impacts to Alerting, Groups, Dashboard Widgets, etc. I'm not sure (especially with globs) if LM can "auto-correct" these mappings on a rename, so just informing the operator for me is a great start.
  10. I haven't seen any discussions about DS/ES API support. You can clone dataPoints, then edit the name and the key-value pair. It's slightly faster than fully manual. I too would love DataSource and EventSource management from API.
  11. Have you tried assigning an escalation chain to the collector in Settings -> Collectors -> Select your Collector -> Manage -> "Escalation Chain". If you do this, you'll receive an Agent alert (LMAx where x is the collector-id). Also, if you set up collector failover (from the same screen), you'll see an LMFx (failover alert) from this collector.
  12. We have many SNMP DataSources. For us, we do not alert on "no data" except for one purpose-built dataPoint we call SNMPHealthCheck which *does* alert if no data. That way, it can signal to us that SNMP may be in trouble vs. the monitored resource.