Try our new research platform with insights from 80,000+ expert users

Kaseya Traverse vs LogicMonitor comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 10, 2024

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

Kaseya Traverse
Ranking in Network Monitoring Software
78th
Ranking in Cloud Monitoring Software
49th
Average Rating
6.6
Reviews Sentiment
6.5
Number of Reviews
8
Ranking in other categories
No ranking in other categories
LogicMonitor
Ranking in Network Monitoring Software
6th
Ranking in Cloud Monitoring Software
7th
Average Rating
9.0
Reviews Sentiment
7.1
Number of Reviews
34
Ranking in other categories
Application Performance Monitoring (APM) and Observability (13th), IT Infrastructure Monitoring (8th), Container Monitoring (4th), AIOps (5th)
 

Mindshare comparison

As of March 2026, in the Network Monitoring Software category, the mindshare of Kaseya Traverse is 0.5%, up from 0.3% compared to the previous year. The mindshare of LogicMonitor is 2.3%, up from 1.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Mindshare Distribution
ProductMindshare (%)
LogicMonitor2.3%
Kaseya Traverse0.5%
Other97.2%
Network Monitoring Software
 

Featured Reviews

AMMAR HUMAIDY HUSIN - PeerSpot reviewer
Technical Consultant at a university with 11-50 employees
Automation increases efficiency, but pricing needs to be more competitive
Improvement is needed in making it cheaper, of course. I am not emphasizing making it cheaper, however, it should be more competitive with other products. The product itself is very good and helpful for me as a customer. The issue always is the price, as we cannot beat most of our competitors on pricing alone. If a product is just nice to have, not essential like an antivirus, if it's not really competitive with pricing, we cannot sell it.
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

"We have found the solution to be very flexible to our requirements. We have been able to configure it on-premise effectively when we were using less of the cloud."
"If I want to automate the management and maintenance of my server automatically, this product is a good use case for that."
"It is a pretty stable solution...It is a pretty stable solution."
"It's a simple and humble tool."
"The remote support and data collection features are great."
"Everything is running seamlessly on the solution, to the point where you don't see any gap."
"Most of the features are pretty good and the solution is user friendly."
"Automating processes is crucial for me, so the automation part stands out."
"The concept of developing a dashboard template for ourselves, then cloning it for every single customer, and only having to change one piece of information, is a godsend. That's one of the strengths. We can develop a template that fits every customer and just change the information that is presented."
"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 is good for getting a full view of your topologies. They have LiveMaps, which give you a visual representation of your infrastructure."
"LogicMonitor helps us prevent potential downtime. It's pretty good. It generates low-level warnings that aren't necessarily preemptive but can still alert us to issues we should investigate. These warnings allow us to correlate data and identify areas where we should take action, even if the issues aren't critical."
"We get full visibility into whatever the customer wants us to monitor and we get it pretty rapidly. That is very important. Only having certain metrics that other platforms will give you out-of-the-box means you only get a small picture, a thumbnail picture. Whereas with LogicMonitor, you get the entire "eight by 10 picture", out-of-the-box. Rather than some availability metrics, you get everything. You get metrics on temperature, anything related to hardware failure, or up and down status."
"LogicMonitor has positively impacted our organization by especially improving service reliability and user experience, and 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."
"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."
"The breadth of its ability to monitor all our environments, putting it in one place, has been helpful. This way, we don't have to manage multiple tools and try to juggle multiple balls to keep our environment monitored. It presents a clear picture to us of what is going on."
 

Cons

"We've noticed a few bugs as of late. However, this seems to only be in the reporting part of the product."
"Reporting is a bit difficult."
"However, the issue lies in the adequacy of the responses to my questions, which are usually not up to par."
"Kaseya Traverse can improve by adding a Service Map to help us create a configuration management database (CMDB), this would be helpful for us."
"The tool needs to have some AI capabilities, which it lacks currently."
"Improvement is needed in making it cheaper."
"Reporting is tedious and not organized in the way customers expect."
"Dashboards and Central Protection were an issue. Also, database monitoring was not there. Even though they said that it was there at an additional cost, that tool was very basic. We couldn't have device configuration backup also."
"One drawback of LogicMonitor is its licensing model, which requires an additional license for each module. For example, if you need to use Azure monitoring, you'll need an additional license on top of the base license."
"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."
"LogicMonitor should always improve AI because we are always striving for real intelligence. An additional feature we'd like to see in the next release of LogicMonitor is more in the area of identification of when the dominant workload is working. There are certain devices and applications that have cycles of their own. Some are used primarily during prime time, and some are used during the overnight timeframe, and better identification and classification of those workloads would be helpful. For example, we could then do some more planning about, for this particular set of devices, as it has a prime time environment, and we don't want to see a 24-hour average, as we want to see what is the 75th or 90th percentile utilization during the prime time when it is being used, whenever that prime time is."
"Dashboarding capabilities could be enhanced. It is cumbersome, you must do it all at once, and then you must repeat the process every now and then."
"We are working with LogicMonitor to get flexibility to see the absolute running numbers, rather than doing an average. They can keep the average for customers who want it, but there should be a way to at least show the real numbers, which are coming every second on the screen."
"It needs better access for customizing and adding monitoring from the repository. That would be helpful. It seems like you have to search through the forums to figure out what specific pieces you need to get in for specific monitoring, if it's a nonstandard piece of equipment or process. You have to hunt and find certain elements to get them in place. If they could make it a bit easier rather having to find the right six-digit code to put in so it implements, that would be helpful."
"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."
"I'd like to see more automation in the tool, especially around remediation."
 

Pricing and Cost Advice

"The solution is not cheap, but it is not too expensive."
"The price depends on whether you are monitoring different applications, especially in bulk, and depends on what you're doing. If you're monitoring one endpoint, it will cost you 150 ZAR."
"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."
"We are on an enterprise license plan, we are paying $7.75 per device a month. That is for a commitment of 350 devices. Anything that is over the 350 is charged at 1.2 times the rate; 1.2 times $7.75 would be the overage charge. We are looking at increasing our commitment to either 450 or 500 devices. It changes our pricing if we go to 450 devices, bringing it from $7.75 down to $7.70. If we go for 500 devices, it brings it from $7.75 down to $7.50. We will probably factor in the volume discount drop from $7.75 to $7.50 in our decision of whether we uplift or not. We also have some cloud monitors, which are about $500 a month."
"The tool's pricing falls into the middle range."
"In terms of pricing, I would rate LogicMonitor four out of five."
"The features were very valuable to us because we could consolidate them into one platform and have a good user experience with the platform, our accounts, and the support team. That was the key driver for us. That was what we were looking for. We looked for a comprehensive solution that could provide advanced features all in one platform, and LogicMonitor was the solution that we chose. It definitely has a premium price. However, you are getting what you pay for in a very effective way. That was important in our decision-making.The features were very valuable to us because we could consolidate them into one platform and have a good user experience with the platform, our accounts, and the support team. That was the key driver for us. That was what we were looking for. We looked for a comprehensive solution that could provide advanced features all in one platform, and LogicMonitor was the solution that we chose. It definitely has a premium price. However, you are getting what you pay for in a very effective way. That was important in our decision-making."
"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."
"It definitely pays for itself in the amount of time we're not spending with false errors or things that we haven't quite dealt with monitoring. It has been good cost-wise."
"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."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
884,933 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
14%
Government
11%
Healthcare Company
7%
Comms Service Provider
7%
Manufacturing Company
11%
Computer Software Company
10%
Financial Services Firm
9%
Healthcare Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business1
Large Enterprise7
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise11
Large Enterprise11
 

Questions from the Community

What needs improvement with Kaseya Traverse?
Improvement is needed in making it cheaper, of course. I am not emphasizing making it cheaper, however, it should be more competitive with other products. The product itself is very good and helpfu...
What is your primary use case for Kaseya Traverse?
If I want to automate the management and maintenance of my server automatically, this product is a good use case for that.
What advice do you have for others considering Kaseya Traverse?
I'd rate the solution seven out of ten. As Kaseya sellers, we always promote Kaseya first. If the price is more competitive, then I think it will be better. It's a main pain point for us as a resel...
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 do you like most about LogicMonitor?
LogicMonitor helps us prevent potential downtime. It's pretty good. It generates low-level warnings that aren't necessarily preemptive but can still alert us to issues we should investigate. These ...
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...
 

Overview

 

Sample Customers

UltiSat, Clear Concepts, nVidia, United States Postal Service, Cisco, Redbox, Spark Digital, People's Bank & Trust
Kayak, Zendesk, Ted Baker, Trulia, Sophos, iVision, TekLinks, Siemens
Find out what your peers are saying about Kaseya Traverse vs. LogicMonitor and other solutions. Updated: March 2026.
884,933 professionals have used our research since 2012.