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

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
77th
Ranking in Cloud Monitoring Software
52nd
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.9
Number of Reviews
49
Ranking in other categories
Application Performance Monitoring (APM) and Observability (9th), IT Infrastructure Monitoring (8th), Container Monitoring (4th), AIOps (6th)
 

Mindshare comparison

As of August 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 2.1%, 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.1%
Kaseya Traverse0.6%
Other97.3%
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

"In terms of most valuable features, we are happy with everything so far, and maybe in a year's time I'll have a different opinion on what can change, what can be better, but for now it's the perfect solution."
"It's a simple and humble tool."
"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."
"Kaseya Traverse is a very stable solution and very sustainable in terms of what the market wants, what is out there, price-wise and functionality features. They're quite competitive and they are always innovating."
"Everything is running seamlessly on the solution, to the point where you don't see any gap."
"The remote support and data collection features are great."
"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."
"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."
"LogicMonitor has more features compared to CloudWatch in terms of real-time alerting, log ingestion, alerting, visualization dashboards, and complaint support."
"LogicMonitor saves time in terms of its ability to proxy a connection through a device. For example, if you are troubleshooting a device, which you may want to connect to, you can proxy this connection through the platform. As a support resource, I don't need to use multiple platforms to connect to a device to further investigate the issue. It is all consolidated. From that perspective, it saves time because a resource now only needs to use one platform."
"LogicMonitor really improved our workflow as a company."
"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."
"From the time that I started using it, I haven't had any issues with the software at all."
"LogicMonitor has a very highly talented support team that can answer the questions and help the customer right away."
 

Cons

"However, the issue lies in the adequacy of the responses to my questions, which are usually not up to par."
"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."
"The tool needs to have some AI capabilities, which it lacks currently."
"Reporting is tedious and not organized in the way customers expect."
"Improvement is needed in making it cheaper."
"I think the software is still a little bit too new to actually fully assess what it has."
"We've noticed a few bugs as of late. However, this seems to only be in the reporting part of the product."
"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."
"The ease of use with data source tuning could be improved. That can get hairy quickly. When I reach out for help, it's usually around a data source or event source configuration. That can get challenging."
"LogicMonitor has a very steep learning curve."
"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."
"It needs better access for customizing and adding monitoring from the repository."
"LogicMonitor should improve its logging features. It can become expensive and should be cost-effective. It would be great to see prebuilt templates for alerting methods in LogicMonitor that are similar to the prebuilt dashboards. Currently, users have to build their alerting configurations."
"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."
"I think the product is expensive when looking at products in the same segment in the market."
"One thing I would like to see is parent/child relationships and the ability to build a "suppression parent/child." For example, If I know that a top gateway is offline and I can't talk to it anymore, and anything that's connected below it or to it is also going to be offline, there is no need to alarm on those. In that situation it should create one ticket or one alarm for the parent. I know they're working towards that with their mapping technology, but it's not quite to that level where you can build out alarm logic or a correlation logic like that."
 

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 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 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."
"LogicMonitor is competitively priced at the same level as other vendors, like Datadog."
"In terms of pricing, I would rate LogicMonitor four out of five."
"I know we are saving at least several hundred thousand dollars in that we're not buying Cisco Prime."
"They are expensive for the cloud."
"The license is annual, and I'm not fully aware of what it costs. We have a through-cycle that we go through, and they've been generous with us going above our limit. They're not strict on it. At the end of the year, they got us to renew. We always add some cushion for what we expect. Also, if you need custom monitoring or design work, you can pay them for consulting services."
"The tool's pricing falls into the middle range."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
908,858 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
13%
Construction Company
10%
Government
9%
Outsourcing Company
9%
Manufacturing Company
11%
Financial Services Firm
10%
Computer Software Company
9%
Construction 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 Enterprise13
Large Enterprise31
 

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?
My experience with pricing, setup cost, and licensing is that the licensing model has changed and is very confusing as it currently stands and overly complicated.
What needs improvement with LogicMonitor?
I do see negatives and areas for improvement in LogicMonitor. Obviously, there is always space for improvement. First of all, I believe the commercial aspects require improvement. At the moment, if...
 

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: August 2026.
908,858 professionals have used our research since 2012.