I primarily use the solution for database storage.
Engineer at IT Specialist LLC
Stable, easy to use, and very powerful
Pros and Cons
- "The solution is very powerful."
- "The solution doesn't have much of a user interface."
What is our primary use case?
What is most valuable?
The solution is very powerful.
The solution is easy to use and easy to learn.
Influx Series Ten, in particular, is a strong application.
What needs improvement?
The solution doesn't have much of a user interface.
The integration of Chronograf and Capacitor is not so good. They could work to make it better.
For how long have I used the solution?
I've been using the solution for two years.
Buyer's Guide
InfluxDB
May 2025

Learn what your peers think about InfluxDB. Get advice and tips from experienced pros sharing their opinions. Updated: May 2025.
851,604 professionals have used our research since 2012.
What do I think about the stability of the solution?
The solution is very stable. I haven't experienced bugs or crashes.
What do I think about the scalability of the solution?
I've never tried to scale the solution, so I don't know how easy it would be. However, I do think it is possible to scale if you need to.
In my organization, only five people are currently using it.
How are customer service and support?
I've never contacted technical support. If I have questions, I look at forums to find the answers that I need. I've found their forums to be very good and quite helpful.
Which solution did I use previously and why did I switch?
I often use another product as well to obtain a graph for the data centers and for virtualization. I can't remember the name of it, however.
How was the initial setup?
The solution's initial setup is very straightforward. I didn't find it to be complex at all.
Deployment only takes a few hours. It should only take two or three hours at a maximum.
What about the implementation team?
I handled the deployment myself. I didn't need the assistance of a specialist.
What other advice do I have?
I only use the solution a little bit, not too extensively.
I'd rate the solution nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Software Engineer at a tech services company with 5,001-10,000 employees
Good log aggregation features and integration with Grafana
Pros and Cons
- "The most valuable features are aggregating the data and integration with Graphana for monitoring."
- "The error logging capability can be improved because the logs are not very informative."
What is our primary use case?
We don't use a managed service. Rather, we manage it ourselves. We have deployed it and right now, we are using it for log aggregation with a two-week retention policy.
What is most valuable?
The most valuable features are aggregating the data and the integration with Grafana for monitoring.
We have been looking at the continuous query feature and think that it might solve one of our use cases, but we have not implemented it yet. We are trying to do that now.
What needs improvement?
The initial setup is a little bit complex.
The error logging capability can be improved because the logs are not very informative.
For how long have I used the solution?
I have been using InfluxDB for approximately one year.
What do I think about the stability of the solution?
This is a stable product.
What do I think about the scalability of the solution?
You can scale InfluxDB but the initial cluster that we had is still serving our purpose, so we don't have to scale up. We are a team of people who use it.
How are customer service and technical support?
We have not contacted technical support for InfluxDB yet. When we have a problem, we consult with our other teams, and most of the time, they solve our problems.
Which solution did I use previously and why did I switch?
I haven't used another similar product before this one.
How was the initial setup?
The initial setup was a little bit complex for a cluster. When trying to join the cluster, we were failing. We looked at the log but it was not very informative. We agreed to try a few things and after a while, we were able to join the cluster. That is the difficulty that we had.
What about the implementation team?
I deployed it myself.
In our company, there are many different teams that use InfluxDB for different projects. For example, I am one of the people on our new project, and my colleague is responsible for maintaining and updating it, for this project specifically.
Which other solutions did I evaluate?
I was also looking into Prometheus but our project manager told us to use InfluxDB. So far, it has been working well for me.
What other advice do I have?
This product has been working well and it is serving our purpose, so I can recommend it to others.
I would rate this solution an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.

Buyer's Guide
Download our free InfluxDB Report and get advice and tips from experienced pros
sharing their opinions.
Updated: May 2025
Product Categories
Open Source Databases Non-Relational Databases Network Monitoring Software IT Infrastructure Monitoring NoSQL DatabasesPopular Comparisons
Datadog
Zabbix
New Relic
Juniper Mist Premium Analytics
MySQL
PostgreSQL
PRTG Network Monitor
Redis
MongoDB
Centreon
Nagios Core
Checkmk
ScienceLogic
ITRS Geneos
Splunk Observability Cloud
Buyer's Guide
Download our free InfluxDB Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- When evaluating Open Source Databases, what aspect do you think is the most important to look for?
- Did you switch from a different solution to MySQL? Can you list a few pros and cons for making the move?
- Which database is the best for session cashing?
- Why is Open Source Databases important for companies?
- Which low-code (no-code) database solution do you prefer?