Open yuzefovich opened 3 years ago
@yuzefovich, can you provide more details on this issue? Did the user already have the MODIFYCLUSTERSETTING privilege?
Unfortunately, I don't know any other details.
Perhaps @glennfawcett can check how we collected these stmt bundles during an escalation.
I saw this again with a statement bundle from a CC cluster. We can try reproducing there. We should prioritize fixing this because it's preventing us from debugging customer issues.
@kevin-v-ngo @maryliag I just updated the issue description with some more information. This issue is now about highlighting in the DB Console when there were some issues when collecting a bundle making that bundle incomplete. #105005 makes some improvements with the bundle itself as well as the output of EXPLAIN ANALYZE (DEBUG)
in the SQL shell. It seems like it's now purely cluster o11y issue, so I'll remove from our board.
@yuzefovich how can we identify that the bundle is incomplete? is there a specific flag or column value that we can check?
That information is not currently stored in the system table explicitly - as of #105005 non-critical errors will be included into errors.txt
file in the bundle. We'll need to expose the fact that the bundle is incomplete for DB Console, but it should be a pretty easy task.
Whenever a statement bundle collection is requested from the DB Console, it might result in a bundle that is incomplete. For example, this can happen when the user doesn't have the privileges for all things in the bundle (e.g. the user cannot read cluster settings). We should consider highlighting that somehow in the DB Console (perhaps a yellow icon somewhere). As of #105005 we are aggregating these non-critical errors into the
errors.txt
file in the bundle, but perhaps we'd need to expose it to the console differently.Jira issue: CRDB-9067