Infrastructure monitoring. We have it deployed for our IT manufacturing systems deployed at plants, cloud and datacenter locations, and networking teams to replace SCOM. We like LogicMonitor for agentless server monitoring, its SaaS based, thresholds and its ability to autodiscover. We find LM lacking severely in website, network, and cloud monitoring, as well as automation as they are no longer supporting their ansible modules. When we first started with them, they had a marketing slide about PowerBi, that my manager was keenly interested in. It turned out that was not an actual feature and have since removed the graphic.
Pros
Server monitoring
Baselining performance
Simple alerting method
Easy to use interface
Forward thinking
Cons
They need to support automation like ansible, puppet, chef.
The collector agent is extremely insecure and they are making no effort to improve this design.
They only support a few collector sizes that are unable to keep up with number of devices we have.
They do not support load balancing collectors.
They are terrible at notifying when datapoints are dropped or missing.
They are not good at network equipment monitoring and aren't able to tell the difference between weighted BGP interfaces intelligently understanding traffic patterns.
They're ML story is a lie, its all based on what they call dynamic thresholds that don't really work at scale and still require manually configuring the settings.
They released LM Cloud but scoped its use case too narrow causing a really good feature to be blind to other possible uses of that feature.
It is WAY too easy for datapoints team to be messed with and broken.
Likelihood to Recommend
LogicMonitor is great for small shops or MSPs. Their ability to autodiscover devices and datapoints is awesome. There is a measure of flexibility in LM's ability to monitor and for that reason we like to say, if it can be scripted, we can monitor it.
I wouldn't use it for monitoring websites, NPM, APM, or Configuration management. Its just not well-developed in these areas. Website monitoring doesn't support synthetic logins or transactions. They actually told us we had to write our own groovy code to do this. Why should we as a customer have to learn a new programming language to attempt to login to a website? Our networking team likes LM's ability to backup the config on the networking equipment globally, but there is no ability to push the config, which almost makes it pointless according to them. NPM with LM is like pulling hair, there is no consistency and the requirements we need to get to where it is stable is daunting where SolarWinds would work right off. LogicMonitor's ability to autodiscover data is another feature that is sorely undervalued. There is a great opportunity to capture specific equipment details that they do not do out of the box and also has to be scripted.
We are using LogicMonitor to monitor and alert on a wide range of devices across our organization. From Dell servers to Nokia routers, we have no issue with setting each device up to be monitored. LogicMonitor monitors these devices and alerts on a wide array of issues. It can also be setup to monitor before there is an issue. This allows us to not only be reactive but proactive as well.
Pros
Intuitive
Cloud-based
Scope
Cons
Importing mib files
Alert tuning
Likelihood to Recommend
LogicMonitor is well suited for alerting on devices based of snmp data points. It currently is less suited for monitoring and reading syslogs, but they are working to rollout a new feature that would improve this. It is also useful for keeping config backups of many devices, via importing them through ssh.
VU
Verified User
Engineer in Information Technology (Utilities company, 201-500 employees)
