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.

Initially, we used Prometheus and Grafana for alerts. But, it wasn't feasible to handle logs and other types of databases. We then switched to InfluxDB due to its user interface, which allowed us to customize alerts, data visualization, and filtering for monitoring purposes. 

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.

I'm using InfluxDB to store documents related to the database and to populate data through their funnel.

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

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

I primarily use the solution for database storage.

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.