Connect Firebase
If your app uses Firebase, Seylo can show its crashes and performance on Observability → Mobile apps, and Nightshift can cite an app’s crashes as a lead when a backend alert fires. It reads Firebase’s BigQuery export where it lives, in your own Google Cloud project. Nothing is copied to Seylo, and Seylo stores only the connection: which project, which cloud account, and whether user ids are shown.
What you need
Section titled “What you need”- A Google Cloud account already connected on Cloud accounts. It is keyless and read-only. Seylo runs the queries in that project, using the read access the account already has.
- Firebase’s BigQuery export switched on (below).
- The Firebase project id: Firebase console → Project settings → General → Project ID.
Switch on the export in Firebase
Section titled “Switch on the export in Firebase”You need the Owner or Firebase Admin role.
-
Firebase console → Project settings → Integrations → BigQuery → Link.
-
Crashlytics: switch it on, and tick Include sessions. Without sessions Seylo cannot show crash-free users, because the Crashlytics table holds crash events only and never the installations that did not crash.
-
Crashlytics streaming, if the project is on the Blaze plan. Without it, crashes appear a day or more after they happen.
-
Performance Monitoring: switch it on.
Google says the first export can take up to 48 hours. Until a table exists, Check says the export datasets hold no app table yet and tells you to press Check again the next day.
Connect it
Section titled “Connect it”-
Open Integrations → Firebase (
admin), choose the connected Google Cloud account, and enter the Firebase project id. -
Press Check. It reads metadata and runs one free test read, and stores nothing. It ends in one of these:
Check says What to do Ready: N apps in the project can be read in place; nothing is copied to Seylo Press Connect Seylo’s service account may not read the named datasets Run the one command the page shows, once, in Cloud Shell, then press Check again The export datasets hold no app table yet, or the project has no export Switch the export on (above), or wait for the first export The BigQuery API is not enabled in the project Run the gcloud services enableline it shows, then Check againSeylo’s service account may not run a query Check that it still holds roles/vieweron the project and that no deny policy removesbigquery.jobs.create -
Connect is enabled only when the check says ready. The check is stored on the connection, and Check again refreshes it any time.
The one command
Section titled “The one command”When the Firebase project is the same project you connected, access is usually
already there. Otherwise the page shows one command that grants read on the
export datasets only, roles/bigquery.dataViewer, to Seylo’s service
account, and nothing else in the project. It names only the datasets that were
refused. Someone who can change those datasets’ access runs it once.
Seylo asks for read on the datasets and the right to run a query. It does not ask for a project-wide data role or for permission to change anything.
What each read costs you
Section titled “What each read costs you”Every page view is a BigQuery query in your project. Seylo bounds it:
- at most 10 GiB billed per query;
- only the export’s partitions for the window, and only the window’s events (1, 7 or 30 days);
- a limit on rows: 50 issues, 5 events for one issue, 20 screens and 30 URL patterns.
The first 1 TiB a month is free on BigQuery’s on-demand pricing. Answers are kept for 1 hour for an app on the daily batch export and 5 minutes when streaming is on. Nightshift reads at most twice per run. A Check is metadata plus a dry run, which is free.
Who sees the data
Section titled “Who sees the data”Observability → Mobile apps is for people whose access is not limited to some namespaces, because an app belongs to the project, not to a namespace.
User ids are off by default. On Integrations → Firebase, an admin can
turn on Show user ids. Without it, user ids are never selected from
BigQuery. Installations leave BigQuery only as counts.
Seylo removes email addresses, phone numbers, card numbers, tokens and keys from crash messages, custom keys, logs and breadcrumbs before it shows them. A name typed into free text is not recognised. Stack frames keep their file and line.
Remove the connection
Section titled “Remove the connection”Remove on Integrations → Firebase (admin) deletes the connection.
If a grant was asked for, the page shows the matching REVOKE command. Run it
to take the dataset access back.
Troubleshooting
Section titled “Troubleshooting”| You see | Why |
|---|---|
| Crash-free users: Unavailable, because the sessions export is off | Tick Include sessions in Firebase’s Crashlytics BigQuery settings |
| Not shown: N installations crashed but only M recorded a session | The two exports disagree: the sessions export may have started later, or the app’s SDK is too old to send sessions |
| Unavailable, because no installation recorded a session in this window | There is nothing to divide by yet |
| A read fails because it would read over 10 GiB, or because the table is not partitioned | Shorten the window or filter the issues; the message says which |
See Mobile apps for what the page shows.