Michael Rodrigues

LogicMonitor Staff
  • Content count

    55
  • Joined

  • Last visited

Community Reputation

100 Excellent

About Michael Rodrigues

  • Rank
    Community All Star
  1. Issues With Creating A Datasource

    Taking Mike's advice, you might just try swapping out your filter string with the URLEncoded version: "startEpoch%3E%3A1538370000%2CendEpoch%3C%3A1541048399%2Ccleared%3A*"
  2. SNMP Trap Event Consolidation

    Reviving an old thread, but we're currently reevaluating EventSource suppression logic. Some of the other EventSource types already use a timeout like mechanism to avoid duplicates, but we don't do anything like that for SNMP traps. The general idea right now is to let the user decide which duplicate fields indicate a duplicate event, and suppress anything within the "effective interval" of the original alert. I think it makes sense to have the timer reset logic be optional. I also like the idea of providing more visibility on how many events were suppressed. We've also had a fair number of requests for a mechanism like the DataSource "trigger interval", where we only trigger an alert if we see the same event N times in the interval. Anyways, any additional feedback is appreciated.
  3. What Is My IP as found from a Google search

    @wanabeninja@helient it should be out out of the review holding cell now. I can't imagine Google would have done anything to break this. It works for me. Those hosts/customers aren't behind the same NAT gateway, are they? Or using a shared proxy? Have they tried other sites that do this to see if they get the same result? I was always partial to ifconfig.me, and ipchicken.com, though please don't take that as an official LM endorsement :).
  4. 497 days and counting........

    @Kwoodhouse the one that includes the fix is SNMP_HostUptime_Singleton. It requires the addCategory_snmpUptime PropertySource to work without manual intervention. "HostUptime-" (no space) is deprecated and no longer in core. Unfortunately there's no way for you to get that information in your account currently. SNMPUptime and SNMP_Engine_Uptime- are more or less duplicates. They both get the uptime for the agent, not the host. This seems to be an oversight. Originally, we just looked at the uptime counter with a gauge datapoint. If the value indicated uptime of less than 60 seconds, we'd alert. Of course, this happens during a counter wrap. To fix it, we started tracking the uptime counter with a counter. Given that the rate of time is constant, we should always see the rate of 100 ticks/second coming back from the counter datapoint if the host hasn't been rebooted. The logic in the UptimeAlert CDP looks at both that tick rate, and the raw uptime to determine if the host has rebooted, or the counter has just wrapped. If it's just a counter wrap (no reboot), we'll see 100 ticks/second, even if we see less than 60 seconds of uptime with the gauge. If it's rebooted, the UptimeCounter datapoint could return either No Data (counters need 2 consecutive polls), or, it will return a huge value because no polls were missed, and LM assumed the counter wrapped when it was really reset due to reboot. This is explained in the datapoint descriptions, but is admittedly a bit difficult to grok without an intimate understanding of how LM's counter/derive work. I do still think it's a rather ingenious solution. We use "102" instead of "100" ticks/second in the CDP to avoid false positives, as the collection interval isn't always exactly a minute. I recommend this blog if you're interested in learning more about counter/drive: https://www.logicmonitor.com/blog/the-difference-between-derive-and-counter-datapoints/ I will talk to the Monitoring team about removing some of those duplicates, and getting a public document up explaining it all.
  5. DataSources_List PropertySource

    @pperreault it should be out of security review now.
  6. Monitor File System - extend the built in UNC monitor

    This module should be out of security review now.
  7. VMware VSAN

    We have some vSAN LogicModules in the pipeline but we've been waiting to complete and release them until we after we release our update for the base VMware modules. There isn't currently a plan to pull the vCenter-defined alerts through directly. We'd prefer to pull the metrics out and define the alarms within LogicMonitor to avoid noise and allow configuration within the product. That being said, if there's enough interest in just pulling VMware's alarms through we can look at that too.
  8. Scripts for deleting datasource instances

    Hey @BrianG, you're talking about device instances, right? If they share a common property or name you can make a Dynamic Group that holds them all, then deletes that group. When you delete it, you can delete the devices from the account along with it.
  9. DNS Domain registration expiry

    @Mike Graham, try this updated version: 37WCMA
  10. Hi @Archana, check Visual Average for the general trend over the month. Given you're looking at CPU usage, it's probably also worth taking a look at the VaST version to see if you're getting lots of spikes. You won't see the spikes with Visual Average, but it will be harder to see the trends in VaST view.
  11. Hi @Archana, I think we do what you're looking for, but the feature is sort of hidden. Open the expanded graph, then expand the instances pane at the bottom. On the right side of the instance pane, there's another downward pointing arrow. If you click on that arrow and select "Show Boundaries' you'll see min/max/avg for each instance for the selected time range. You may have to aggregate instances into one to get the average across multiple instances.
  12. Hi @Archana, there's a great blog entry about VaST here: https://www.logicmonitor.com/blog/vast-opportunity-with-logicmonitor/ Generally, you'll want to go with VaST when you're looking at a longer time frame, and if you're concerned about seeing peak utilizations that would otherwise be hidden with "visual average". The visual average option is better when you're just looking for trends.
  13. Cisco EIGRP Peers

    Hey @Richard Collisn, thanks for this, we'll include this fix in the version in core.
  14. Scripts for deleting datasource instances

    Hey @BrianG, I don't have a script for you, but I wanted to see if you could expand on this. Are you clearing out old instances or something? AD filters and instance deletion options should be able to solve most instance deletion needs, so I'm curious about what's going on on your environment.
  15. Certificate Expiration Notification

    Hey @ugamike, we do ship a DataSource called "SSLCerts-" that will do this for you. If your hosts with the management webservers are already in monitoring, the SSLCerts- module should already be applied and monitoring them.