No more typing reviews! Try our Samantha, our new voice AI agent.

Apache SkyWalking vs LogicMonitor comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Apache SkyWalking
Ranking in Application Performance Monitoring (APM) and Observability
33rd
Average Rating
8.4
Reviews Sentiment
4.4
Number of Reviews
3
Ranking in other categories
No ranking in other categories
LogicMonitor
Ranking in Application Performance Monitoring (APM) and Observability
12th
Average Rating
8.8
Reviews Sentiment
7.1
Number of Reviews
40
Ranking in other categories
Network Monitoring Software (6th), IT Infrastructure Monitoring (8th), Container Monitoring (4th), Cloud Monitoring Software (7th), AIOps (5th)
 

Mindshare comparison

As of May 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of Apache SkyWalking is 0.6%, down from 0.7% compared to the previous year. The mindshare of LogicMonitor is 1.7%, up from 0.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Mindshare Distribution
ProductMindshare (%)
LogicMonitor1.7%
Apache SkyWalking0.6%
Other97.7%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

reviewer2784462 - PeerSpot reviewer
Software Engineer at a tech vendor with 10,001+ employees
Tracing has revealed hybrid bottlenecks and delivers full visibility into critical payment flows
Apache SkyWalking provided full visibility into the black hole because before using it, we could not see what was happening when a request left Amazon EKS and went to our on-premises legacy databases. Apache SkyWalking's distributed tracing correlates these two worlds in a single view, showing us that 40% of the latency was actually happening in the network hop between the cloud and the physical data center, not in the code itself. Second, it exposes hidden architectural flaws. By using the automatic dependency mapping, we discovered that some microservices were stuck in a cyclic dependency which was documented nowhere. This visual evidence allowed us to refactor the logic and immediately increased our throughput by 30%. Apache SkyWalking gave us database-level insight without database access. Through its slow query monitoring, the Java agents captured the exact SQL statements that were hanging during peak sales hours. This meant our developers could fix the exact line of code or index without needing to wait for a DBA to pull logs, reducing our mean time to resolution. There are many features that are useful to mention in this case because we obtained different benefits. Apache SkyWalking automatically drew the topology of the 600 pods where we discovered cyclic dependencies between services that no one had documented before and that were slowing down the system. Another valuable feature is resolving hybrid bottlenecks because we isolated a specific network issue between AWS and the physical data center. Without distributed tracing, infrastructure teams blame Java code and vice versa. Database tuning is also important because thanks to slow query metrics captured by the agent, we identified and rewrote the SQL queries that most impacted performance during sales peaks.
Anshuman Thakur - PeerSpot reviewer
Site Reliability Engineer at a comms service provider with 501-1,000 employees
Monitoring has reduced downtime and now enables proactive alerts across cloud workloads
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.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"Using Apache SkyWalking has had a positive impact on my organization because it has enabled us to identify the causes of various problems more quickly."
"Apache SkyWalking is a very nice tool and an exceptional tool for managing volume and complex architecture on AWS without the prohibitive cost of commercial suites."
"Apache SkyWalking has positively impacted my organization by reducing the time of the team so that they can put in more efforts into their other tasks, saving a lot of time, improving our SLA in resolving any issue, providing good RCA analysis to the leadership team, and helping us in monitoring the entire health in a shorter time span."
"One of the key reasons for going for it was the knowledge of the things that they put in the product."
"LogicMonitor is very reliable compared to many other monitoring tools I have used, as each individual BGP session, IPsec tunnel, and interface is captured accurately and the logs are highly reliable."
"It has had a solid impact and has helped us to resolve issues faster with everything in real time and the alerts."
"We have seen a great return on investment after the deployment of this product, with 24/7 visibility on our network infrastructure being achieved through a centralized management console, requiring only a few resources to manage, such as three people on our team."
"One thing that's very valuable for us is the technical knowledge of the people who work with LogicMonitor. We looked at several products before we decided to use LogicMonitor, and one of the key decision-making points was the knowledge of the things that they put in the product. It provides real intelligence regarding the numbers that you see on the product, which makes it easy for us technical people to troubleshoot. Other products don't provide you with such information. You see a value going up, but you don't know what it means. LogicMonitor provides such information. For instance, if a value goes up, it says that it is probably because your disk area was too low."
"It has improved our organization with its capacity planning. We have a performance environment that we use to benchmark our applications. We use it to say, "Okay, at a certain level of concurrency, we know where our application will fall over." Therefore, we are using LogicMonitor dashboards to tell us that we're good. Our platform can handle X number of clients concurrently hitting us at a time."
"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 most valuable feature of LogicMonitor is the infrastructure monitoring capability."
 

Cons

"Apache SkyWalking can be improved with storage management complexity because with this volume of 50 million traces a day, managing data retention on OpenSearch is critical."
"Apache SkyWalking can be improved by responding more quickly to new versions of monitored products."
"Apache SkyWalking can be improved by enhancing a few things. The learning curve is definitely there, so it needs a good learning curve."
"Their Logs feature is quite new. It is not as feature-rich as we would like it to be. There have been a couple of conversations internally around other log management tools, like Splunk, which may do more for us than LM Logs. The benefit of LogicMonitor is that our staff know how to use it, so we don't really want to move away from it, if we don't have to. I fully expect there to be more development in this area. It is their newest feature, so it is understandable that it hasn't evolved as some of the other stuff. It would be good to see a bit more development in this area, but I think the monitoring side of things is spot on."
"LogicMonitor has good features, but the ease of use is a little bit confusing. Additionally, we are looking for workflow automation, which is a little bit tricky for LogicMonitor."
"LogicMonitor should always improve AI because we are always striving for real intelligence."
"Automated remediation of issues has room for improvement."
"Automated remediation of issues has room for improvement. I don't know how best to handle it, but I know that they're kind of working on it. I know there are some resources that can do automated remediation. I would like them to improve this area so it could be completely hands-free, where it detects an issue, such as, if a CPU is running high. There are ways to do it even now, but it's a bit more involved."
"If you only want to use LogicMonitor in the cloud, there's a better tool available."
"Some more application performance type monitoring would be nice. For example, an APM type solution, which would not necessarily completely replace it, but be able to tie into to what we're seeing on the application performance side so we can correlate what's going on with the application versus the underlying infrastructure."
"We only use plain monitoring and do not use cloud monitoring such as Office 365 because it is too expensive."
 

Pricing and Cost Advice

Information not available
"The tool's pricing falls into the middle range."
"We've had customers who have reduced their costs by not having multiple platforms for monitoring. That said, especially with super-large environments, the cost model for LogicMonitor is the one area where we run into issues."
"They are expensive for the cloud."
"It can handle scaling. It is like any other cloud service. There is a cost associated with scaling, so we currently don't monitor all of our environments. We monitor just the customer-facing production environments. It would be nice if we could monitor our dominant environments, but we will have to pay a lot more due to the scaling issue. So, there's a balance there between what we would like and what we are willing to pay for."
"As a managed service provider, we have the highest level of licensing that they offer, so we don't have any extra fees. I believe there are some add-ons for some of the lower tiers of LogicMonitor service, but that's not something that we use with our agreement."
"We have definitely seen ROI with LogicMonitor. We used to provide 24/7 IT support for our users. We have since been able to change to operating just within normal business hours for IT support, and LogicMonitor was a large part of being able to accomplish that."
"It's an enterprise-grade solution and competitively priced compared to the other solutions that are out there... Our organization is not huge, but LogicMonitor is worth every penny that we pay for it. I've never heard anyone say, "I'm not sure that we're getting good value for money from this product." It's integral to our business."
"The licensing side of things with LogicMonitor, is quite simple. It is one license per device. Recently, you have additional licenses with things, like LM Cloud, which does confuse things a bit. Because it's very hard to estimate how many licenses you're going to need until you're monitoring it, so it's quite hard through that process to give a customer price to say, "This is how much this services will cost.""
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
894,738 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
20%
Computer Software Company
17%
Manufacturing Company
13%
Retailer
10%
Manufacturing Company
11%
Computer Software Company
11%
Financial Services Firm
10%
Healthcare Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise11
Large Enterprise18
 

Questions from the Community

What is your experience regarding pricing and costs for Apache SkyWalking?
Our experience with pricing, setup cost, and licensing for Apache SkyWalking is positive since it is free, which was the reason for our decision to use it.
What needs improvement with Apache SkyWalking?
Apache SkyWalking can be improved by responding more quickly to new versions of monitored products, including, for example, taking into account changes in Java class names.
What is your primary use case for Apache SkyWalking?
Our main use case for Apache SkyWalking is for monitoring Java application servers such as Tomcat and WebSphere Liberty.
What is the best network monitoring software for large enterprises?
It actually depends on the exact purpose or requirements. Some tools are better for only network devices while others are better from a cloud monitoring or APM monitoring perspective. You can check...
What is your experience regarding pricing and costs for LogicMonitor?
I researched the pricing of LogicMonitor, and it costs around ten dollars per device per month, which is somewhat expensive compared to other products. Some monitoring tools such as Zabbix are free...
What needs improvement with LogicMonitor?
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 of...
 

Comparisons

 

Overview

 

Sample Customers

1. Alibaba 2. Amazon 3. Apple 4. Baidu 5. ByteDance 6. Cisco 7. Dell 8. Google 9. Huawei 10. IBM 11. Intel 12. JPMorgan Chase 13. Klarna 14. LinkedIn 15. Microsoft 16. Netflix 17. Oracle 18. PayPal 19. Pinterest 20. Qualcomm 21. SAP 22. Samsung 23. Spotify 24. Tencent 25. Twitter 26. Uber 27. VMware 28. WeChat 29. Xiaomi 30. Zoom
Kayak, Zendesk, Ted Baker, Trulia, Sophos, iVision, TekLinks, Siemens
Find out what your peers are saying about Apache SkyWalking vs. LogicMonitor and other solutions. Updated: April 2026.
894,738 professionals have used our research since 2012.