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
22nd
Ranking in IT Infrastructure Monitoring
26th
Average Rating
8.2
Reviews Sentiment
6.6
Number of Reviews
11
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (9th), NoSQL Databases (4th)
Zenoss Cloud
Ranking in Network Monitoring Software
77th
Ranking in IT Infrastructure Monitoring
53rd
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
8
Ranking in other categories
Application Infrastructure (31st), Event Monitoring (14th), Server Monitoring (26th), Container Monitoring (10th), Cloud Monitoring Software (39th), AIOps (25th)
 

Mindshare comparison

As of August 2025, in the Network Monitoring Software category, the mindshare of InfluxDB is 0.4%, up from 0.3% compared to the previous year. The mindshare of Zenoss Cloud is 0.5%, up from 0.4% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software
 

Featured Reviews

DeepakR - PeerSpot reviewer
An open-source database that can be used to insert data
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.
ClaudiaChen - PeerSpot reviewer
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

"The most valuable feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"InfluxDB works as expected with excellent scalability and stability, which is critical for our application."
"The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem."
"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 from servers. It must be installed on Windows or Linux servers. During installation, ensure that the configuration file is correct to prevent issues. Once data is collected, it can be sent to InfluxDB. For visualization, you can use open-source tools like Grafana."
"The most valuable features are aggregating the data and integration with Graphana for monitoring."
"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."
"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."
"The solution is very powerful."
"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."
"It's easy to use."
"They have also accommodated many state-of-the-art technologies like Docker and ZooKeeper."
"The product offers good documentation that helps with initial training."
"Its Docker Container concept is mind blowing. It is the first monitoring tool which comes with Docker features."
"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

"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."
"In terms of features that I would like to see or have, in the community version, some features are not available. I would like to have clustering and authentication in the community version."
"InfluxDB cannot be used for high-cardinality data. It's also difficult and time-consuming to write queries, and there are some issues with bulk API."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"One area for improvement is the querying language. InfluxDB deprecated FluxQL, which was intuitive since developers are already familiar with standard querying."
"I've tried both on-premises and cloud-based deployments, and each has its limitations."
"The error logging capability can be improved because the logs are not very informative."
"It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster."
"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."
"The AI aspect needs to improve."
"The inclusion of a feature to show a graphical view of the network would be a helpful improvement."
"Now it is stable, but they should design threshold parameters in percentage instead of raw values."
"It would be ideal if the product offered sound alerts."
"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"
 

Pricing and Cost Advice

"The tool is an open-source product."
"InfluxDB recently increased its price. It is very expensive now."
"InfluxDB is open-source, but there are additional costs for scaling."
"We are using the open-source version of InfluxDB."
"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 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."
"It depends on the customer, what he wants."
"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 Network Monitoring Software solutions are best for your needs.
865,295 professionals have used our research since 2012.
 

Top Industries

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

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
 

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?
It is challenging to get long-running backups while running InfluxDB in a Microsoft Azure Kubernetes cluster. Replicating data for on-prem development and testing is difficult. Having a SQL abstrac...
What is your primary use case for InfluxDB?
InfluxDB is the main component in our large enterprise-scale streaming data application for maritime vessels. We collect position data from vessels around the coast once per second, put it on a Kaf...
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: August 2025.
865,295 professionals have used our research since 2012.