Understanding query count in Cloud

I tried to understand my latest InfluxDB Cloud invoice and when doing so I try to understand where the queries generating the query count numbers come from.

It seems like some thousand queries per hour are generated by a Grafana dashboard. The Flux queries executed to get the data are executed every minute but the query count is far higher than that. The Pricing FAQ hints that the query count “broadly” equals a Flux query. Are there cases a Flux query is not the same as a billable query?

I also have a steady stream of 2000 queries per hour that I have no idea where they are coming from. How do I find out where these queries come from? The data from the _monitoring bucket/usage.from() doesn’t tell.

1 Like

Hi PHL did you ever get a reply to this? I am also trying to monitor the query count in real-time to prevent issues like this.
I know in Grafana you can set the Cache per Data Source to 300000ms (customisable) which can help.
They can also set a refresh limit (on request) to prevent the 5sec auto refreshes.

Unfortunately not. After concluding Grafana was causing the queries I ended up moving this statistics to an existing RDB instead. My business rely heavily on InfluxDB in our own product and there are no uncertainties in query count when we control our queries ourself.

Hello @PHL and @JimWilk,
I know that clustered will provide users with far more operator control and custom partitioning to optimize query performance.

However I don’t know about product plans for improved monitoring of InfluxDB.