Connect Google Cloud to ShipVitals
Costs, usage and releases for Google Cloud and Firebase
What it reads
- roles/firebasehosting.viewer
- Reads Hosting release history
- roles/run.viewer
- Reads Cloud Run revisions
- roles/bigquery.dataViewer on the export dataset
- Reads the billing export
- roles/monitoring.viewer
- Reads usage metrics on each project
Read-only: ShipVitals can't change anything at Google Cloud.
What ShipVitals keeps from Firebase Hosting and Cloud Run releases: The reader's email and your project ids; no key exists.
What ShipVitals keeps from Google Cloud billing: The reader's email and the dataset's name; queries run in ShipVitals' project.
What ShipVitals keeps from Google Cloud usage: The reader's email and your project ids; no key exists.
How to connect
Firebase Hosting and Cloud Run releases
- Run the snippet ShipVitals gives you on each Firebase project.
- It grants Firebase Hosting Viewer and Cloud Run Viewer only.
- Choose Check access.
Google Cloud billing
- Turn on the detailed cost export to BigQuery in Billing → Billing export.
- Note the project and dataset the export writes to.
- Run the snippet ShipVitals gives you to grant read access to that dataset.
- Choose Check access.
Google Cloud usage
- Run the snippet ShipVitals gives you on each Firebase project.
- It grants Monitoring Viewer only.
- Choose Check access.
About 3 minutes.
How to revoke
Removing the connection in ShipVitals deletes the stored key at once.
What it powers
Dashboard tabs: Costs, Health.
Figures it fills
- Firestore reads
- Firestore writes
- Firestore deletes
- Cloud Functions calls
- Cloud Run requests
Sync
- Free: Daily
- Indie: Hourly
- Studio: Every 15 minutes
- Agency: Every 15 minutes
Google Cloud reports a day in full after 1 day; ShipVitals waits for it.
Troubleshooting
Each error a connection can hit, and its fix. The connection's health page names the one it hit.
- Access refused
- Google Cloud no longer accepts what ShipVitals signs in with. Create a new key, or connect again, and replace it in the connection.
- A permission is missing
- What ShipVitals has can't read everything it needs. Add the permissions under What it reads, or create a new key with them, and test again.
- Access removed
- ShipVitals' access was removed in Google Cloud. Connect it again; the history it brought in is kept.
- Rate-limited
- Google Cloud billing: This workspace has used its BigQuery scan budget for the month, or {provider} is limiting requests. ShipVitals reads the export again when the budget resets on the 1st; a larger plan has more.
- Quota reached
- The account used up a Google Cloud quota. The sync resumes when the quota resets.
- Not found
- Something the connection reads is gone from Google Cloud: renamed, moved or removed. Review the connection's resources, or connect again.
- Google Cloud is unavailable
- Google Cloud is having trouble on its side. Check its status page; ShipVitals retries by itself.
- Couldn't reach Google Cloud
- The request didn't get through. ShipVitals retries by itself; if it keeps failing, check that Google Cloud is reachable.
- An answer ShipVitals didn't expect
- Google Cloud answered in a shape ShipVitals didn't expect, usually after a change on its side. We're told, and the data you have is kept.
- A setting doesn't work
- A field in the connection doesn't work with Google Cloud. Check it against How to connect, and test again.