Pitfalls with Layer 2/3 configurations. Our shortcomings with resource allocation on certain servers.

Overall we've been pleased with LogicMonitor.

I work for an MSP Logic Monitor has greatly simplified our monitoring issues, with the ability to place a collector anywhere and that doesn't require a VPN tunnel back to our office it has reduced our firewall maintenance cost greatly. The built it SNMP mib library has saved us countless hours trying import MIBs and trying to decide what to alert on. There are a few features that I would like to see implemented in a logic monitor, the ability to tie devices together so that if an ISP goes down we get one alert not 20 separate alerts for each device at that location. I would also like to see the creation of data sources be simplified, recently I attempted to create a data point that reported on a string and found it extremely difficult to have it report on more than one variable.

Pretty freaking awesome.

Our use case is centered on routers, switches, wlan and other infrastructure hardware components of the service-delivery stack as opposed to servers, applications, etc. Based on LogicMonitor's performance to-date, I would fully expect that we will expand its role. In selecting LogicMonitor, we heavily weighted factors related to administrative overhead and convenience. On both counts LogicMonitor gets the highest marks: 1)We no longer spend time installing a bloated monitoring application on a server (physical or otherwise) or fighting to upgrade any part of the application's components. 2)We no longer spend time sustaining remote access mechanisms that make it cumbersome to view our monitoring data...wherever and whenever that data is needed, a browser is all that is required. I highly recommend LogicMonitor as a source of powerful and valuable insight that can be leveraged to maximize the ROI of your IT service-delivery stack.