My main use case for LogicMonitor is enterprise monitoring, specifically infrastructure monitoring, and cloud, so hybrid monitoring. For hybrid monitoring, we monitor services that are running in the cloud amongst all three providers, whether it's GCP, AWS, or Azure, as well as infrastructure in our data center and at our various locations as well.
Infrastructure Monitoring and Observability Platform
LogicMonitorExternal reviews
External reviews are not included in the AWS star rating for the product.
Has reduced mean time to resolution by expanding visibility across hybrid environments
What is our primary use case?
What is most valuable?
The best features LogicMonitor offers include the single pane of glass, the constant improvements to the features within LogicMonitor, as well as the excellent support and the ability to actually get hold of the developers of their specific products or features within the tool.
The single pane of glass feature helps my team day to day by allowing us to look at all our specific areas in one view, in one tool, even though it's infrastructure for various departments or various teams; with that, they can see their own systems within LogicMonitor, do reporting, graphing, dashboarding, etcetera.
LogicMonitor has positively impacted my organization by being up to date with all the latest features and capabilities, so as our organization develops cutting-edge systems, whether internal or third party, we can always rely on LogicMonitor to provide proper enterprise level monitoring and observability.
LogicMonitor has expanded our view of our systems and has reduced our mean time to resolution, as now engineers that work on specific issues are able to very quickly identify what the cause is.
What needs improvement?
LogicMonitor can be improved by having more meetings with customers to find out what they really need and perhaps also by providing feedback on feature requests to see where the feature requests actually sit in their development queue.
For how long have I used the solution?
In my current field, I've been working for more than twenty years.
What do I think about the stability of the solution?
LogicMonitor is stable.
What do I think about the scalability of the solution?
LogicMonitor scales well; however, the need to assess the load on collectors is a bit cumbersome.
How are customer service and support?
Customer support is good, but escalations within customer support are not so good.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I previously used a different solution, but I cannot say the name, and it wasn't up to date with current technologies and did not align with our observability requirements.
What's my experience with pricing, setup cost, and licensing?
I experienced no issues with pricing, setup cost, and licensing; it was very transparent, and the licensing model is very clear and easy to understand, with the exception of the cloud licensing, which is a bit confusing.
The cloud licensing is confusing due to the way resources are counted; they have an algorithm or method that they use, but it's not shared or easily determinable for me to ascertain what the actual cost is based on my usage.
Which other solutions did I evaluate?
Before choosing LogicMonitor, I evaluated other options, but I cannot disclose what those other options were.
What other advice do I have?
On a scale of one to ten, I would rate LogicMonitor an eight. I choose that number because it's above average, but they still haven't quite reached the level of features required for it to be a complete single pane of glass; for example, the APM feature is not quite as developed as Datadog.
My advice for others looking into using LogicMonitor is to assess what your needs are, whether the features align with your company's design, as well as what your company actually requires from the tool, since LogicMonitor is designed for full level observability, so it's pointless getting it just to monitor three servers; we're looking at enterprise-level monitoring here.
I would rate LogicMonitor an 8 out of 10.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Has improved issue resolution with custom monitoring while needing better support for cloud and containers
What is our primary use case?
LogicMonitor is our network and systems monitoring tool. It is primarily for our on-premises infrastructure, including firewalls, routers, switches, servers, both physical and virtual, storage systems, and anything in between. We do a little bit with SaaS solutions and cloud, but LogicMonitor really shines for on-prem solutions.
Primarily, it determines when a server is up or down. It is also helpful to correlate multiple different alerts together. If I see one server down at a branch location and I can go in and quickly check that the router is also down, that would tell me the circuit or the power is probably out at that location. This helps me narrow down what I need to work on.
It is a really solid tool for the on-premises, physical and virtual infrastructure. I have had nothing but good things to say about it, and it has been a pleasure using it for those use cases.
What is most valuable?
I love the idea of how the monitoring scripts are built. LogicMonitor is made up of Logic Modules with different types. Primarily, users work with data sources. The Logic Modules are written in Groovy programming language. The script goes out and does whatever it needs to do to authenticate, which may be a custom situation for every type of different device. It authenticates, and within the logic of the script, it knows how to pull the data and output it to standard out in a standard format.
This is really powerful because it allows you to look at the code that LogicMonitor's own engineers have written for all of the various different out-of-the-box solutions. For example, with VMware vSphere, they have probably a dozen Logic Modules. If you need to troubleshoot, or if the Logic Module does not work exactly as needed, you can go in, look at the code, and fork that Logic Module to adjust the Groovy code to do exactly what you need.
I was able to create ping monitoring of every virtual machine in our vSphere instance. I did not want to pay for a separate LogicMonitor license for certain servers where I only needed to know if they were up or down. I built a custom Logic Module that operates off of all the VM instances within Vcenter and performs a ping every minute. We use that primarily to determine up-down status for all of our VMs.
For our colocation facility, which has an API, we wanted to monitor certain events, such as when someone enters our cage. I wrote a custom event source which queries the API periodically. It looks for new entries into our cage, and if it finds one, it creates a LogicMonitor alert that gets delivered to all proper stakeholders so we know when someone enters our secure location.
What needs improvement?
The hardest part about LogicMonitor is its current support for cloud, SaaS, and container monitoring. The on-premises network monitoring tools are stronger than some of the more modern things we need to monitor in the IT landscape. With cloud monitoring, all metrics are pulled directly from Azure, whatever Azure provides. There is not really anything custom. There are no Groovy scripts or anything custom that can be customized for cloud monitoring.
The container monitoring seems to be really behind compared to some bespoke cloud-native monitoring solutions that are designed around Kubernetes, containers, and ephemeral environments. LogicMonitor does not shine as well in these more modern IT systems.
The product is not as mature in these areas. During our trial, I developed quite a list of different issues and bugs. While we could deal with or work around each issue individually, the combination of all of them together made me less excited to move forward with a monitoring product for containers. Being that it was a separate cost requiring procurement, we opted not to proceed at that point. We are still in the market and looking around. We may do another trial of LogicMonitor container monitoring in the future, but it is not number one on our list.
For how long have I used the solution?
I have been using this solution for at least five years.
What do I think about the stability of the solution?
It is very stable. I have never seen LogicMonitor itself go down. I have seen issues where our collectors stop working, but I think that is potentially due to issues with our own infrastructure and not necessarily their software. In terms of their cloud-hosted portion, it is extremely solid. I have never had any issues with it.
What do I think about the scalability of the solution?
Their model assigns monitor devices to a collector, and you can scale out collectors as much as you want. They are not licensed, so you could deploy one collector or 1,000 collectors for the same cost. As your company grows, you are able to scale effectively by just deploying additional collector machines.
How are customer service and support?
Thankfully, I have not had to open many support tickets because the product mostly just works without issues. For the few times that I have had to open a ticket, they have been helpful. I have found that they are less likely to want to jump on a call. I appreciate when support at other companies is quick to say, "Let's jump on a Zoom call and work it out." With LogicMonitor, they really want to try to keep the conversation over email and tickets as long as possible. Sometimes that can prolong the support experience, but overall, the support experience was good, and I usually always got what I needed from the support engineers.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We did not have previous solutions. We might have evaluated one or two options, but it was primarily LogicMonitor because some team members had prior experience at previous employers and there was not really anything else that caught our eye or that we thought was worth looking at.
What was our ROI?
I do not have any specific metrics because we do not record that information, but I can definitely notice a difference in our posture, uptime, and ability to solve problems and resolve outages much quicker since we have had LogicMonitor in place.
We have felt improvements in our ability to solve problems quicker and diagnose issues faster. Overall, it makes our jobs easier, though I do not have any hard numbers to share.
What other advice do I have?
If you need a traditional on-premises monitoring tool for your physical and virtual infrastructure in your own data center, it is a great solution. If you are primarily a public cloud user, you should probably look at another solution.
On a scale of 1-10, I rate this solution a 7.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Reliable and Comprehensive Monitoring Solution
The platform’s detailed performance insights also support capacity planning and resource optimization, ultimately improving overall system reliability and efficiency.
Has improved service reliability and reduced downtime by providing full visibility into infrastructure
What is our primary use case?
My main use case for LogicMonitor is monitoring almost all devices, including servers, VMs, data backups, network endpoints.
A primary use case for LogicMonitor is in hybrid environments, specifically in Microsoft ecosystems for monitoring servers and VMs by collecting performance metrics such as CPU, memory, disk, network latency, application throughputs, and to help avoid downtime and performance degradation by spotting trends and anomalies.
LogicMonitor allows me to model key business services, define underlying infrastructure components such as databases, networks, and applications, and helps me to show the health of services based on the health of its parts. It gives me business connection awareness so that my team and I can instantly see if a service used by customers or our own staff is impaired and be quick to identify the root cause component.
What is most valuable?
The best features LogicMonitor offers include metrics that are automated discovery and monitoring, which is the biggest time saver. Once you deploy the connector in a network, it automatically discovers devices and applies the appropriate monitoring templates, which are the modules, and eliminates almost all manual configuration work, so we don't have to write scripts to monitor new servers or devices, and everything shows up on the dashboard for monitoring.
The unified dashboarding and customization are highly flexible, allowing me to create everything from high-level executive views to deep dive technical troubleshooting views. The pre-built LogicModules are good out-of-the-box, and although there are many, they are a time saver.
LogicMonitor has positively impacted our organization by especially improving service reliability and user experience. The dynamic alerting and root cause analysis have helped us fix issues before they cause a full-blown outage or degrade performance for end users. When an incident occurs, we can use the topology maps to pinpoint the root cause in minutes instead of hours, minimizing business disruption. The strategic alignment and risk management has made our IT become a business partner as opposed to just a cost center.
What needs improvement?
I wish the user interface would be customizable to allow users to create personal context-specific workspaces to hide irrelevant data, rather than trying to have a one-size-fits-all interface. This would go a long way, as would introducing a usage-based pricing model for data ingestion, per GB of metrics or logs alongside a device-based model similar to New Relic, which would be more attractive for cloud-native companies with dynamic infrastructure.
While dynamic alerting is great, the overall alerting system can be complex to configure. If LogicMonitor looks into going beyond the topology-based correlation to include AI that can group related alerts from different parts of the stack into a single probable cause incident, that will significantly improve the system.
For how long have I used the solution?
I have been using LogicMonitor for three years now.
What do I think about the stability of the solution?
LogicMonitor is stable, 100%.
What do I think about the scalability of the solution?
LogicMonitor's scalability is very satisfactory.
How are customer service and support?
Customer support is on point and very well trained. I have interacted with their support team and had a good experience.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I previously used DataDog but switched due to the complexities and pricing.
We switched from DataDog to LogicMonitor because of the complexities, pricing model, and predictability. LogicMonitor gave us a device-based pricing model that is highly predictable for our organization, which is key.
How was the initial setup?
I had a few challenges with pricing and setup cost, but with the help of their sales executives, we were able to have a straight path on what to purchase and get. We used the core pricing model which was device-based licensing, straightforward, although the complexity and unpredictability of cloud resources made it harder for us to go for cloud, but we had a smoother experience with the help of the sales executives.
What was our ROI?
The return on investment focuses on risk mitigation and operational efficiency to enable the business to run. The return is more of value and savings in preventing costly downtime, making the savings of about $60,000 which we would have lost without LogicMonitor, and in IT staff efficiency, we save approximately 15 hours a week.
From the time we started using LogicMonitor, it has reduced downtime significantly to about 60-70%, and in terms of business operations, the time to recover and time to get users up and running has reduced dramatically, almost 60%. It has enabled us to prevent more losses, saving the organization about $60,000 over the past year, had those incidents occurred.
Which other solutions did I evaluate?
Before choosing LogicMonitor, we evaluated Sentinel, which was too expensive, and another major player, but we wanted something that had cost predictability.
What other advice do I have?
I would advise others looking into using LogicMonitor that if they are looking for something stable regarding stability and price-wise, they should consider it. On a scale of 1-10, I rate LogicMonitor an 8.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
LogicMonitor: When AI Watches Your IT
Great network monitoring tool with cloud integrations
More than just SNMP polling
First time Logic Monitor user
Initial learning curve to get started is low. More advanced features require more time to get familiar with.
Ability to create custom modules
Update frequency of modules not always following the latest available versions of systems/applications to be monitored.
Some feature limitation (for example maximum 15 Log pipelines)
Single pane of glass/end-to-end view.
LogicMonitor review
Cloud Native Platform
Supports a wide range of technologies: servers, networks, containers, applications, cloud services (AWS, Azure), and more. No on-premises infrastructure needed.Fast to deploy and scale.
Less appealing for air-gapped environments.