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

InfluxDB vs Zenoss Cloud comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Oct 9, 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

InfluxDB
Ranking in Network Monitoring Software
12th
Ranking in IT Infrastructure Monitoring
16th
Average Rating
8.0
Reviews Sentiment
6.7
Number of Reviews
19
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), NoSQL Databases (6th)
Zenoss Cloud
Ranking in Network Monitoring Software
75th
Ranking in IT Infrastructure Monitoring
51st
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
8
Ranking in other categories
Application Infrastructure (26th), Event Monitoring (13th), Server Monitoring (24th), Container Monitoring (7th), Cloud Monitoring Software (42nd), AIOps (25th)
 

Mindshare comparison

As of March 2026, in the Network Monitoring Software category, the mindshare of InfluxDB is 0.3%, down from 0.4% compared to the previous year. The mindshare of Zenoss Cloud is 0.7%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Mindshare Distribution
ProductMindshare (%)
InfluxDB0.3%
Zenoss Cloud0.7%
Other99.0%
Network Monitoring Software
 

Featured Reviews

Mugeesh Husain - PeerSpot reviewer
Team Lead, Software at Energybox
Time series data has been managed efficiently for IoT sensors but reporting still needs improvement
How InfluxDB can be improved is relevant since for Energy Box, we face certain issues. We have customers worldwide, including the United States, United Kingdom, and Europe, but when we expanded to China two years ago, they indicated that they do not support the cloud version there. Our application is built on the cloud, which required us to create a separate application for Azure China, which was painful for us. The second issue involves frequent version changes. For example, we started with version one, transitioned to version two, and I heard they are considering InfluxDB version three, reverting to earlier practices. InfluxDB should improve without completely changing its approach. Now we have to redo our work for InfluxDB version three. Regarding needed improvements, the documentation is sufficient, but pricing presents a challenge. InfluxDB has standard pricing, which is acceptable for large companies. However, for startups in our position, they should provide special discounts so everyone can utilize it. The pricing should adapt as companies grow, which is a reasonable expectation.
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

"While I would rate InfluxDB a ten on a scale of one to ten, users should be thoughtful about matching the engine to their specific needs."
"Overall, InfluxDB delivered excellent performance, stability, and simplicity for telemetry-driven use cases."
"InfluxDB's best feature is that it's a cloud offering. Other good features include its time-series DB, fast time-bulk queries, and window operations."
"The user interface is well-designed and easy to use. It provides a clear overview of the data, making it simple to understand the information at hand."
"InfluxDB has positively impacted Energy Box by being the best choice for our needs."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"The custom built integration is one of the most valuable features because you can see all the especially critical items."
"The most valuable feature is the flexible discovery mechanism."
"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."
"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."
"It's easy to use."
"Its Docker Container concept is mind blowing."
"They have also accommodated many state-of-the-art technologies like Docker and ZooKeeper."
 

Cons

"Sometimes, when we write too much data within a minute, the data count becomes excessive, reaching perhaps 100,000 or 500,000 data points, and InfluxDB gives a timeout exception, which we must handle in our application."
"InfluxDB is generally stable, but we've encountered issues with the configuration file in our ticket stack. For instance, a mistake in one of the metrics out of a hundred KPIs can disrupt data collection for all KPIs. This happens because the agent stops working if there's an issue with any configuration part. To address this, it is essential to ensure that all configurations are part of the agent's EXE file when provided. This makes it easier to package the agent for server installation and ensures all KPIs are available from the server. Additionally, the agent cannot encrypt and decrypt passwords for authentication, which can be problematic when monitoring URLs or requiring authentication tokens. This requires additional scripting and can prolong service restart times."
"InfluxDB can improve by including new metrics on other technologies. They had some changes recently to pool data from endpoints but the functionality is not good enough in the industry."
"The solution doesn't have much of a user interface."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"However, I cannot ignore the challenges I faced while configuring the database with my message brokers, whether Rabbit or Kafka, because the documentation is not properly provided."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"If it gets a little bit more into the metric side, then it would really be great, similar to Prometheus."
"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 was a problem with Zenoss and storage monitoring."
"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"
"It would be ideal if the product offered sound alerts."
"The inclusion of a feature to show a graphical view of the network would be a helpful improvement."
"Technical support is 3/10, poor: Incomplete and poor documentation Undocumented processes Inconsistent solutions to problems depending on source"
"Now it is stable, but they should design threshold parameters in percentage instead of raw values."
"Now it is stable, but they should design threshold parameters in percentage instead of raw values."
 

Pricing and Cost Advice

"InfluxDB is open-source, but there are additional costs for scaling."
"We are using the open-source version of InfluxDB."
"The tool is an open-source product."
"InfluxDB recently increased its price. It is very expensive now."
"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."
"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."
report
Use our free recommendation engine to learn which Network Monitoring Software solutions are best for your needs.
884,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
11%
Financial Services Firm
10%
University
9%
Comms Service Provider
9%
Manufacturing Company
10%
Performing Arts
10%
Computer Software Company
10%
University
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business8
Midsize Enterprise4
Large Enterprise8
By reviewers
Company SizeCount
Small Business4
Large Enterprise5
 

Questions from the Community

What do you like most about InfluxDB?
InfluxDB is a database where you can insert data. However, it would be best if you had different components for alerting, data sending, and visualization. You need to install tools to collect data ...
What needs improvement with InfluxDB?
InfluxDB can be improved in several ways. The Flux query language needs to be learned, but if there were something similar to SQL or previous options, it would be much easier for users without impo...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is for server management metrics, Kubernetes monitoring, and application performance monitoring due to the time series data involved. We have InfluxDB integrated with ...
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

ebay, AXA, Mozilla, DiDi, LeTV, Siminars, Cognito, ProcessOut, Recommend, CATS, Smarsh, Row 44, Clustree, Bleemeo
2degrees, Rackspace, State of North Dakota, El Paso Independent School District, NWN Corporation
Find out what your peers are saying about InfluxDB vs. Zenoss Cloud and other solutions. Updated: March 2026.
884,873 professionals have used our research since 2012.