LogicMonitor Reviews

My main use case with LogicMonitor is monitoring the health of our EC2 instances and applications, such as my Kubernetes clusters, and the metrics which AWS does not provide, like memory management, memory utilization, and many other information points which AWS does not provide by default. LogicMonitor handles all of that.

I use LogicMonitor to monitor the EC2 CPU, memory, disk, and network metrics and set up threshold-based alerts. I am notified immediately if an instance spikes in usage or shows signs of performance degradation.

I use LogicMonitor to alert me when an EC2 instance CPU stays above 80% for 10 minutes, so I can quickly investigate whether it is a workload spike, a stuck process, or if we need to scale the instance. We have LogicMonitor integrated with Slack where we get alerts if anything goes wrong for an instance, the Kubernetes cluster, or anything similar.

The best feature according to me with LogicMonitor is that it is easy to configure. All the alerts are very easy to configure. It has a clean dashboard that is very intuitive. It has really strong EC2 cloud integrations. You do not have to install the agent. It is agentless, so that is the biggest advantage that I find because in other tools like Rapid7, you have to install the Rapid7 agent inside the instance. Here, we just need to have an instance in our VPC, and it will automatically scan all the instances and give me the stats for those instances.

What stands out most is how quickly I can spot issues, get notified with the right context on Slack, and track trends over time without a lot of manual steps.

The agentless setup reduces a lot of time because we do not need to add any code. We do not need to add any specific code in order to monitor that instance. Any instance that spins up in my AWS account which is in the same VPC as the LogicMonitor collector instance will automatically get picked up and all the statistics will be there. It is very easy with no setup. The only setup effort that I have to do is setting up one instance per VPC. Once that is done, we do not need to worry about it ever.

Another thing which I prefer about LogicMonitor is the flexibility. I can customize dashboards and alert thresholds based on what actually matters for our workloads. The historical data makes it very easy to spot patterns and prevent repeated issues.

LogicMonitor helps because there are two phases of alerts in any application. One is when the application is actually down. That happens when you have your monitoring system on your website or application level. However, that is too late to find out whether the application is down because at that time, it will be impacting the customers. LogicMonitor can give a kind of forecast when it comes to your servers because it will tell beforehand that particular servers are getting heavy on usage or CPU load. We can then go and either reduce its load or add another instance to share the load. This helps in prevention of any downtimes. It has helped significantly in our downtimes to prevent downtimes.

LogicMonitor has actually helped reduce our downtimes. When talking about the statistics, it has helped us reduce downtime to about 40 to 50% because without LogicMonitor, we used to know about the downtime only when the application was actually down. With it, the downtime has been reduced to 40 to 50%. That is a huge improvement when it comes to our applications.

When it comes to the improvement of LogicMonitor, I think there are a few points that can be improved. The first one is alert tuning, which takes time. It requires effort when trying to understand it for the first time. The defaults do not always match our workload patterns, so I have to adjust the thresholds to reduce noise and avoid alert fatigue. While the dashboards are solid, I sometimes wish that the UI was a bit more intuitive when drilling down quickly during an incident. There are many options and finding the exact view where I can identify the exact problem takes a few extra clicks. When an alert comes and I click on a LogicMonitor alert, it takes time to understand what the alert actually is and to go through the data points. The alert page specifically could be better. The alert tuning part can also be made more simple.

The first area that could be better is alert clarity and routing. Sometimes alerts do not include enough immediate context, so I still have to spend a few minutes correlating data across views. Adding more actionable details directly in the alert would make the response even faster. LogicMonitor sometimes gives false alerts as well. For example, if an EC2 instance is down, it will not determine whether the EC2 instance has been deliberately turned off or if it is actually not responding. At that time, it will give false alerts. The clearing of alerts is also an issue. Once an issue is fixed, the alert should be cleared, but it takes a little time for that alert to be cleared. Another improvement that would be helpful is simpler customization for complex dashboards. It is powerful, but building highly tailored dashboards, especially across multiple environments, can feel heavy and time-consuming. I would also appreciate a stronger out-of-the-box AWS correlation, such as automatically grouping related issues across EC2, EBS, and ALBs in a way that reads as a single incident story. This would reduce the mental overhead during outages. Grouping incidents together, such as all the EC2 alerts, all the EBS alerts, or all the load balancer alerts would be beneficial. Overall, none of these are blockers, just some improving areas.

There could be smarter anomaly detection out of the box that can catch unusual but important behavior without manual tuning of every threshold. Better tagging and dynamic grouping for EC2 instances would also be helpful. Cleaner alert de-duplication so a single underlying issue does not generate multiple redundant alerts would improve the system. More guided root cause workflows would be beneficial, such as providing the most likely causes based on correlated metrics. Faster search navigation across devices, dashboards, and alerts during incidents would also improve the platform.

I have been using LogicMonitor for the past three years.

LogicMonitor is very stable. I have never seen the UI down or any alerts or anything when it comes to the LogicMonitor side. It has been very stable for us. The platform is reliable, alerts are consistent, and once collectors and integrations are in place, monitoring runs smoothly with minimal disruption. Any issues we have seen are usually related to configuration or tuning, not the stability of the tool itself.

LogicMonitor is pretty good at scaling things when it comes to monitoring AWS infrastructure because I can see that it scales very well for us. It handles growth in the number of EC2 instances and services without major performance issues. It is straightforward to onboard new resources as environments expand. The main scaling challenge is not the platform itself, but making sure alerting and grouping stays organized as the infrastructure grows. Apart from that, there are no other challenges.

The customer support is very reliable. I can send emails to them and they will reply within 24 hours. It has been solid for us.

When it comes to customer support, I would rate it as a 7 because the option to call LogicMonitor support is not yet available. They do not give us the option to connect over a call. That can be a little bit of a hassle, but apart from that, it is solid.

Positive

Before LogicMonitor, we were using CloudWatch and a mix of manual dashboards, but it did not give us the same centralized visibility or alerting consistency. We had to go into each AWS account and open CloudWatch in that particular region. That was very tedious and cumbersome. We switched to LogicMonitor because it provides stronger end-to-end monitoring, better dashboards, and faster and more actionable alerts across our infrastructure. It is easy to view the alerts across all of our AWS accounts and regions. That is a big help for us.

There were a few challenges which I faced while setting up LogicMonitor with my AWS infrastructure. The first one was the initial discovery and onboarding, which took some effort. I needed to ensure the right AWS permissions, collectors, and access policies because that instance needs to access some sort of data while keeping in mind the security aspect so that the instance does not have every access. We give limited permissions to that particular instance and the IAM role associated with it. The next challenge was tuning alerts, which was the biggest time investment early on. The default thresholds did not always match our workload behavior. I had to adjust to reduce noise. Getting dashboards just right required some trial and error, especially when grouping EC2 instances by environment, tags, or services. Making sure the coverage was complete across hybrid components took time. We also have our servers in a vSphere infrastructure. I had to first identify all of our infrastructure and then carefully install a collector instance in each of the VPCs. That took time and effort, but it was all initial.

There has been definitely a return on investment when it comes to LogicMonitor. Previously, due to the downtimes, we used to have more infrastructure running because we were concerned about unexpected downtimes. Because of LogicMonitor, we have reduced our EC2 infrastructure significantly, which has helped us reduce costs by 20%. The time which is saved is significant. The incident response is better because there are no incidents and we are always preventing the incidents before they happen. The incident response time has also reduced significantly. When an alert comes, we also check LogicMonitor to see whether there was a warning there or not. This helps us pinpoint the issue. We can give a conservative percentage of 40 when it comes to the time saved. Fewer employees are needed now, so we used to have three to four people managing all the AWS infrastructure and the alerting part, which was reduced significantly because now only one person can look at the dashboard and the UI, which is very intuitive and easy to understand. It has also helped us reduce employees.

There were a few options which we considered before going with LogicMonitor. They included DataDog, New Relic, or staying fully on CloudWatch. We went with LogicMonitor because it gave us the right balance of infrastructure visibility, flexible alerting, and centralized monitoring without needing a lot of custom work and making it very useful in our day-to-day DevOps lifecycle.

If asked about LogicMonitor, I would simply say that if someone wants to consider LogicMonitor, they can definitely go for it. The only things that will need to be done is spending time upfront on alert tuning, setting up the collector instances, and giving them permissions. Apart from that, once that is done, it will be smooth sailing. There is no need to do anything as it is agentless. One just adds infrastructure, expands infrastructure, and it will automatically detect and discover. The alerting part is also very good. I would rate LogicMonitor with a review rating of 8 out of 10.

LogicMonitor is a solid end-to-end tool when it comes to monitoring AWS infrastructure. It is agentless, easy to set up, and easy to monitor.

The main use for LogicMonitor at Universal Music and the other organizations I'm working for is infrastructure-based monitoring. The goal is to move everything off of Dynatrace and other sources and into LogicMonitor as the main point of contact for all data, logs, filters, and infrastructure monitoring.

LogicMonitor monitors everything from servers to wireless access points to applications. Universal Music has sites all over the world on every continent outside of Antarctica. The offices have infrastructure devices such as Cisco switches, access points, servers, and VMware devices, all being monitored by LogicMonitor.

The challenges we faced with LogicMonitor were getting everybody up to speed, setting up training, and encouraging people to play around in the sandbox we built. The granularity of LogicMonitor has been a huge win, being able to create filters, set thresholds, dashboards with real-time monitoring, heat maps, and customize everything site by site.

The best features LogicMonitor offers include the ability to set up filters using Groovy scripts and Python. As a scripting person who loves doing things by code and automations, setting things up via scripts has been a huge benefit. The dashboarding feature and the different types of reports available are excellent, allowing us to get as granular as possible to provide only the pertinent data needed and filter out the white noise.

We set up filters to track dead devices and devices that haven't been reporting in for 90 and 180 days, built through a Groovy script that runs constantly and sends out a daily report. We also have reports built inside Python with Groovy scripting to help determine the top 10 most frequent sites having the biggest issues and break down what issues are coming in. There has been a lot of customization and many options in this space.

LogicMonitor has positively impacted our organization by cutting down white noise and false positives. With Dynatrace and AKIPS, we were getting a lot more white noise, and LogicMonitor allows our team to be more proactive than reactive, which cuts down on the SLOs and SLAs we are trying to meet at all times. During big events such as album releases, we need to ensure our devices are running at peak performance, and LogicMonitor allows us to see these flare-ups in real-time before they become massive issues. Being able to stamp out these issues before they take down sites during big releases is key.

Since switching to LogicMonitor, we have gone down from about 65 to 70% in false positives to 20 to 30%. While still not where we want it to be, this is a massive step in the right direction. Our SLAs and SLOs were averaging about 10 to 15 failed SLAs and SLOs that were over the time allotted to get those resolved, and those are now down to about two to three per week. This is a massive step forward and always going to be a work in progress, but LogicMonitor has definitely helped us move everything in the right direction.

LogicMonitor could improve their support system. One thing Dynatrace had that I enjoyed was real-time support chat available to reach someone and get help in real-time. With LogicMonitor, that is not really an option. We have to set up an email or reach out to support and try to set up an ad hoc call, which cannot be done in real-time when time is the most sensitive issue. That is definitely one area where they could improve.

There are not many gaps or anything that LogicMonitor does not already have available. More data sources or more reporting options would be helpful to make sure all bases are covered, no matter what kind of report or data we are looking to pull. Outside of that, there are really not many notes regarding changes to the application itself.

I have been using LogicMonitor for almost five years and took it end to end from the point of proof of concept all the way through go-live and beyond with Universal Music Group. I have a lot of experience, and I am now working on some other projects that use LogicMonitor as well.

Since we implemented LogicMonitor and got it working in production, there has been no downtime, no reliability issues, and nothing major regarding flare-ups from LogicMonitor's perspective.

LogicMonitor's scalability absolutely meets our organization's growth needs. When we bring in new sites and new devices, the auto setup or wizard very easily automatically detects those and pulls in those devices.

Overall, customer support has room for improvement because reaching someone can be difficult at times. We need to be able to reach them in real-time, and without those kinds of options available, we have to set up ad hoc calls, which could be improved.

Neutral

We previously used Dynatrace along with AKIPS and AWS CloudWatch. Dynatrace was only using about 25 to 30% of the resources available, and it was a very high price point. We ended up going with LogicMonitor because it was more cost efficient and allowed us to utilize even more than what we were using with Dynatrace.

LogicMonitor is deployed in our organization on private cloud, with the majority being private cloud. We have some hybrid deployments because we have some infrastructure inside Amazon AWS as well.

We did not purchase LogicMonitor through the AWS Marketplace. This was something we did contracts with and went through LogicMonitor directly, setting it up from proof of concept all the way through go-live and beyond.

I do not have information concerning money saved, fewer employees needed, or time saved. However, I do know they have definitely seen a return on investment with LogicMonitor. I have heard them say very positive things financially about it and how improvements have occurred since implementation, but I do not have specifics in that area.

I did not have much experience with the pricing, setup cost, and licensing for LogicMonitor. I sat in on some of the business meetings, but my main focus was the technical side of it, getting everything implemented and moved over through all of the integrations. I do not remember much about the business sales aspect.

We looked into DataDog, we also had Splunk for a little while, and Grafana as well. Those did not pan out much. We even looked at possibly using more of the Dynatrace space, but their price point was far too high, so LogicMonitor ended up being the solid choice for us.

New users should definitely pay attention to how LogicMonitor allows you to change everything from adding things in via the resource tree, doing things using the expert wizard tools. You do not have to manually bring your devices over; LogicMonitor can automatically find the devices for you. There are plenty of different modules that you can use and data sources, so pretty much any scenario you have that you need for a monitoring space or monitoring option, LogicMonitor will be able to provide that and then some.

I give LogicMonitor a solid 10 on a scale of 1 to 10. Outside of those little things, that would not bring my score down at all. With my experience working with other observability stacks and applications, this one is definitely top of the game and top of the list.

I chose a 10 because of the granularity, the customization, the scripting capabilities, the real-time monitoring options, and how easy it is to migrate or integrate it with things such as BigPanda and ServiceNow. Overall, LogicMonitor is a one-stop shop for anything you need monitoring-wise.

There is going to be a learning curve as with all observability stacks, but definitely play around with LogicMonitor, get comfortable with it, build out a sandbox, and do their demo trials. Being willing to embrace change and a new way of doing things will show you that LogicMonitor is very solid, as they should be able to support any use case you throw at them.

As long as LogicMonitor makes the updates and lets us know what has changed and how to access the new features, that is the main thing. I would rate this product a 10 out of 10 overall.

I am a customer of LogicMonitor and have handled B2B business. My usual use cases for LogicMonitor involve our cloud resources and on-premise resources. I have used LogicMonitor for monitoring devices, servers, and websites. I have around 11 collectors and 1,000 devices onboarded for my client account, Welsh Water. I am from Infosys and used LogicMonitor for Welsh Water, so basically it is B2B.

The impact of LogicMonitor solution on my team's mean time to resolve incidents involves automated ticket polling. When we set a limit, it automatically closes the ticket if it is resolved. This saves a lot of time and I don't need to go through piles of unwanted errors. Automated error recovery is something I really appreciate.

Another thing is the scheduling of reports, which saves most of my time and energy. The error handling mechanism comes with a scope, and we have RBAC enabled. Those who know can approach it and nobody else is going to see what is happening in the other team. It helps the team directly resolve errors. Half of the errors which are invalid go away, and half of the errors which just need to be acknowledged can be scheduled as a report and solved by each individual team. This reduces time and energy significantly.

The feature and capability of LogicMonitor that I liked the most is the assistance. We have handmade assistance support available 24/7. If we have any technical glitch or technical issues, the vendor support is available right away. That is what made my work much easier.

The Partner Academy supported by LogicMonitor is a feature I could highlight and really liked. Learning about the tool is possible through this platform. I can see an instructor teaching me the implementation of LogicMonitor. We don't have many other resources to study about the tool, and we have very limited resources available. The partner portal is one such feature I appreciated.

The latest version has features that satisfy me greatly. I am impressed with the look of the new version, the design, and the dashboard options. It has more tabs but is very easy to navigate with everything on one page. The UI and UX design made as a new feature in LogicMonitor is something I appreciate. I usually use one feature where I can see the resources in a hive structure. All the resources can be seen in a hive manner, with everything color-coded basically in three colors for error, warning, and good status. If anything is coded in red, I can go to that and easily see it. I have seen this feature on the resources page or maybe in the dashboard page where every service and website is shown. My usual health checkup is much easier with this feature.

The collector was really good and I had a good experience with it, especially on load balancing. There exists automatic load balancing which I really appreciated.

LogicMonitor's 24/7 monitoring is a feature I really appreciate. It saves me from the night shifts and I don't need to worry about it. It handles both business time and off-business time without my consent in an automated manner.

LogicMonitor can be improved when we go to the settings page. In the earlier version, it was pretty simple where I had to navigate individually to the individual settings. In the new version, the navigation is easier but the buttons are very close to each other. Sometimes when I'm clicking on something else, I'm clicking on the next button. I need some good alignment to happen on the settings page.

I have been using LogicMonitor for about five years.

I evaluate how stable and reliable LogicMonitor is, and I don't find it unreliable because even the chat is happening very confidentially. I don't think it is unreliable from my end. I have never felt any power issues or power backup issues from LogicMonitor. Whatever I have made for my collector as a backup always stayed in place.

One day I made a mistake by shutting down all the servers at once and I haven't touched anything with it. I went to see the mistake after some 12 hours. When I clicked it on and gave access again, making everything active, every alert was there. Whatever happened within that 12 hours was recorded there. Even if it was not kept in active mode, it somehow gave me all the data. That is the stand-alone stability of LogicMonitor.

I can rate the stability of LogicMonitor from one to ten as eight because it is not classified properly. Though we have the common three classifiers of warning, error, and critical, I expect some classification if it happens for piles of emails or piles of errors. However, I can give it an eight.

I evaluate how scalable LogicMonitor is and I can give it a nine because of its very good UI, except for the spacing in the buttons. It is very navigable and we can navigate to anything very easily and quickly. I can give it a nine. When I am about to learn something, the interface presents it in a way that is easy to understand. When I look at the resource page, I can learn all the cloud resources we are having and the number of devices we are having very quickly. In order to understand the architecture, it is very easy for me. When it comes to adaptability, I can give it a nine as well.

The features and capabilities of LogicMonitor that I liked the most is the assistance. We have handmade assistance support available 24/7. If we have any technical glitch or technical issues, the vendor support is available right away. That is what made my work much easier.

My communication and interaction with technical support shows they won't make anything out of the league. They maintain their confidentiality between us and the client very well. They also have a corporate approach and what we have discussed will be released via email, which is very perfect. We have quick assistance where they go into the server, look for the issue, and if they find anything, they report to us immediately and within 10 to 15 minutes it is resolved. Rapid problem solving is what I would say in one word. It is very fast.

I can rate technical support from one to ten as nine, definitely nine.

Before LogicMonitor, I used a different solution for the same use cases, and it was SolarWinds. The reason I decided to stop using SolarWinds is that SolarWinds requires agents, as basically all other monitoring and observability tools have this agent to be used, and there is no built-in API with that. LogicMonitor is having REST API and is also agentless, which makes it more advanced.

The challenges I faced in gaining complete visibility across my infrastructure involve especially working with the syslog and the tags. There are many tags for a particular server which I am not confident about which ones we are using and for which purposes we are using them. That is something I really stuck on, but as we don't use them much, I am comfortable with the current setup. I would rate this review an overall eight out of ten.

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.

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.

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.

I have been using this solution for at least five years.

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.

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.

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.

Positive

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.

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.

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.

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.

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.

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.

I have been using LogicMonitor for three years now.

LogicMonitor is stable, 100%.

LogicMonitor's scalability is very satisfactory.

Customer support is on point and very well trained. I have interacted with their support team and had a good experience.

Positive

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.

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.

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.

Before choosing LogicMonitor, we evaluated Sentinel, which was too expensive, and another major player, but we wanted something that had cost predictability.

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.

I am an internal system administrator using LogicMonitor. Most of what we do with LogicMonitor involves on-premises hardware such as servers, network equipment, firewalls, and storage devices.

We do not utilize the Dynamic Service Insights feature for real-time visibility. We only use plain monitoring and do not use cloud monitoring such as Office 365 because it is too expensive. We exclusively use network monitoring equipment and server monitoring.

LogicMonitor is deployed on-premises in our organization. We have agents on-premises for servers at our customer sites, and they report back to our LogicMonitor instance.

I have not used LogicMonitor's AIOps for diagnosing root causes and orchestrating remedies.

The most valuable features of LogicMonitor are the company's knowledge about monitoring devices and their expertise in what to monitor. They excel at telling you what is performing well and what is performing poorly. LogicMonitor provides thresholds with explanations of what they mean, whereas a lot of monitoring software captures thresholds and data without knowing exactly what those metrics mean. If needed, you can get help with solving the problem causing the threshold to be triggered. LogicMonitor knows when something is going wrong. For example, when a disk threshold exceeds 90%, you receive a warning. However, that is straightforward, and many software solutions do that.

When you encounter Active Directory thresholds for concurrent connections or open connections, those are more difficult to set correctly. The main reason I appreciate LogicMonitor is that we do not have to set those thresholds ourselves. LogicMonitor does that for us.

LogicMonitor has positively impacted our organization by allowing us to implement it for 1,200 clients or 1,200 endpoints within three months, which went very well. The software has enabled us to operate with one fewer full-time employee because it works exceptionally well and does exactly what we need it to do. Our deployment process was reduced from one day to embed a customer in our settings and workflow to just one hour with LogicMonitor. That is a significant improvement in speed. Additionally, because LogicMonitor is cloud-based software, we do not have to perform any maintenance on the platform itself. All maintenance is automated by LogicMonitor, which saves us considerable time.

LogicMonitor affects our team's mean time to resolve incidents because we perform a lot of troubleshooting with it, particularly performance troubleshooting and configuration management, and those capabilities help us reduce the time to resolve problems significantly. For example, when a switch goes down, we have the latest configuration of the switch available in LogicMonitor.

I do not think there are areas of LogicMonitor that could be improved or enhanced other than the price. We do not have a lot of contact with LogicMonitor because the software usually works as it should.

I have been working with LogicMonitor since 2017.

LogicMonitor has not been down in the years we have used it. It has consistently remained operational. I cannot remember the last time LogicMonitor sent me an email about an error or when I visited the website and encountered an error.

LogicMonitor is very much scalable, stable, and reliable.

I sometimes communicate with LogicMonitor's technical support. For example, a few years ago, we wanted to monitor a specific firewall and have its configuration displayed in LogicMonitor. This capability was not included in the default packages, so I asked whether LogicMonitor could provide that functionality. Within one day, I received a script, and LogicMonitor was able to provide the firewall configuration in LogicMonitor on the same day I submitted the request.

Based on my experience with LogicMonitor's support, I would rate them nine out of ten, with ten being the best support, primarily because of the price.

Positive

I participated in the initial setup of LogicMonitor.

The initial setup process of LogicMonitor involved testing several software options. We tested LogicMonitor, Kaseya Traverse, and another option that I do not recall at this moment. LogicMonitor was the solution we selected. We had a connection between our CEO and LogicMonitor for pricing discussions, and after they completed the pricing process, we performed some pre-configuration on the customer side to make LogicMonitor implementation easier. After that, we spent about one month with three people converting everything from the monitoring software we were using previously, which was Zenos, similar to Zabbix. We completed the conversion to LogicMonitor within that one month. We then spent one month troubleshooting the events that were generated, and we used the final month for cleaning up all remaining elements. We made a complete transition to LogicMonitor within three months without any interruption to monitoring.

The challenges I faced in gaining complete visibility across my infrastructure involve combining on-premises devices such as laptops, on-premises users who sometimes transition to another device, mobile devices, or work from home or from another location, and gathering all alerts and then consolidating them into a single usable alert to solve real-time issues with account hacks and other security concerns. However, that has nothing to do with LogicMonitor.

Dynamic Service Insights does not affect my understanding and management of digital services in my organization.

I would rate this product nine out of ten overall.

LogicMonitor is used to monitor servers, network devices, firewalls, routers, switches, and anything with support for SNMP, WMI, and API support.

LogicMonitor manages network assets that are deployed globally across all data centers. Proactive monitoring for any SNMP alert helps to check the device status and its availability.

An agentless architecture is implemented with collectors that are very easy to deploy and manage, which helps reduce the overhead of installing agents on every monitored endpoint.

LogicMonitor has a device discovery console that helps monitor devices and significantly reduces onboarding time. The platform is MSP friendly with strong, mature multitenant capabilities.

Several customers leverage the same tenant of LogicMonitor, making it easy to navigate and switch between different tenants to manage customers.

LogicMonitor supports monitoring for a vast array of devices including VMware, Cisco, NetApps, and Linux and Windows servers. The platform also supports API-based monitoring, which is very useful for SaaS-based applications.

LogicMonitor is a very easy and agentless monitoring platform offering over 3,000 automated integrations. This is one of the very nice and good tools to be acknowledged in the case of enterprise-level monitoring.

LogicMonitor delivers a lot of positive outcomes through proactive SNMP alert monitoring. When a device goes down, it triggers an alert to the operations team, and the operations team quickly checks why and what problems may have arisen for the device to go down. This allows the operations team to open a relevant ticket to the support team to check the device physically.

LogicMonitor has delivered a lot of good use cases in terms of knowing the availability of the network and how the network devices are performing. In a large enterprise environment, knowing this is always valuable. Downtime on each network asset has been reduced, and now there is better visibility for the operations team to manage 24/7 support.

A change in handling incidents has been noticed. The visibility on overall network infrastructure and availability has been maintained above 98% overall in terms of managing network services.

Reporting limitations exist with the product. When trying to create a dashboard that is useful for day-to-day monitoring, the native reporting is not that intuitive.

For the first-time user, learning the product presents a very steep learning curve. It is a bit complicated yet effective tool. It may take some time for an individual who is new to the platform to learn and become familiar with the navigation because the GUI is full of tabs.

LogicMonitor is a very effective and helpful tool to monitor all SNMP-based network devices. However, the response time and application loading can be slow, and despite being a SaaS-based application, the GUI could be better designed to show less and do more.

Customization support is not that easy. Professional support or the support team must be involved to look after customized monitoring, which is sometimes not that straightforward and requires a lot of collaboration with other teams to support that requirement.

LogicMonitor has been used for more than two years.

LogicMonitor is stable.

LogicMonitor scales well across the geography of customer presence. By placing the number of pollers, N number of devices can be polled, and managing those pollers is easy as it is a SaaS-based application that can be managed without any dependency on VPN or being on-premises.

There have been no issues so far to report to customer support. However, based on what has been heard, the support team is very good and very responsive in terms of acknowledging and attending to any problems and challenges from end customers.

A different solution called SolarWinds was used previously. That product was implemented in a different business environment. After splitting the network infrastructure from a legacy business environment to new, there was an opportunity to onboard and review a new product, and LogicMonitor was onboarded.

Though LogicMonitor is a SaaS-based platform, the pricing and overall deployment was quite easy. The licensing part was not involved in the process. The decision was made by the customers, and the purchase order was made directly by them.

LogicMonitor underwent a POC, and it was then finalized.

LogicMonitor is a very effective and helpful tool to monitor all SNMP-based network devices. Downtime on each network asset has been reduced, and there is now better visibility for the operations team to manage 24/7 support.

The pricing and overall deployment was quite easy. The licensing part was not involved. The decision was made by the customers, and the purchase order was made directly by them.

For someone looking for an all-in-one solution that covers network, infrastructure, and cloud, LogicMonitor is a pretty solid choice. However, if the needs are simpler, more cost-effective, or less complicated, open-source tools might be better options.

LogicMonitor is overall a great tool, and it is moving in the right direction. The latest enhancement in the GUI console is really intuitive and has brought a lot of good insight about monitoring network infrastructure. The review rating for LogicMonitor is 9 out of 10.

We have both on-premises and cloud resources as well as network resources. Everything monitored for my client, which I cannot disclose, is done by LogicMonitor itself. The endpoint website monitoring is also done via LogicMonitor.

What I appreciate about LogicMonitor is that it has a number of data sources and data points, which they call LogicModules. One thing that is not available in many other monitoring tools is the level of customization I can do with it. Even at the ground level, I can go into a very particular data point for a single instance and change the metrics for monitoring. The granularity is something that is not provided by many great products, but this one offers it.

The insights from LogicMonitor affect my understanding and management of digital services in my organization as we heavily rely on the insights from LogicMonitor. It cannot go without human verification, obviously, but the insights it gives and the alert notifications which top talkers have generated are easy to portray to clients, to the C-suite, and to executives to make them understand where the bottleneck is and where I am utilizing more resources or where resources are not needed. This helps in cost-cutting as well.

The main area for improvement is that if LogicMonitor's UI were a bit more user-friendly, that would be more useful. Not many people can easily understand the data sources and data points. New joiners on my team cannot get away with it very easily without proper training. LogicMonitor is not as intuitive as Blue Coat or SolarWinds in this regard. You will have to go through the LMCP or you have to pursue complete training, after which you will be able to understand and use it.

I have been using LogicMonitor for the last 2.5 years.

Regarding stability, I have experienced downtimes when LogicMonitor upgrades the portal completely, but it is well-informed in advance and there are collector updates that occur during that time. For half an hour, we will not see any insights or miss any alerts and insights, but they inform us well in advance and they do not do it during business hours. I have not seen any downtime that extends more than what they have decided.

I do not find any scalability issues with LogicMonitor so far.

I personally used LogicMonitor technical support directly, and there were no third parties involved such as partners or consultants. LogicMonitor provided a dedicated team to support us. They have a 24/7 team who were always available during setup, and we had numerous meetings and calls to help us understand the setup and how the tool works. On a scale of 1 to 10, where 10 is the best, I would rate the tech support and customer service team as a nine. They are always responsive apart from weekends or public holidays when they take a bit more time, but otherwise, they are quick.

Apart from LogicMonitor, I work with other monitoring solutions and previously used different solutions for monitoring. I have used SCOM and SolarWinds majorly, and a number of others in my previous organizations. However, primarily here with my client, it is LogicMonitor itself.

When reflecting on the initial setup of LogicMonitor, I found that whenever we onboarded, we had a support person and a complete team assisting us for the first initial few days. This was necessary. Anyone without any prior knowledge of LogicMonitor would not be able to figure it out as it is quite different from other monitoring tools, particularly regarding the granularity I mentioned. LogicMonitor provides complete support for migration, setup, and initiation, which is helpful. However, any company wanting to onboard with LogicMonitor alone will find it difficult if they attempt to do so without support.

I personally used LogicMonitor technical support directly, and there were no third parties involved such as partners or consultants. LogicMonitor provided a dedicated team to support us. They have a 24/7 team who were always available during setup, and we had numerous meetings and calls to help us understand the setup and how the tool works.

I have seen return on investment and measurable benefits with LogicMonitor by creating a report on how many resources we are actually using and what the billing should be. I ensure that no unnecessary resources are being monitored just to create unnecessary billings.

We have been utilizing the Dynamic Service Insights feature for real-time visibility for reporting purposes, and we are still to onboard and still to use the diagnostic features which LogicMonitor provides. We are still using the traditional way to diagnose with our teams rather than having LogicMonitor handle the diagnostics.

LogicMonitor's AIOps for diagnosing root cause analysis and orchestrating remediation is quite new for us. The LogicMonitor Plus subscription has now given us Edwin AI, and we are still struggling to get this completely legalized for work. Not all AI features are being used yet. When we gain more knowledge about it, probably in a year from now, we will start using Edwin AI.

The impact of LogicMonitor on my team's mean time to resolve incidents has been great. We find a number of points which create lots of top talkers, perhaps something which creates unnecessary noise with alerting. LogicMonitor flags that on its own, which is quite helpful on a monthly or weekly basis. We focus on lowering MTTR from a monthly basis for each team that works on LogicMonitor.

Regarding missing features, the diagnostic features for Edwin AI are something I am really looking forward to. I am handling LogicMonitor for my client solely right now, with a few other peers. Edwin AI would help resolve lots of server issues and diagnose them to minimize MTTR.

The challenges I have faced in gaining complete visibility across my hybrid infrastructure with the Envision platform are that LogicMonitor started about 2.5 years ago and I struggled a lot to get the teams onboarded on it. Nobody would let go of traditional ways such as AWS monitoring to get onboarded with LogicMonitor, as there is a cost per resource added. The reports it fetches, the insights it gives, and the future forecasting have always been very helpful. We have around 10,000 plus devices from a server point of view, and it is ever increasing. Still, we have many on-premises devices from third parties which are still not on LogicMonitor. We can only hope that those teams agree to onboard as well.

If organizations would like to monitor on-premises and cloud infrastructure, many have different tools for cloud and on-premises devices and differently for network devices as well. That can be cumbersome as the data points and ratios are different. If they would like everything in one place, they should go with LogicMonitor. It handles it pretty well. If they need any deep dive for NOC operations and network devices, they can incorporate another app above it, but for everything all in one place, LogicMonitor is good with it. I would rate LogicMonitor as a product and solution eight out of ten.

My main use case for LogicMonitor is to monitor all the networking devices deployed in our on-premises network.

Whenever the network goes down, I receive an alert from LogicMonitor indicating that a node or device is down, which allows me to check and troubleshoot the device physically or review the logs to determine the issue, how many packets were dropped, and other relevant details.

LogicMonitor provides me with the total number of devices present in the network and allows me to see how it monitors the networking scenario.

LogicMonitor offers the best capabilities, including capturing the node status, checking whether the network is down or up, and seeing how the network is actually working.

I can create customized widgets in the dashboard, which helps me check on networking equipment whether they are servers, switches, Layer 3 devices, access devices, printers, or anything else. If any device goes down, it alerts me immediately.

In LogicMonitor, I can view the node, configure it, manage the bandwidths, and if a node is down, I can manually change the path.

After deploying LogicMonitor, I can get information about the device condition within one to two seconds and receive alerts. Yellow alerts appear first, and when they exceed a set interval of time, red critical alerts come through, which helps my organization check on critical issues.

The alerts and emails sent to customers could be improved and delivered more directly.

The interface is acceptable, and I do not have any suggestions for it.

SNMP configurations and deployment guides could be more user-friendly for engineers deploying the solution.

I have been using LogicMonitor for one and a half years.

The main challenge occurs when LogicMonitor goes down while the physical device is actually up. Sometimes physical devices are functioning properly, but LogicMonitor is unable to detect this, which results in unnecessary ticket generation that my team must address.

Occasionally, the monitoring does not function properly, and minor issue tickets are generated unnecessarily, requiring my team to resolve them.

LogicMonitor is a properly scalable solution.

Customer support is good and they respond on time, though they could improve their services further.

We were previously using SolarWinds, though I was not fully aware of its complete capabilities. My company switched to LogicMonitor with the decision that it would reduce downtime.

I have seen a return on investment for the employees involved. When manual work was being performed, downtime was very high and significantly impacting the business. After deploying LogicMonitor into the hybrid cloud environment, money was saved. Ultimately, LogicMonitor saves my organization time. Deploying LogicMonitor into the hybrid cloud in our setup achieves both objectives of saving money and saving time.

For licensing, I raise queries and take approval from the owner or client. They handle the licensing portion and manage pricing decisions. Clients care about the pricing, and they provide the license for us to work with.

I am still exploring the AI capabilities of LogicMonitor and learning about cloud solutions. Dynamic services does not interrupt my work, and I follow its processes accordingly.

LogicMonitor has helped me resolve issues faster. As alerts come through, I directly check the interfaces or nodes that are down, and I examine the mean time to resolution to determine how I can bring the device back up. I can also push configuration changes if a device is completely down, which is the best part.

When using LogicMonitor, I recommend creating customized widgets according to your specific problems and solutions, and placing all critical nodes on the same dashboard for proper monitoring.

LogicMonitor partners with us and checks everything including business support and customer satisfaction alongside the timeframes in which clients can be satisfied.

My overall review rating for LogicMonitor is nine out of ten.

I work as a consultant providing solutions to customers, and I use cloud native services for monitoring. I primarily recommend CloudWatch, and if the customer has a preference for a third-party tool, I provide solutions for DataDog or other services.

I function as an architect in cloud services, particularly hybrid cloud. I need these tools and services that I always offer to customers. When I design solutions, I provide a monitoring solution and recommend these services.

I have multiple customers to whom I have recommended monitoring tools. I have worked on many projects including McAfee, CarMax, AMC, and American Media Corporation. I have recommended these services across different projects.

I have been using CloudWatch for more than ten years. I primarily recommend CloudWatch because customers do not want to spend additional money on other tools. I would recommend a native service so they can save cost. AWS is introducing synthetic monitoring for applications, which is crucial for precise monitoring. AWS X-Ray and Amazon QuickSight integration makes CloudWatch a centralized monitoring tool.

LogicMonitor is used for application insights monitoring, collecting, analyzing, and visualizing data from application infrastructure, and identifying errors. It boasts features including real-time alerting, log ingestion, and visualization dashboards. LogicMonitor offers microservices monitoring and more features in terms of alerting and support compared to CloudWatch, but it is costlier.

CloudWatch's integration is very quick. Since these are all connected internally with the AWS backbone network, no significant integration is needed. I simply enable CloudWatch across AWS services. This centralized tool also offers logs query through Amazon QuickSight, creating visual alert dashboards.

Technical support is obviously good in LogicMonitor, rating it a ten. CloudWatch's support rates at eight to eight and a half.

LogicMonitor excels in performance monitoring, tracking performance, bolstering security, and real-time alerting. However, LogicMonitor can struggle with high ingestion costs, data retention limitations, delayed alerts, and missing critical security events.

There are several areas for LogicMonitor to improve. Overly sensitive real-time monitoring leads to too many alerts, which could be managed via AI to reduce false positives. Cost optimization by offering discounts to enterprises could help manage pricing concerns. LogicMonitor should become more centralized to handle heterogeneous environments, as plugins sometimes do not work across platforms like F5 firewall. Complexity and steep documentation also need simplification.

LogicMonitor might struggle with delayed detection, as alerts may not be immediate under high infrastructure load. Other weaknesses include ingestion costs, data retention limitations, missing critical security events, real-time analysis gaps, and delayed alerts.

I have been working with this solution for more than seven years.

Technical support is obviously good in LogicMonitor.

I have experience with AWS, DataDog, and CloudWatch. LogicMonitor offers logs monitoring capabilities. Integration-wise, LogicMonitor also has an agent that can be installed on a particular service, and all data gets populated on LogicMonitor. I can see all the documents and everything. I can also integrate with ServiceNow and other platforms. The choice depends on how the customer is using their infrastructure to monitor.

The main consideration is cost optimization. Some customers want to optimize their cost for their infrastructure, so I would recommend CloudWatch. For other customers who are open to spending additional funds, I would recommend LogicMonitor or DataDog.

LogicMonitor provides application dynamic monitoring and application insights monitoring. It collects, analyzes, and visualizes data from application infrastructure and identifies errors. I can track performance and bolster security with microservices monitoring using LogicMonitor.

LogicMonitor has more features compared to CloudWatch in terms of real-time alerting, log ingestion, alerting, visualization dashboards, and complaint support. However, cost is the only matter of concern. LogicMonitor has more features compared to CloudWatch.

I find a few weaknesses at the moment. Alert fatigue sometimes occurs when there is a peak load on the AWS infrastructure, and LogicMonitor takes some time to alert. High ingestion cost is another concern. Data retention limitations present challenges because sometimes I need to check alerts from six months back, but the data retention is only one week, maximum ten days, or one month. Missing critical security events is an issue where some non-critical logs get flagged as false positives. Real-time analysis is required but sometimes only works in a few services and not in all services. Some security breaches cannot be identified through LogicMonitor because those logs are not captured when something happens to a particular service. For example, if an application has vulnerabilities, the application acts like a legitimate service, but I do not know that. LogicMonitor hardly identifies these things. Even when I collect the logs, I cannot exactly know if the log is the faulty one. I think most service vendors are trying to implement AI models to identify this, but it takes some time to get this done. I think LogicMonitor is also trying to do this.

Delayed detection is a significant issue. Because of high load on the infrastructure, sometimes I will not find the alert immediately. It takes five to ten minutes, and after the impact happens, I get notified five to ten minutes later. This delayed detection is the main issue.

Real-time monitoring is required, and that means overly sensitive alerts with too many false positives. If LogicMonitor can use AI or other methods, they can remove those duplicates and maintain the actual alerts. They can identify false positives prior and prevent them by nullifying those things. Cost is another area where LogicMonitor can provide discounts to enterprise companies using most of their infrastructure to reduce their license cost. Complexity should be addressed because if a customer has multiple heterogeneous environments, LogicMonitor should be centralized to get all the data and do the log monitoring. Sometimes some plugins and agents do not work on few services. For example, on F5 firewalls and on-premises firewall physical servers where I want to get some logs, those do not get logged on LogicMonitor. A lack of context and understanding of the tool is also an issue. The documentation should be more clear and simple in simple language. When I first see the documentation, it is pages upon pages, and it is very difficult to understand everything until I gain some control of that tool. The documentation should be reduced so people can easily use that tool. Instead of going very complex, straightforward guidance should be required. My overall rating for this product is nine out of ten.