Rodger Keesee

  • Posts

  • Joined

  • Last visited

  • Days Won



3 Neutral

About Rodger Keesee

  • Rank
  • Birthday 07/13/1967

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Collectors are often physical devices that need to be located onsite. We have over a hundred collectors to keep track of. We keep notes about each collector's location in a separate system but this is error prone and time consuming to synchronize. It would be much more convenient if we could keep notes about a collectors geographic and physical location in LM.
  2. Thanks for the speedy reply Sarah. I think what I want is simple: I want to capture both Warning and Error types in the same Eventsource. So previously I would modify a Windows Eventsource to have the filter "LEVEL More urgent than Information". The way the interface is now, I need to create two different Eventsources, one for LEVEL Equal Error and LEVEL Equal Warning. Are you saying that removing the LEVEL filter is the same as showing all Warning and Error events? It's extra confusing because when I create a new Eventsource the filter is set to LEVEL More urgent than Information. But with this interface change, I can never set an existing Eventsource to that. Ya know, I've heard from multiple sources that this is just the way it is and to get used to it. I'm bummed at this pointless interface change (because it wasn't harming anyone before) but I can work around it by creating twice as many Windows Eventsources as I previously needed to.
  3. From the v75 release notes. "Information, FailureAudit and SuccessAudit have been removed as options for the Windows Eventsource Level filter. Level filters set to these values always had to be used in conjunction with an event ID, making them superfluous." This is a bad change. It wasn't superfluous, it was clear interface design. Here's the unintended consequences to this change: 1) I can't have a single windows event datasource that shows both warnings and errors unless I create a new datasource and not change the filter from the default. 2) Why have a “more urgent than” setting when it doesn’t do anything? See the table below 3) There is no way to set an existing datasource back to the default (more urgent than information) once it has been modified. Here are the options that are possible after the change in the interface. Datasource filter setting What is alerted Notes LEVEL More urgent than Warning Will only alert on Errors Pointless because it’s the same as below LEVEL More urgent than Error Will never alert on anything Pointless because it never alerts LEVEL Equal Error Will only alert on Errors
  4. The SSL Certs- DS works perfectly for our needs. Discovering certs we didn't know existed in new environments. Thanks LogicMonitor!
  5. Wuut! I searched the documentation (and the forums) and found no mention of this awesomeness. I'll try it out immediately.
  6. Some other monitoring tools provide SSL certificate monitoring to alert for expiring certs. Really wish LogicMonitor had this. +1 if I could use a collector to monitor for private SSL certs that aren't accessible publicly (like for RDS and the like).
  7. I often like to submit feedback on LogicMonitor support tickets but I forget what I wanted to say by the time the \'\'we want your feedback\'\' email is sent. Also I\'m not sure what email corresponds to what support case and I don\'t want to spend the time looking up my case history. I request a way to submit support feedback via a form on the website. Even something as basic as an email address would be ok. You\'d get more feedback from me and could improve faster.
  8. Thanks for this info everyone. At the moment we are stuck with installing PingPlotter on a desktop at each clients LAN - obviously this solution sucks and isn't scalable to the 100 networks we need to monitor. We have demoed Appneta but at a minimum of $7000 per year for only 3 sites it isn't a good ROI for our limited need. I assume everyone in IT has the need to measure and alert on network health so I feel like I'm missing something. Here's the only choices I see: 1) buy and install Cisco or Juniper equipment and use LM to gather Netflow data 2) use Ping datasource to measure ICMP latency as the only indicator of network health 3) purchase enterprise-grade network health software completely outside of LM 4) invent network health monitor software that runs as a virtual machine appliance and reports Netflow and SLA data (ideal, but non-existent)
  9. Thanks Jeff and Steve. We use ping now (and will add ping-multi). But I dont have to tell you you guys what a blunt tool ping is. We have Meraki (a Cisco product) at most clients but that doesnt provide NetFlow stats. Does LM support other standards like sFlow, OpenFlow, IPFix, and jFlow?
  10. Hey guys, We have the need to measure network health from our clients' LAN to our datacenter and vice-versa. We'd like to gather QoS, UDP, and TCP stats (jitter, RTT, loss, etc). The network health monitoring tools I've tested duplicate a lot of what LogicMonitor already does for us (alerting, collecting, reporting, etc). What do you guys use to monitor network health that also leverages the power of LogicMonitor? Software that we could install on a desktop would be great.
  11. Hi Steve, rnI exaggerated about it taking me a few hours, but it felt like it. I like the cascading SDT feature very much where I can apply SDT by groups and have servers in multiple groups and thus have aggregated SDTs - its really useful. The reason it took me so long is (1) we intended to tune SDT for each server by its network, role and its boot order. The lack of visibility of the aggregate SDT made me give up on that and do a more one-size-fits-all approach and (2) the form often would not save my numbers and instead saved it as an all day outage (using Chrome on Win8.1). RE (1): I may be missing something, but the only way to determine the SDT on a particular server is to right click it, choose SDT and then click the tab to see SDTs affecting this object.
  12. SDT management and entry is very time-consuming. As a new user, I just spent a few hours setting SDT for our servers (around 100) and in our previous monitoring system this would have taken about 10 minutes. As a start, create a single screen that shows the SDT for all hosts. More importantly: the SDT form does not save the correct schedule about 20% of the time and instead saves the item as an \'\'all day\'\' outage. This is bad.
  13. The prompt for authentication is enough to tell if the website is up or down. The services, as you have them, cannot monitor websites that require client-side auth and so we have to use another solution.
  14. 'Alert Cleared' messages follow the same escalation chain as the original alerts, this is awful for an after hours team. We would like 'Alert Cleared' alerts to be sent only via email and not follow the same path as the critical outage alert. Otherwise, it results in everyone being woken up to be told that 'everything is fine'.