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

LogicMonitor vs Zenoss Cloud comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 16, 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 Network Monitoring Software
6th
Ranking in IT Infrastructure Monitoring
8th
Ranking in Container Monitoring
4th
Ranking in Cloud Monitoring Software
5th
Ranking in AIOps
6th
Average Rating
8.8
Reviews Sentiment
6.9
Number of Reviews
49
Ranking in other categories
Application Performance Monitoring (APM) and Observability (9th)
Zenoss Cloud
Ranking in Network Monitoring Software
65th
Ranking in IT Infrastructure Monitoring
52nd
Ranking in Container Monitoring
8th
Ranking in Cloud Monitoring Software
41st
Ranking in AIOps
28th
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
8
Ranking in other categories
Application Infrastructure (19th), Event Monitoring (14th), Server Monitoring (26th)
 

Mindshare comparison

As of August 2026, in the AIOps category, the mindshare of LogicMonitor is 5.5%, up from 4.1% compared to the previous year. The mindshare of Zenoss Cloud is 2.2%, up from 0.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
AIOps Mindshare Distribution
ProductMindshare (%)
LogicMonitor5.5%
Zenoss Cloud2.2%
Other92.3%
AIOps
 

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.
ClaudiaChen - PeerSpot reviewer
Cloud Architect - Senior Technology Architect at Telstra
Generates close to real-time alerts so users can resolve issues, but needs more integration and public cloud monitoring features
As Zenoss Service Dynamics is more for network-centric devices and you want to monitor, for example, a server, its services, IP addresses, and interfaces, if it's a network and you're going to monitor multiple items, you'll be charged multiple times. This is what Zenoss Service Dynamics needs to improve to make sure that customers pay just one fee to monitor the entire server. What I'd like to see in Zenoss Service Dynamics in the future is a public cloud monitoring feature, particularly for the Azure public cloud. Another additional feature I'd like to see in the next release of the solution is integration with the Azure public cloud because I know that there are some services from Azure that Zenoss Service Dynamics is currently unable to monitor.

Quotes from Members

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

Pros

"LogicMonitor has more features compared to CloudWatch in terms of real-time alerting, log ingestion, alerting, visualization dashboards, and complaint support."
"After deploying LogicMonitor into the hybrid cloud environment, money was saved."
"From the time that I started using it, I haven't had any issues with the software at all."
"LogicMonitor helps improve outcomes, including improved infrastructure uptime, faster issue resolution, and better visibility across servers, network devices, and cloud resources."
"Having a full team at LogicMonitor for support is super helpful as they are available all the time to answer any questions you may have."
"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."
"LogicMonitor basically gives you the ability to monitor the infrastructure side of your application ecosystem."
"The initial setup is very simple."
"It's easy to use."
"With this solution, they can have one million users at the same time with no crashes."
"Its Docker Container concept is mind blowing. It is the first monitoring tool which comes with Docker features."
"Zenoss is more complex than LogicMonitor, but scalable and hugely customizable."
"The product offers good documentation that helps with initial training."
"They have also accommodated many state-of-the-art technologies like Docker and ZooKeeper."
"Overall, it's a great solution, and I consider it to be one of the best."
"What I like most about Zenoss Service Dynamics is that it monitors the devices and gives close to real-time alerts. For example, in case the device is not available, Zenoss Service Dynamics generates an alert so my team can resolve the issue."
 

Cons

"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."
"Their Logs feature is quite new. It is not as feature-rich as we would like it to be."
"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."
"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."
"Additionally, I found that LogicMonitor needs some improvement in threshold monitoring."
"In terms of improvement, I suggest that the pricing could be on the higher side for smaller organizations, advanced customization has a learning curve, and alert tuning may require initial optimization to avoid too many alerts."
"The scalability of LogicMonitor is good, but it is challenging to have to spin up additional collectors all the time."
"This is one thing that is a pain and flaw with LogicMonitor."
"As Zenoss Service Dynamics is more for network-centric devices and you want to monitor, for example, a server, its services, IP addresses, and interfaces, if it's a network and you're going to monitor multiple items, you'll be charged multiple times. This is what Zenoss Service Dynamics needs to improve to make sure that customers pay just one fee to monitor the entire server. What I'd like to see in Zenoss Service Dynamics in the future is a public cloud monitoring feature, particularly for the Azure public cloud. Another additional feature I'd like to see in the next release of the solution is integration with the Azure public cloud because I know that there are some services from Azure that Zenoss Service Dynamics is currently unable to monitor."
"There is room for improvement with the administrative part. They introduced Control Center to manage things in Zenoss 5. The services that Zenoss provides remained the same, but the administrative part, since they introduced Docker, etc., has become a little complex"
"Now it is stable, but they should design threshold parameters in percentage instead of raw values."
"There was a problem with Zenoss and storage monitoring."
"Technical support is 3/10, poor: Incomplete and poor documentation Undocumented processes Inconsistent solutions to problems depending on source"
"It would be ideal if the product offered sound alerts."
"This solution is complex for beginners so it takes some time to learn."
"The AI aspect needs to improve."
 

Pricing and Cost Advice

"I know we are saving at least several hundred thousand dollars in that we're not buying Cisco Prime."
"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."
"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."
"They are expensive for the cloud."
"It's affordable. The price we get per license is a lot cheaper than what we were getting with some of the other tools. There are other monitoring tools out there that are cheaper, but what you get with LogicMonitor, out-of-the-box, makes it worth the cost."
"The solution is not expensive."
"We pay for the enterprise tech support."
"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."
"There are additional costs you'll have to pay apart from the license fee for Zenoss Service Dynamics. I can't remember exactly how much my company is paying because I don't handle the finance part, but the cost is paid annually. On a scale of one to five, with one being the cheapest and five being the most expensive, I'm rating the solution three out of five."
"It depends on the customer, what he wants."
"It is very cost-effective compared to the tools I worked with in the past. The company is gaining a lot with respect to the cost factor. It provides agentless monitoring and in a very cheap way."
"The pricing depends on the environment, the number of services, and the size of the data center. It can go from $100,000 to a million dollars."
report
Use our free recommendation engine to learn which AIOps solutions are best for your needs.
908,800 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%
Construction Company
14%
Comms Service Provider
11%
Manufacturing Company
10%
Transportation Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business13
Midsize Enterprise13
Large Enterprise31
By reviewers
Company SizeCount
Small Business4
Large Enterprise5
 

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 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...
What is the best network monitoring software for large enterprises?
In my experience, I worked with many monitoring software, but the one that gave me the most functionalities of a large-scale company is Zenoss, due to its ability to monitor completely hybrid and a...
 

Comparisons

 

Also Known As

No data available
Cloud Monitoring, Zenoss Service Dynamics
 

Overview

 

Sample Customers

Kayak, Zendesk, Ted Baker, Trulia, Sophos, iVision, TekLinks, Siemens
2degrees, Rackspace, State of North Dakota, El Paso Independent School District, NWN Corporation
Find out what your peers are saying about LogicMonitor vs. Zenoss Cloud and other solutions. Updated: July 2026.
908,800 professionals have used our research since 2012.