Backtrace supports ingesting crash reports from Google Stadia.
This integration guide will provide instructions using the Google Cloud Console, Google Cloud Shell, or command-line tools (
Google Cloud Console and access to web console of command-line tools.
project_id, cloud storage bucket name, Pub/Sub name and your Service Account Key JSON file. These can all be configured through the user interface but this integration guide provides command line invocations for convenience.
Backtrace instance to push Stadia game crashes too.
Setup and Installation
Following are detailed setup instructions and a 3 minute video to walk you through the steps.
1. Configure Stadia Title to route crashes to Google Cloud Storage
Follow instructions in Google Cloud Develop Stadia “Get Crash Reports” documentation for creating or using an existing Cloud Storage Bucket. Retrieve the
project_id (screenshot below) and bucket name that are in use, and write this information down for reference and use later.
2. Configure Google Cloud Storage topic
gsutil command line to setup a new Topic where Cloud Storage will post a notification for every new object created (finalized) in the Cloud Storage bucket. Below is a command to create a bucket.
gsutil notification create -t <topic> -f json -e OBJECT_FINALIZE gs://<bucket>[/<optional folder>]
gcloud pubsub command to create a Pub/Sub subscription for the topic. See below for the invocation.
gcloud pubsub subscriptions create <subscription_name> --topic=<topic>
Remember the PubSub Subscription name you specified and write this information down for reference and use later.
3. Create a service account key credential in Google Cloud
Navigate in Google Cloud Console to
API & Services > Credentials UI > Create Credentials > Service Account Key to start the process. Choose a “New service account” and specify a “Service account name”. Choose the following roles:
Storage > Storage Admin
Pub/Sub > Pub/Sub Subscriber
Pub/Sub > Pub/Sub Viewer
Specify Key type as JSON and click on
Create. Google will save a
.json file to your desktop - remember where that file is. We will use it in the next step.
4. Configure Backtrace Data Source with the information you have recorded
Go to the Project Settings > Error Submission > Data Sources.
Upload the .JSON file so the Backtrace system can properly authenticate.
Fill in the project_id, bucket_name, and subscription_name that were created in the previous steps.
Save the data source and any new crashes received will be ingested by Backtrace. Use the Data Source to also download historical data
Investigating an Error in Backtrace
Once errors are being reported to your Backtrace instance, you should see them in your Triage and Web Debugger view. See below for a screenshot of the Triage view.
The developer who is debugging the error may find it useful to view more details of Exception. They choose the 'View Latest Trace' action to see more details in the Backtrace Web Debugger. We can see a list of all attributes submitted with a report, the call stack and details of the selected frame, details about the system environment, and more, to further assist with investigation.