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

Kaseya Traverse vs LogicMonitor comparison

Why PeerSpot?
 

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
75th
Ranking in Cloud Monitoring Software
53rd
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
5th
Average Rating
8.8
Reviews Sentiment
6.7
Number of Reviews
58
Ranking in other categories
Application Performance Monitoring (APM) and Observability (8th), IT Infrastructure Monitoring (7th), Container Monitoring (4th), AIOps (5th)
 

Mindshare comparison

As of November 2026, in the Network Monitoring Software category, the mindshare of Kaseya Traverse is 0.6%, up from 0.3% compared to the previous year. The mindshare of LogicMonitor is 1.9%, up from 1.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Mindshare Distribution
ProductMindshare (%)
LogicMonitor1.9%
Kaseya Traverse0.6%
Other97.5%
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

"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."
"It's a simple and humble tool."
"The remote support and data collection features are great."
"It is a pretty stable solution...It is a pretty stable solution."
"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."
"Automating processes is crucial for me, so the automation part stands out."
"If I want to automate the management and maintenance of my server automatically, this product is a good use case for that."
"Seeing how easy it is to manage devices, how simple it is to add, remove, or modify a device, and the amount of data that's included out-of-the-box whenever you add a device, makes it far superior to any product."
"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 helped reduce the length of an outage of a facility because of the identification of a fiber cut, so my company was able to be on top of that faster, so in that respect, the product gave us less than one year's worth of ROI."
"We have very fine-tuned alerting that lets us know when there are issues by identifying where exactly that issue is, so we can troubleshoot and resolve them quickly. This is hopefully before the customer even notices. Then, it gives us some insight into potential issues coming down the road through our environmental health dashboards."
"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 gives us visibility into issues that we didn't even know existed."
"The alerting would be number one in my book. The thresholds for getting alerts for different criteria are pretty well-thought-out. We don't get many false positives or negatives on the alerting side. If we do get an email alert or some similar alert, we know that it is something that has to be looked at."
"LogicMonitor has positively impacted my organization by reducing outages."
 

Cons

"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."
"With my most recent experiences on the solution, I can say that it isn't currently stable; there are a lot of glitches and bugs and the reliability just isn't there right now."
"I think the software is still a little bit too new to actually fully assess what it has."
"Improvement is needed in making it cheaper."
"We've noticed a few bugs as of late. However, this seems to only be in the reporting part of the product."
"The tool needs to have some AI capabilities, which it lacks currently."
"In terms of what could be improved, we are innovating all the time, as well as having a look at different avenues so that the strategy follows the structure. I think the software is still a little bit too new to actually fully asses what it has."
"There is substantial room for improvement with LogicMonitor."
"One thing I would like to see is parent/child relationships and the ability to build a "suppression parent/child.""
"One of the areas that I sometimes find confusing is the way that the data is presented. For example, a couple of weeks back I was looking at bandwidth utilization. That's quite a difficult thing to present, but they should try to dumb down how the data is presented and simplify what they're presenting."
"LogicMonitor could be improved by making the initial setup a little easier and giving users more control over alerts."
"LogicMonitor can be improved when we go to the settings page. In the new version, the navigation is easier but the buttons are very close to each other and sometimes when I'm clicking on something else, I'm clicking on the next button."
"One thing that could be really better is the mapping. Auvik is really good at it. They have a really nice way to give you a visual representation of your network, but in LogicMonitor, this functionality is not as powerful and as good as Auvik."
"Automated remediation of issues has room for improvement."
"Additionally, it times out after every couple of minutes, perhaps 20 or 30 minutes."
 

Pricing and Cost Advice

"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."
"The solution is not cheap, but it is not too expensive."
"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 is pretty expensive, but we now need one less full-time engineer. With on-prem, we used to have one more engineer in our department. That engineer has now moved to another department. Our capacity is better with this product than the previous one. It is easy for us to manage the sites. You have to choose between the standard account and the premium account. With the premium account, you get a lot more than the standard one, and you can also buy some extra features. It is a good thing to look at them because you would probably want to buy them. You should take your time and negotiate the price. They are easy. Like all cloud providers, they are able to discuss the price and if necessary, change the price."
"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."
"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."
"The solution is not expensive."
"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."
"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.""
"As a managed services provider, the licensing model that LogicMonitor provides us is excellent. We are able to scale up and scale down as needed. The pricing is reasonable for the amount of features and support that they provide."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
920,939 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Outsourcing Company
16%
Financial Services Firm
10%
Manufacturing Company
9%
Government
7%
Manufacturing Company
11%
Outsourcing Company
10%
Financial Services Firm
10%
Computer Software 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 Business17
Midsize Enterprise14
Large Enterprise35
 

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 is your experience regarding pricing and costs for LogicMonitor?
We directly connect to LogicMonitor, purchasing it through our third-party vendor. Regarding pricing, setup cost, and licensing, it is more about management decisions, but I find the pricing for co...
What needs improvement with LogicMonitor?
In my experience, I think LogicMonitor could be improved. I believe that at LogicMonitor events, there should be more tech time. It seems all focused on certification or what is new and the latest ...
 

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: October 2026.
920,939 professionals have used our research since 2012.