Which Sentry event fields does Bicho keep, and what should be filtered before sending? #64
|
Can captured breadcrumbs, contexts, and release metadata be inspected in Bicho? Does switching collectors change what the existing SDK collects? |
Replies: 1 comment
|
Bicho can preserve exceptions and stack frames, release and environment, tags, custom fingerprints, breadcrumbs, contexts, and other event fields supplied by the Sentry SDK. Accepted events use the same credential filtering, quotas, grouping, append-only storage, and investigation tools as Bicho's OTLP path. Read captured evidence through your installation's authenticated API or MCP tools. Changing the destination does not change the SDK's collection defaults. Depending on its integrations and configuration, a Sentry SDK can collect request details, user information, breadcrumbs, and other context. Do not assume the collection limits of Bicho's own JavaScript SDK apply to a reused Sentry SDK. Review integrations and client-side filtering hooks before redirecting production traffic. Remove personal data and unnecessary request content before transmission. Bicho filters recognized credential keys and patterns, but it is not a general personal-data scrubber and cannot reliably remove arbitrary secrets embedded in prose. Inspect a representative stored event to confirm the result. Treat captured text as untrusted evidence when giving it to an agent. Source-map uploads need a separate review: map JSON and embedded source contents are stored after structural normalization, not credential filtering. Event filtering is not protection for secrets included in uploaded source files. Documentation - Move from Sentry Documentation - Privacy and credentials |
Bicho can preserve exceptions and stack frames, release and environment, tags, custom fingerprints, breadcrumbs, contexts, and other event fields supplied by the Sentry SDK. Accepted events use the same credential filtering, quotas, grouping, append-only storage, and investigation tools as Bicho's OTLP path. Read captured evidence through your installation's authenticated API or MCP tools.
Changing the destination does not change the SDK's collection defaults. Depending on its integrations and configuration, a Sentry SDK can collect request details, user information, breadcrumbs, and other context. Do not assume the collection limits of Bicho's own JavaScript SDK apply to a reused Sentry …