Grafana Dashboard: Non-existent GCE Default Service Account used fetch from BigQuery by default

dora-team / fourkeys

Platform for monitoring the four key software delivery metrics of software delivery

Apache License 2.0

2.17k stars 595 forks source link

Grafana Dashboard: Non-existent GCE Default Service Account used fetch from BigQuery by default #284

Closed jvasallo closed 2 years ago

jvasallo commented 2 years ago

Running through the default setup, the original Grafana Datasource is hardcoded to use GCE Service Account (which is not created by default).

I ended up needing to create my own JSON Key and manually create a secondary BigQuery Source using that key. Not sure if this is expected :)

davidstanke commented 2 years ago

Thanks for the report, @jvasallo! Sounds like we need to explicitly depend on the custom service account (which we are are already creating, so might as well use it here, too).

martasd commented 2 years ago

Hi. I cannot see the mock data in Grafana some time after running the script. Is it caused by this issue?

rogerthatdev commented 2 years ago

Since the Grafana dashboard does not run from a GCE instance it doesn't actually use the default GCE service account. Instead is uses the service account fourkeys@[PROJECT_ID].iam.gserviceaccount.com that is created during setup and included on the dashboard Cloud Run service configuration.

Try the following:

Make sure the Big Query tables contain data.
Make sure that the fourkeys service account has the Big Query User role assigned on the project that includes your BigQuery data.