InfluxDB Reviews

Our usage of Influx is very specific. We use it for our casino stack and applications. We use it for monitoring, logging, and metrics and trend analysis for player wagering. It is for casino data. We correlate all that data and generate reports for data warehousing. So, we use it massively in our stack for the casino for a lot of things. 

We haven't yet migrated to Influx 2.0. We are still using Influx 1.8 because we have multiple workloads in production. It is going to take some time, and we need to ensure that the latest one is stable and the framework also brings a lot of different languages.

We use it on-premise and in the cloud. We have both. It is a private cloud on AWS.

In our case, it started with a necessity to fill the gap that we had in monitoring. We had very reactive monitoring without trend analysis and without some advanced features. We were able to implement them by using a time series database. We are able to have all the data from applications, logs, and systems, and we can use a simple query language to correlate all the data and make things happen, especially with monitoring. We could more proactively monitor our systems and our players' trends.

We can integrate it with everything. It has an API. We can put any data there. We are developing apps. We are creating scripts. We are doing lots of things. There are different ways to configure it. As a database, it just has to ensure that data is there, and it is properly stored with the tags, fields, measurement names, and time stamps. The focus is that the data that you put in there is perfectly stored. 

I use Kapacitor a lot. It is the feature that allows us to create batch jobs and interact with the data that we have. That's the most interesting feature. 

The query language is very similar to SQL, which is very useful because most of us have a background in SQL language.

They have the Telegraf agent that gets the data and puts it in Influx. We can also put data into Influx through the API. We are doing a lot of custom-based agents and a lot of scripts that are adding data to Influx. As a time series database, it is very powerful and lightweight. It can deal with heavy workloads very easily. That, for me, is the main advantage of Influx as compared to other databases. 

Influx has TICK Stack, which contains multiple services and multiple products that work together. InfluxDB is just a time series database, and it works really well. I haven't yet had the time to look into the new stack based on Influx 2.0, but currently, as a time series database, InfluxDB is working the way it is supposed to work. 

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. 

I would also like to have high availability features, such as replication, active-active, etc. If they can put an extra plugin or service on top of it, it would be something interesting. I am not sure if they have high availability to make it data center-aware for clustering. For example, I am not sure whether you can have it at different locations with big clusters that are location-aware. Even in their documentation or presentation, they talk too little about high availability and extended clusters with different locations. They might already have it in the newer versions. We have Influx 1.8 in our production in the stage and internal workloads environments. 

The other products in their ecosystem, such as Chronograf, can be improved. Chronograf is a dashboarding or visualization layer product, and that, for sure, can be improved.

I have been using this for five years.

I really like it. I always recommend the stack to lots of friends I have in other places. It is really good, and it helped us a lot.

We will see scalability with the new version. In terms of its users, everything is automated. So, there are almost zero users. Admins and DevOps are the only ones that go to Influx to manage or implement any kind of tweaks, improvements, or developments, but it touches almost everyone, which includes managers who do reports regarding the business, data warehousing, our 24/7 teams for monitoring, developers, and system administrators. They go to Grafana, and they have all the dashboards for system availability and everything else. It touches almost everyone.

It is being used extensively. As the business grows and we create a new environment, a huge part of the management of that environment comes from Influx. It is one of the primary stacks that we build for monitoring and reporting. Because everything is in Influx, it always comes first.

I did a search and used the community forums and help, but I never had to contact them. Their community is really big, helpful, and active. It is very easy to just go to their support site and search for solutions or ask questions. That's another thing where they are very good.

We mainly went from Icinga. It is like Nagios. So, we were using Nagios monitoring, but because the monitoring was so reactive, we wanted something new that could help us with the business requirements. We needed something that could host the metrics and data from multiple sources and can be used to correlate. It was because of the necessity we moved away from Nagios, which is very focused on systems monitoring, to something that uses a time series database and has a simple SQL query language that we can use to correlate data and create trends.

We implemented everything. The setup is straightforward. There is a learning curve, but the setup is very easy. They have repositories for most distributions. You just have to install from a binary, and the entire stack of Influx is up and running. For most operating systems, they already have repositories that allow you to just install it with one command. I would rate it a ten out of ten in terms of ease of setup. 

In terms of duration, deploying InfluxDB took minutes. It is like installing an app on your laptop. It is very easy and quick to deploy InfluxDB, but deploying what we have has been an ongoing process for the last five years.

I implemented it myself. In terms of maintenance, it is very lightweight. We just ensure that Influx doesn't get any updates other than the security updates that are always coming from the repository. It is very simple to maintain and update.

I went straight to Influx. I came across Influx, and I tried it, tested it, and learned a little bit more about it. I saw that this would do what we needed and meet our requirements.

It depends a lot on what you are going to use it for but just enjoy it. It is very powerful. I would advise learning the TICKscript language. I know that the latest Influx 2.0 is using a different language than Influx SQL, but I would advise learning how to develop using their framework. You will see how powerful it is to use for a big data cluster. So, explore the batch processing and the scripting language that they have in 2.0. We use TICKscript, which is very powerful and allows you to do everything you need.

I would rate it an eight out of ten.

My main use case for InfluxDB involves gathering metric data from our storage clusters and putting them into Grafana dashboards, so InfluxDB is the data source for Grafana.

I collect and display metrics in Grafana such as throughputs, IOPS, latencies, quota consumptions, network and cart errors.

Regarding my main use case, there are no particular challenges; we run our scripts every five minutes, so we gather data from our clusters every five minutes and keep more than six months.

The best features InfluxDB offers include a web UI that I love because sometimes I need to check some details about my metrics, enabling me to easily see simple details on it.

While the API does not stand out to me since we don't use it regularly for InfluxDB, we primarily use it as a data source for Grafana.

InfluxDB has positively impacted my organization by being a part of our solution, which helps us maintain our solution easily.

It helps me maintain my solution easily because it is very reliable, so we didn't face any performance issues or crashes regarding our queries; we can get the results very fast.

I believe InfluxDB can be improved, but I'm not sure how; maybe some people can say more than me, but for myself, it is enough.

I don't have any additional improvements to suggest regarding documentation, UI, or anything else that I wish was different; nothing comes to mind.

I have been using InfluxDB almost for two years.

InfluxDB is stable.

We haven't faced any issues with InfluxDB's scalability; maybe our capacity consumptions are small, or it is simply good enough to handle that much capacity.

I did not previously use a different solution; there was no switch required.

We do not purchase InfluxDB through the AWS Marketplace; instead, we use the open-source version.

I haven't seen a return on investment; unfortunately, I cannot share relevant metrics such as time saved, fewer employees needed, or money saved.

I'm not sure about the details regarding pricing, setup cost, and licensing.

Before choosing InfluxDB, I only evaluated Prometheus, but it is not the right solution for us because it has a different methodology than InfluxDB, which exactly matches our requirements.

My advice to others looking into using InfluxDB is that if they need any time-series database, InfluxDB is a good solution with its stable, high performance, and scalable capabilities, and I love the web UI, which also allows us to create dashboards without any other third-party tools.

On a scale of one to ten, I rate InfluxDB a ten.

I use the solution to store and manage data from various sensors in a production environment. I have developed a system where data from these sensors is communicated through an OPC UA receiver and stored in InfluxDB. It handles serial data from sensors effectively and integrates well with Grafana for visualization.

The platform operates very quickly. It is easy to configure, connect, and query and integrates seamlessly with Grafana.

I have been using InfluxDB for four years.

I have not experienced any stability issues with the product. 

Approximately 20% of our team uses InfluxDB.

I recommend InfluxDB to others and rate it a ten. 

I use InfluxDB for querying based on time ranges and window operations.

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.

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. 

I've been using InfluxDB for a year.

InfluxDB is stable.

InfluxDB is scalable, but if you want to scale it on an enterprise level, you'll have to spend lots of money on licenses.

The initial setup is easy, but it takes time at first to understand and set up InfluxDB.

InfluxDB is open-source, but there are additional costs for scaling.

I recommend going with the cloud version of InfluxDB, as it's very cheap and effective. InfluxDB is very powerful, but it requires some technical skill and can't be used by just anyone. I would rate InfluxDB seven out of ten.

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.