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

InfluxDB vs Zenoss Cloud comparison

Why PeerSpot?
 

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
14th
Ranking in IT Infrastructure Monitoring
12th
Average Rating
8.0
Reviews Sentiment
6.5
Number of Reviews
20
Ranking in other categories
Non-Relational Databases (1st), Open Source Databases (7th), NoSQL Databases (6th)
Zenoss Cloud
Ranking in Network Monitoring Software
64th
Ranking in IT Infrastructure Monitoring
50th
Average Rating
8.4
Reviews Sentiment
7.1
Number of Reviews
8
Ranking in other categories
Application Infrastructure (19th), Event Monitoring (14th), Server Monitoring (25th), Container Monitoring (8th), Cloud Monitoring Software (41st), AIOps (28th)
 

Mindshare comparison

As of September 2026, in the Network Monitoring Software category, the mindshare of InfluxDB is 0.5%, up from 0.4% compared to the previous year. The mindshare of Zenoss Cloud is 0.9%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Network Monitoring Software Mindshare Distribution
ProductMindshare (%)
InfluxDB0.5%
Zenoss Cloud0.9%
Other98.6%
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

"InfluxDB positively impacts my organization because I have optimized my database storage, and by using powerful queries, I am able to find my data logs efficiently and also manage logging."
"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 feature of the solution is we can use InfluxDB to integrate with and plug into any other tools."
"The solution is very powerful."
"InfluxDB has positively impacted Energy Box by being the best choice for our needs."
"This product has been working well and it is serving our purpose, so I can recommend it to others."
"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."
"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."
"The product offers good documentation that helps with initial training."
"It is very cost-effective compared to the tools I worked with in the past."
"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."
"The most valuable feature is the flexible discovery mechanism."
"Overall, it's a great solution, and I consider it to be one of the best."
"Zenoss is more complex than LogicMonitor, but scalable and hugely customizable."
 

Cons

"However, I do wish the documentation and community resources around Flux were more extensive and beginner-friendly."
"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."
"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."
"The interface of InfluxDB is so complex and should be made easier for non-technical people."
"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."
"InfluxDB can be improved by addressing issues such as performance drops, queries being more difficult to understand, and its high memory usage."
"This solution is complex for beginners so it takes some time to learn."
"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."
"It would be ideal if the product offered sound alerts."
"Technical support is 3/10, poor: Incomplete and poor documentation Undocumented processes Inconsistent solutions to problems depending on source"
"There was a problem with Zenoss and storage monitoring."
"Now it is stable, but they should design threshold parameters in percentage instead of raw values."
"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

"We are using the open-source version of InfluxDB."
"InfluxDB is open-source, but there are additional costs for scaling."
"The tool is an open-source product."
"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."
"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.
913,924 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Comms Service Provider
11%
Financial Services Firm
10%
Manufacturing Company
10%
Outsourcing Company
9%
Comms Service Provider
14%
Construction Company
13%
Manufacturing Company
8%
Outsourcing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise5
Large Enterprise9
By reviewers
Company SizeCount
Small Business4
Large Enterprise5
 

Questions from the Community

What needs improvement with InfluxDB?
If the dashboarding facility can be improved in terms of the visualization parameters and the amount of support available from the community, as well as having smarter alerts to send those alerts t...
What is your primary use case for InfluxDB?
My main use case for InfluxDB is to inject all my performance data and visualize it as a data source into Grafana. My data comes from JMeter from a plugin, which is inserting data to InfluxDB, and ...
What advice do you have for others considering InfluxDB?
It is good to start with InfluxDB to stabilize your data, visualize your data, and have the data stored on a time-series basis. I would recommend everyone to get into InfluxDB and start using it. T...
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: September 2026.
913,924 professionals have used our research since 2012.