You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, SQL queries are included as breadcrumbs, but with placeholders rather than with actual parameters, as this may leak senstive info (e.g. sessions or hashes). This limits their usefulness when debugging issues.
Instead, we should include the parameters in the sentry breadcrumb, but also have a blacklist of sensitive table names, that if present in the query, mean we fall back to the placeholder version of the query to avoid leaking.
We should probably have a default blacklist, e.g. 'user', 'session', as well as allow user to add their own blacklisted tables for their app.
The text was updated successfully, but these errors were encountered:
Currently, SQL queries are included as breadcrumbs, but with placeholders rather than with actual parameters, as this may leak senstive info (e.g. sessions or hashes). This limits their usefulness when debugging issues.
Instead, we should include the parameters in the sentry breadcrumb, but also have a blacklist of sensitive table names, that if present in the query, mean we fall back to the placeholder version of the query to avoid leaking.
We should probably have a default blacklist, e.g. 'user', 'session', as well as allow user to add their own blacklisted tables for their app.
The text was updated successfully, but these errors were encountered: