Bugsink is compatible with the Sentry SDK. However, since Bugsink is self-hosted, we have some different recommendations for the SDK 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 to not send PII; for a SaaS solution this is
probably the right choice to avoid sending even more sensitive data to a third party. Bugsink is self-hosted, so we
recommend setting send_default_pii to True so that you have as much information as possible to debug issues.
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 either proceed with the monkey
patching described in this issue, or set
max_request_body_size to "always" (which will send everything). Note that both these solutions may result in
messages so large that they are dropped by the server. Because Bugsink is self-hosted, you can adjust the server
settings to accept them anyway.
