-
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
sqltelemetry: add CANCEL QUERIES and CANCEL SESSIONS telemetry #46778
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but should we wait for #46730 to be addressed first?
Reviewed 2 of 2 files at r1.
Reviewable status: complete! 0 of 0 LGTMs obtained (waiting on @RaduBerinde)
Yes, I think so. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 1 of 1 files at r2.
Reviewable status: complete! 1 of 0 LGTMs obtained (waiting on @RaduBerinde)
bors r=yuzefovich |
bors r=yuzefovich |
46778: sqltelemetry: add CANCEL QUERIES and CANCEL SESSIONS telemetry r=yuzefovich a=asubiotto Release note: None (internal telemetry change) Closes #45103 Not sure whether we want to distinguish between CANCEL QUERY vs QUERIES use and CANCEL SESSION vs SESSIONS use (or even how to). So just added one counter for each statement type which is probably good enough. Tested this manually but holding off on writing tests since I've heard some work will be done on #46730 Co-authored-by: Alfonso Subiotto Marques <alfonso@cockroachlabs.com>
Release note: None (internal telemetry change)
Forgot about this one, it seems like bors canceled both times. Rebased and trying again. bors r=yuzefovich |
Build succeeded |
Release note: None (internal telemetry change)
Closes #45103
Not sure whether we want to distinguish between CANCEL QUERY vs QUERIES use and CANCEL SESSION vs SESSIONS use (or even how to). So just added one counter for each statement type which is probably good enough.
Tested this manually but holding off on writing tests since I've heard some work will be done on #46730