SDK Recommendations

NOTE: Bugsink intentionally focuses only on error events. It does not handle metrics, traces, or other event types. See why we chose this focus.

Bugsink works with the Sentry SDKs, with a few recommended changes to their default configuration.

If you have configured your SDK using the Bugsink UI, your settings will already reflect the recommendations below (but understanding why we recommend them is still useful). If you are moving from Sentry to Bugsink, you may need to adjust your SDK configuration.

  • PII (personally identifiable information): The SDK’s default is not to send PII. We recommend setting send_default_pii to True, because this information is often useful when debugging. Make sure that this is appropriate for your application: when we run Bugsink for you, the data is processed by us; with Self-Hosted Bugsink, it is sent to the installation you control.

  • Traces: Bugsink intentionally does not support traces, so there is no need to send them. traces_sample_rate=0 is set by default.

  • Preserving Local Variables (optional, Python-specific): The SDK’s default is to be quite conservative with the number of local variables it sends per frame (the default is is 10). If you want to see more, you may proceed with the monkey patching described in this issue Note that this solution may result in messages so large that they are dropped by the server. With Self-Hosted Bugsink, you can adjust the server settings to accept them anyway.