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

LogicMonitor vs Turbo360 (Formerly Serverless360) comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 18, 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

LogicMonitor
Ranking in Application Performance Monitoring (APM) and Observability
22nd
Ranking in Cloud Monitoring Software
14th
Average Rating
9.0
Reviews Sentiment
7.2
Number of Reviews
33
Ranking in other categories
Network Monitoring Software (12th), IT Infrastructure Monitoring (15th), Container Monitoring (6th), AIOps (8th)
Turbo360 (Formerly Serverle...
Ranking in Application Performance Monitoring (APM) and Observability
62nd
Ranking in Cloud Monitoring Software
44th
Average Rating
9.0
Reviews Sentiment
6.9
Number of Reviews
2
Ranking in other categories
Cloud Management (50th), Cloud Cost Management (29th)
 

Mindshare comparison

As of January 2026, in the Application Performance Monitoring (APM) and Observability category, the mindshare of LogicMonitor is 0.9%, up from 0.6% compared to the previous year. The mindshare of Turbo360 (Formerly Serverless360) is 0.6%, up from 0.1% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Application Performance Monitoring (APM) and Observability Market Share Distribution
ProductMarket Share (%)
LogicMonitor0.9%
Turbo360 (Formerly Serverless360)0.6%
Other98.5%
Application Performance Monitoring (APM) and Observability
 

Featured Reviews

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.
reviewer1858887 - PeerSpot reviewer
Software Development Engineer In Test at Quinbay
Centralized, great for performing corrective actions and has a helpful Business Activity Monitoring module
1) The user interface of Serveress360 could be improved a bit to make the platform even easier to use. 2) The addition of management and monitoring features for Cognitive services, Power Automate, and a few more Azure services. 3) It would be much better if it is a multi-cloud management/monitoring platform. 4) The consolidated error reports sent via the alerting channels can be a bit more intuitive. 5) Their customer support was good but good technical documentation or feature videos can be even more helpful.

Quotes from Members

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

Pros

"LogicMonitor has actually helped reduce our downtimes, helping us reduce downtime to about 40 to 50% by warning us before servers get heavy on usage or CPU load so we can take action in advance."
"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."
"Another feature from the technical aspect, the back-end, is the ability to allow individual users or customers to have their own APIs. They're able to make changes using the plugins covered by LogicMonitor. That is a very powerful feature that is more attractive to our techno-savvy customers."
"LogicMonitor improved on-premises infrastructure monitoring in several ways. One key feature was dynamic resource allocation, although we didn't utilize it much in our system. The main functionalities we benefited from were email alerts, network mapping, and dashboards."
"The initial setup is very simple."
"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."
"LogicMonitor has positively impacted my organization by being up to date with all the latest features and capabilities, so as our organization develops cutting-edge systems, whether internal or third party, we can always rely on LogicMonitor to provide proper enterprise level monitoring and observability."
"LogicMonitor is good for getting a full view of your topologies. They have LiveMaps, which give you a visual representation of your infrastructure."
"Service Bus topic subscription monitoring turned out to be the most useful for us."
"It offers all the core capabilities we need to manage and monitor our Azure services."
 

Cons

"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."
"Sometimes alerts do not include enough immediate context, so I still have to spend a few minutes correlating data across views."
"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."
"The dashboards can be improved. They are good, but there is a pain point. To show things to management, to explain pain points to other customers, to show them exactly where we can do better, the dashboarding could be better. Dashboards need to show the key things. Nobody is going to go into the ample details of Excel sheets or HTML."
"The process of upgrading some of the collectors has been a little bit confusing. I need to understand that better."
"We would like to see more functionality around mapping of topologies, in terms of networks. An improvement that we would like to see is added functionality to get more detail out of mapping. For example, if the LogicMonitor Collector identifies a connection between two network endpoints, it would be great to actually see which ports are connecting the two endpoints together. That functionality is something we greatly desire. It would actually make our documentation more dynamic in the sense that we wouldn't need to manually document. If this is something that the platform could provide, then this would be a great asset."
"LogicMonitor's reporting capabilities definitely could use an improvement. We have made do with the dashboarding and done what we can to make that work for our customers. However, there are definitely customers who would like a PDF or some kind of report along those lines, where we have been utilizing other tools to provide them. The out-of-the-box LogicMonitor reporting is the only thing that we have been less than impressed with."
"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."
"The user interface of Serveress360 could be improved a bit to make the platform even easier to use."
"Addition of more monitoring features to Azure Cosmos DB can be a huge help as we use the same as the main database for our applications."
 

Pricing and Cost Advice

"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."
"The solution is not expensive."
"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."
"In terms of pricing, I would rate LogicMonitor four out of five."
"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."
"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.""
"We pay for the enterprise tech support."
Information not available
report
Use our free recommendation engine to learn which Application Performance Monitoring (APM) and Observability solutions are best for your needs.
881,082 professionals have used our research since 2012.
 

Top Industries

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

Company Size

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

Questions from the Community

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 did not have much experience with the pricing, setup cost, and licensing for LogicMonitor. I sat in on some of the business meetings, but my main focus was the technical side of it, getting every...
Ask a question
Earn 20 points
 

Also Known As

No data available
Serverless360
 

Overview

 

Sample Customers

Kayak, Zendesk, Ted Baker, Trulia, Sophos, iVision, TekLinks, Siemens
MSC, Transalta, Rank Group, RACQ, BBC, Q2 Solutions, Middleway, BUPA, Columbia Sportswear, EDF
Find out what your peers are saying about LogicMonitor vs. Turbo360 (Formerly Serverless360) and other solutions. Updated: January 2026.
881,082 professionals have used our research since 2012.