InfluxDB Reviews

We use InfluxDB for monitoring all services we have. We have a lot of services.

The most valuable features of InfluxDB are the documentation and performance, and the good plugins metrics in the ecosystem.

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.

In the next release, it would be beneficial if they added more query language compatibility it is critical for us.

I have been using InfluxDB for approximately one year.

The stability of InfluxDB is good. However, it is similar to most solutions, you have to check the volume metric regularly that you use.

We have approximately 50 people using the solution in the organization.

The support from InfluxDB could improve because I contacted them about some features and they did not get back to me. It has been over one month.

The initial setup of InfluxDB is easy. It took a couple of days for the full implementation.

We are using the open-source version of InfluxDB.

I recommend InfluxDB but proceed with caution. They have to have knowledge about the solution.

I rate InfluxDB a seven out of ten.

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.

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.

The initial setup is a little bit complex.

The error logging capability can be improved because the logs are not very informative.

I have been using InfluxDB for approximately one year.

This is a stable product.

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.

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.

I haven't used another similar product before this one. 

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.

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. 

I was also looking into Prometheus but our project manager told us to use InfluxDB. So far, it has been working well for me.

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.

I primarily use the solution for database storage.

The solution is very powerful.

The solution is easy to use and easy to learn.

Influx Series Ten, in particular, is a strong application.

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.

I've been using the solution for two years.

The solution is very stable. I haven't experienced bugs or crashes.

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.

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.

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.

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.

I handled the deployment myself. I didn't need the assistance of a specialist.

I only use the solution a little bit, not too extensively.

I'd rate the solution nine out of ten.