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.

Sign up for GitHub

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

Jump to bottom

Surface workload level create index recommendations in the console #81862

Open
kevin-v-ngo opened this issue May 25, 2022 · 1 comment
Open

Surface workload level create index recommendations in the console #81862

kevin-v-ngo opened this issue May 25, 2022 · 1 comment
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-observability
Projects
Cluster Observability

Comments

@kevin-v-ngo
Copy link

kevin-v-ngo commented May 25, 2022 •
edited

We should capture workload-level index recommendations and provide a UX in the console. Few experiences we should consider include:

  • When the index recommendation was created
  • The statements that would benefit from the index
  • The 'impact' of creating the index
  • Seamless application of the create index statements
  • Observability into workload behavior after the recommendation(s) was applied

Jira issue: CRDB-16327

Epic: CRDB-19396
@kevin-v-ngo kevin-v-ngo added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label May 25, 2022
@kevin-v-ngo kevin-v-ngo added this to Triage in Cluster Observability via automation May 25, 2022
@kevin-v-ngo kevin-v-ngo moved this from Triage to Backlog in Cluster Observability May 31, 2022
@mari-crl mari-crl added sync-me and removed sync-me labels Jun 2, 2022
@mgartner mgartner mentioned this issue May 10, 2023
Open
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 4, 2024

We have marked this issue as stale because it has been inactive for
18 months. If this issue is still relevant, removing the stale label
or adding a comment will keep it active. Otherwise, we'll close it in
10 days to keep the issue queue tidy. Thank you for your contribution
to CockroachDB!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-observability
Projects
No open projects
Cluster Observability
Backlog
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kevin-v-ngo @mari-crl