Skip to content
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

storage: expand time-series metrics for visibility into deletions #69849

Open
2 of 4 tasks
jbowens opened this issue Sep 5, 2021 · 1 comment
Open
2 of 4 tasks

storage: expand time-series metrics for visibility into deletions #69849

jbowens opened this issue Sep 5, 2021 · 1 comment
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-storage Storage Team
Projects

Comments

@jbowens
Copy link
Collaborator

jbowens commented Sep 5, 2021

It can be difficult to tell if data that was logically dropped by range or point deletions has been physically dropped. Some ideas for new time-series metrics that can help here:

Jira issue: CRDB-9830

Epic CRDB-34247

@jbowens jbowens added C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-storage Storage Team labels Sep 5, 2021
@jbowens jbowens added this to Incoming in Storage via automation Sep 5, 2021
@mwang1026 mwang1026 moved this from Incoming to Backlog in Storage Jun 6, 2022
@nicktrav nicktrav moved this from Backlog to Observability in Storage Mar 21, 2023
@jbowens
Copy link
Collaborator Author

jbowens commented Jun 12, 2023

We could call the remaining items superseded by #102604. I'm not sure timeseries for the remaining two is much more valuable than the ability to aggregate those stats through the new crdb_internal func.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-storage Storage Team
Projects
Storage
  
Observability
Development

No branches or pull requests

1 participant