Segment makes it easy to send your data to Bugsnag (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Bugsnag in the format they understand. Learn more about how to use Bugsnag with Segment.
Once a Segment library is integrated with your app, toggle Bugsnag on in your Segment destinations catalog, and add your API Key, which you can find in your Bugsnag app settings. These new settings will take up to an hour to propogate to all of your existing users. Or if you just added the iOS or Android library to your app code, it’ll be instanteneous!
The next thing you’ll want to do is
identify the user, so that Bugsnag can provide you a full picture of what’s causing every error!
Bugsnag can show you the
traits in the Users tab of each error. This can help you figure out what’s causing the error. You can record this data with the
identify method. You should make the
identify call as soon as you know the user’s identity. This usually happens after they log in or sign up.
You can send handled exceptions and diagnostic data to your Bugsnag dashboard using Bugsnag native methods. Documentation on these methods is available on their website.
Supported Sources and Connection Modes
To learn more about about Connection Modes and what dictates which we support, see here.
This destination requires a Device-based Connection Mode for Mobile data. Follow the steps above to ensure you have packaged the Bugsnag SDK with Segment’s.
Segment lets you change these destination settings via your Segment dashboard without having to touch any code.
You can find your API Key on your Bugsnag Project Settings page.
Distinguish errors that happen in different stages of your app’s release process e.g ‘production’, ‘development’, etc.
Use SSL When Sending Data to Bugsnag