Overview
LogicMonitor is the leading SaaS-based, performance monitoring platform for Enterprise IT. With coverage for thousands of technologies, LogicMonitor provides granular visibility into infrastructure, cloud and application performance across hybrid and cloud infrastructures. Automated device discovery, preconfigured alert thresholds and rich, customizable dashboards, come together to give IT teams the speed, flexibility and actionable insights to succeed in today's competitive markets.
Simply install a LogicMonitor Collector and add devices via network scan, bulk add, or orchestration tool of choice. The Collector automatically recognizes devices in your infrastructure and immediately begins collecting performance metrics. From there, use LogicMonitor's flexible data collection mechanism to pull metrics from virtually any device or API, then create graphs, dashboards, and custom alerts to quickly view application status and analyze trends.
Highlights
- End-to-end AWS Migration Monitoring: Ensuring migrated resources perform as intended with panoramic visibility into on-premises and AWS services in a single-pane view. Agentless Collector provides hybrid and multi-cloud visibility in minutes, not days or weeks. Low cost of ownership as teams are not having to constantly upgrade agents to support new features. Devices are recognized and instantly auto-configured based on best practices.
- Complete visibility into cloud services: visualize cloud performance, availability, and ROI alongside your monitored on-premises infrastructure for a complete view into hybrid and multi-cloud environments.
- Automated device configuration for 2,000+ technologies: LogicMonitor detects what to monitor, what to graph, and what to alert on, automatically, to give you intelligent, actionable monitoring.
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Buyer guide

Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/month |
|---|---|---|
Enterprise Package | Enterprise Package - Local Collector Devices | $22,000.00 |
LM APM Metrics | <50 datapoints pushed via API or scraped via OpenMetrics integration | $3,000.00 |
LM APM Synthetics | Up to 1000 invocations of selenium-recorded synthetic tests | $3,000.00 |
LM APM Traces | Up to 1m application spans | $3,000.00 |
Layered AI | Layered AI | $120,000.00 |
LM Cloud | Cloud Resources | $3,000.00 |
LM Cloud IaaS | See quote | $22,000.00 |
LM Cloud PaaS | See quote | $3,000.00 |
LM Config | Configuration Monitoring and Alerting | $1,500.00 |
LM Container Monitoring | Container Resources | $3,000.00 |
The following dimensions are not included in the contract terms, which will be charged based on your usage.
Dimension | Cost/unit |
|---|---|
Additional usage as defined in Sales Order Form (Private Offers Only) | $0.01 |
Vendor refund policy
Custom pricing options
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Support
Vendor support
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.

Standard contract
Customer reviews
Monitoring tools have unified hybrid visibility and support cost-optimized architectures
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with this solution for more than seven years.
How are customer service and support?
Technical support is obviously good in LogicMonitor.
What other advice do I have?
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.
Real-time dashboards have improved troubleshooting and provide faster insight into server issues
What is our primary use case?
My main use case for LogicMonitor is to have visibility on the servers in our network, various networks, and cloud resources.
I use LogicMonitor to look at various logs, and I have used the logs that I have obtained from LogicMonitor to pinpoint issues and fix them.
What is most valuable?
The dashboards are really very helpful and they can be customized, which helps us.
I think agentless monitoring and the dashboards are my favorite features. With agentless monitoring, there is no need to install software on every device, and that cuts down time because we have a lot of devices. The dashboards are customizable, so various teams and roles can use those dashboards in a way that suits their needs.
When I see things in real time, I am able to get to them faster. When there is any kind of issue on any of our various servers, because we have many servers in our environment, seeing things in real time is very helpful.
It has had a solid impact and has helped us to resolve issues faster with everything in real time and the alerts. Some noticeable changes could be how our dashboards look and how we are able to see things in real time.
What needs improvement?
LogicMonitor has a very steep learning curve. The user interface sometimes can feel unintuitive. The mobile app has some limitations.
The only challenges we have are sometimes the setup, which can take some work to avoid too much noise. When we need support, they have been helpful.
For how long have I used the solution?
I have been using LogicMonitor for three years.
How are customer service and support?
LogicMonitor customer support is good. I advise getting a demo and working with the customer support because I think LogicMonitor works well.
Which solution did I use previously and why did I switch?
I am not sure what we used before, as it might have been before my time. I do know that we switched because whatever we were using before was not functioning in a positive way.
There was DataDog that we looked at, and I thought LogicMonitor was better.
How was the initial setup?
The pricing was a bit high. The setup was pretty fair.
What was our ROI?
I have seen a positive return on investment. I cannot give specific metrics, but it has definitely saved time for my team.
What other advice do I have?
I gave LogicMonitor an overall review rating of 8.
Monitoring expertise has reduced setup time and now supports thousands of on-prem devices efficiently
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with LogicMonitor since 2017.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
LogicMonitor is very much scalable, stable, and reliable.
How are customer service and support?
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.
How was the initial setup?
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.
What other advice do I have?
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.
Unified monitoring has reduced incident noise and enables rapid resolution across networks
What is our primary use case?
What is most valuable?
The impact of LogicMonitor on management of service health and business risks is significant. In my previous company, after implementing LogicMonitor, most issues were resolved within one hour without requiring senior engineer intervention, as junior engineers could resolve issues by reviewing the alert information and understanding what occurred.
What needs improvement?
For how long have I used the solution?
Which solution did I use previously and why did I switch?
What's my experience with pricing, setup cost, and licensing?
What other advice do I have?
Monitoring has reduced downtime and now enables proactive alerts across cloud workloads
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using LogicMonitor for the past three years.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What was our ROI?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.