Bugsnag
Step-by-step guide to send your app event data from RudderStack to Bugsnag.
Last updated
Was this helpful?
Step-by-step guide to send your app event data from RudderStack to Bugsnag.
Last updated
Was this helpful?
Bugsnag provides error reporting libraries for every major software platform which automatically detect and report errors in your applications, and capture diagnostic data required to help you reproduce and fix each error.
Bugsnag monitors application stability so you can make data-driven decisions on whether you should be building new features, or fixing bugs.
To enable sending data when application crashes to Bugsnag, you will first need to add it as a destination to the source from which you are sending your event data. Once the destination is enabled, events from our SDK will start flowing to Bugsnag.
Connection Mode
Web
Mobile
Server
Device mode
Supported
Supported
-
Cloud mode
-
-
-
To know more about the difference between Cloud mode and Device mode in RudderStack, read the RudderStack connection modes guide.
Once you have confirmed that the platform supports sending events to Bugsnag, perform the steps below:
From your RudderStack dashboard, add the source. From the list of destinations, select Bugsnag.
Give a name to the destination and click on Next. You should then see the following screen: Connection settings for Bugsnag
Add your API key to your connection settings. You can find your API key in your Bugsnag dashboard under “Settings”, which is located in the upper left-hand corner.
Click on Next to complete the configuration. Bugsnag should now be added and enabled as a destination in RudderStack.
Android iOS Please follow the steps below to add Bugsnag to your Android Project:
Add the following repository
to your app/build.gradle
file.
After that, add the following dependencies
in the same file:
Finally, change the initialization of your RudderClient
in your Application
class
Follow these steps to add Bugsnag to your iOS project:
Go your Podfile
and add the Rudder-Bugsnag
extension
After adding the dependency followed by pod install
, you can add the imports to your AppDelegate.m
file as shown:
Finally, change the initialization of your RudderClient
as shown:
The identify
call lets you associate a user to their actions and capture all the relevant traits about them. This information includes a unique userid
as well as any optional information such as name, email address, etc.
An example identify
call from our JS source looks like this:
Bugsnag will show you the userId
and traits
in the Users tab of each error.
Along with user-specific information, you can also use Bugsnag to track handled exceptions data to your dashboard using Bugsnag’s native methods. You can find the documentation for these functions on their website.
You can find your API Key on your Bugsnag Project Settings page.
You can distinguish errors that happen in different stages of your app’s release process e.g production
, development
, etc.
You should definitely use SSL When Sending Data to Bugsnag specifically from JS source.
If you come across any issues while configuring Bugsnag with RudderStack, please feel free to contact us or start a conversation in our Slack community. We will be happy to help you.