-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ui: obtain redacted statement diagnostics bundles from the DB console #119040
Comments
In 23.1 we also added:
Maybe these should also be exposed through the DB console somehow? |
#123859 made all the necessary changes to the backend (added new overloads to |
When users with the `VIEWACTIVITY` role activate statement diagnostics via the modal in SQL Activity, they now have the option to redact the output via a checkbox. Resolves: cockroachdb#119040 Epic: CRDB-37557 Release note (ui change): when activating statement diagnostics in the DB Console, users now have the option to produce a redacted bundle as output. This bundle will omit sensitive data.
134229: changefeedccl: fix race in test r=andyyang890 a=asg0451 Fix a data race in duration overrides in tests. Fixes: #133817 Release note: None 134723: ui: add Redact option to stmt diag activation modal r=kyle-a-wong a=dhartunian When users with the `VIEWACTIVITY` role activate statement diagnostics via the modal in SQL Activity, they now have the option to redact the output via a checkbox. Resolves: #119040 Epic: CRDB-37557 Release note (ui change): when activating statement diagnostics in the DB Console, users now have the option to produce a redacted bundle as output. This bundle will omit sensitive data. 134746: scjob: support handling permanent job errors r=fqazi a=fqazi Previously, when a descriptor was detect as a dropped the error was marked as permanent for schema change jobs. However, the declarative schema change job framework did not properly handle these errors. As a result, even if the erorr was tagged we would keep attempting rollbacks. To address this, this patch makes the OnFailOrCancel logic detect permanent errors and allows them to cause the schema change to hit the terminal state. Fixes: #131405 Release note: None Co-authored-by: Miles Frankel <[email protected]> Co-authored-by: David Hartunian <[email protected]> Co-authored-by: Faizan Qazi <[email protected]>
134723: ui: add Redact option to stmt diag activation modal r=kyle-a-wong a=dhartunian When users with the `VIEWACTIVITY` role activate statement diagnostics via the modal in SQL Activity, they now have the option to redact the output via a checkbox. Resolves: #119040 Epic: CRDB-37557 Release note (ui change): when activating statement diagnostics in the DB Console, users now have the option to produce a redacted bundle as output. This bundle will omit sensitive data. Co-authored-by: David Hartunian <[email protected]>
When users with the `VIEWACTIVITY` role activate statement diagnostics via the modal in SQL Activity, they now have the option to redact the output via a checkbox. Resolves: cockroachdb#119040 Epic: CRDB-37557 Release note (ui change): when activating statement diagnostics in the DB Console, users now have the option to produce a redacted bundle as output. This bundle will omit sensitive data.
134525: kvserver: avoid key heap allocation in multiSSTWriter.rolloverSST r=tbg a=sumeerbhola rolloverSST is called for every key-value pair in the incoming snapshot, and the key parameter was inadvertently escaping to the heap. This was 20% of the number of allocations on a node in the 150 node cluster test. Epic: none Release note: None 134723: ui: add Redact option to stmt diag activation modal r=dhartunian a=dhartunian When users with the `VIEWACTIVITY` role activate statement diagnostics via the modal in SQL Activity, they now have the option to redact the output via a checkbox. Resolves: #119040 Epic: CRDB-37557 Release note (ui change): when activating statement diagnostics in the DB Console, users now have the option to produce a redacted bundle as output. This bundle will omit sensitive data. 134919: sql: fix FETCH ABSOLUTE 0 cursor handling r=yuzefovich a=yuzefovich `FETCH ABSOLUTE 0` positions the cursor before the first row, so nothing should be fetched. Previously, this would result in an internal error because we'd be working on unset datums. Fixes: #131115. Release note (bug fix): Previously, CockroachDB would encounter an internal error when evaluating `FETCH ABSOLUTE 0` statements, and this is now fixed. The bug has been present since 22.1 version. Co-authored-by: sumeerbhola <[email protected]> Co-authored-by: David Hartunian <[email protected]> Co-authored-by: Yahor Yuzefovich <[email protected]>
Based on the specified backports for linked PR #134723, I applied the following new label(s) to this issue: branch-release-24.3. Please adjust the labels as needed to match the branches actually affected by this issue, including adding any known older branches. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
When users with the `VIEWACTIVITY` role activate statement diagnostics via the modal in SQL Activity, they now have the option to redact the output via a checkbox. Resolves: #119040 Epic: CRDB-37557 Release note (ui change): when activating statement diagnostics in the DB Console, users now have the option to produce a redacted bundle as output. This bundle will omit sensitive data.
In 23.1 we added the ability to collect redacted statement diagnostics bundles using
EXPLAIN ANALYZE (DEBUG, REDACT)
which was tracked by #68570 and #98817.In order to make collection of these redacted bundles easier, we should add a redaction option to the DB console's existing UI for bundle collection.
We should probably also add a redaction option to
crdb_internal.request_statement_bundle()
.Jira issue: CRDB-35994
Epic CRDB-37557
The text was updated successfully, but these errors were encountered: