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

[CMSP-273] Add additional insights for database performance #138

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

kyletaylored
Copy link
Contributor

In an effort to start tracking database performance within the dashboard, this adds two additional tables to the Database output section of the status report:

  1. Overview of tables sizes with row counts
  2. Overview of index on tables with selectivity and index length

This data can serve well for customers who understand a bit about database performance, and can also provide both a customer or CSE a snapshot of the overall database state just by fetching a few pieces of information. I've added some explainer notes as well for what the index columns mean, but doing some research, the index performance is a bit subjective, so I've only added rough guidelines.

I've also added a new template for lists, and added an optional parameter to the table template for adding scrollable tables when the output is very long.

image

@kyletaylored kyletaylored requested a review from a team as a code owner March 10, 2023 16:06
@jazzsequence jazzsequence changed the title Add experimental database performance tables [CMSP-273] Add experimental database performance tables Mar 13, 2023
@jazzsequence
Copy link
Contributor

Tracking as CMSP-273

@scottbuscemi Product decision?

@scottbuscemi scottbuscemi changed the title [CMSP-273] Add experimental database performance tables [CMSP-273] Add additional insights for database performance Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants