BugSnag automatically captures a variety of data to help you debug your errors. You may wish to avoid capturing some types of data, particularly if there are privacy implications for your users.
Information about Unreal Engine can be useful to identify if an error occurs in certain versions.
The following data is collected and added to the Metadata field of a BugsnagEvent. This data can be removed by clearing the following keys from Metadata:
| Section | Key | Description |
|---|---|---|
unrealEngine |
version |
The version of Unreal Engine used by the application |
unrealEngine |
gameStateName |
The current GameState class name |
unrealEngine |
mapUrl |
The local url of the current map or level |
unrealEngine |
userActivity |
The most recent activity from FUserActivityTracking |
device |
gpuAdapterName |
GRHIAdapterName |
device |
gpuDriverVersion |
GRHIAdapterInternalDriverVersion |
Breadcrumbs are automatically recorded for common actions and can be helpful to reproduce errors.
The following breadcrumbs are collected and can be filtered/amended in a breadcrumb callback block or disabled by its type using the Enabled Breadcrumb Types configuration option:
| Message | Type | Description |
|---|---|---|
| Game state changed | State |
The GameState class has changed |
| Map Loading | Navigation |
Map loading has started |
| Map Loaded | Navigation |
Map loading has finished |
| User activity changed | User |
User activity has been notified via FUserActivityTracking |
The following information is automatically captured by BugSnag when running a Unreal Engine app on Android.
To prevent collection, update the data in event callbacks and session callbacks.
The following information is automatically captured by BugSnag when running a Unreal Engine app on iOS.
To prevent collection, update the data in in event callbacks and session callbacks.