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.

Neutral

Neutral

Positive