Crashlytics BigQuery integration table expiration

0
votes

Is it possible to set the default table expiration that is used when enabling the Crashlytics Big Query integration in Firebase?

We are trying to reduce our monthly Firebase costs (Blaze plan) that are due to the amount of data exported automatically and now exists in our BigQuery tables. These are the costs that appear in our Firebase billing reports as "non Firebase services".

To reduce the costs we would like to allow the data to expire automatically and adjust the "time to expire" shown below for all ongoing data exported from Firebase to BigQuery.

Is this possible from within the Firebase console itself? Or can this only be done in BigQuery using the CLI? This page doesn’t seem to give any indication that this is possible from the Firebase Console itself: https://firebase.google.com/docs/crashlytics/bigquery-export

But we can see from the BigQuery docs that Table Expiration appears to be what we need to set, our question is essentially how to do this to apply for all existing and future tables streamed from Firebase Crashlytics (but also Events and Performance) data.

Thanks for any advice!

1
firebasegoogle-bigquerycrashlytics

1 Answers

1
votes

You can limit data in BigQuery by setting the retention time right in the BigQuery console to whatever length of time you prefer:

  • Set default table expiration times here
  • Update a particular table's expiration time here

The size of exported data highly depends on the product usage. Moreover, especially for Crashlytics, stacktrace in the data is completely unpredictable. In order for you to have an idea of the cost, You can check following links:

Additionally, please follow following documentation, which has clearer insight on the export data to BigQuery.