I work with a Grafana OSS deployment connected to BigQuery, and have run into issues with users creating queries that habitually time out and/or use excessive BQ slots. Tracking down the dashboard they're coming from is a bit of a headache, and some sort of header information I could look at on the BQ console side of things would make tracking down the problem dashboard much easier.
This idea comes from something I've seen with dbt. It includes a header akin to the following in every query it sends to BQ:
I work with a Grafana OSS deployment connected to BigQuery, and have run into issues with users creating queries that habitually time out and/or use excessive BQ slots. Tracking down the dashboard they're coming from is a bit of a headache, and some sort of header information I could look at on the BQ console side of things would make tracking down the problem dashboard much easier.
This idea comes from something I've seen with dbt. It includes a header akin to the following in every query it sends to BQ:
A grafana relevant implementation would include things like dashboard source and panel information.