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

dbconsole: low-relevance license status is distracting and unhelpful #122626

Open
dt opened this issue Apr 18, 2024 · 0 comments
Open

dbconsole: low-relevance license status is distracting and unhelpful #122626

dt opened this issue Apr 18, 2024 · 0 comments
Assignees
Labels
A-cluster-observability Related to cluster observability A-webui Triage label for DB Console (fka admin UI) issues. Add this if nothing else is clear. C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. O-testcluster Issues found or occurred on a test cluster, i.e. a long-running internal cluster P-3 Issues/test failures with no fix SLA T-observability

Comments

@dt
Copy link
Member

dt commented Apr 18, 2024

Recently every page on the DB console started displaying this license status alert in the header, pictured here:
Screenshot 2024-04-18 at 10 02 20 AM

This is shown even when the license status is not concerning, requiring attention or actionable by the user of the console.

The treatment of it is also very prominent: on the top of every single page, underlined, bolded and with a colorful alert icon next to it, actively drawing attention to it. If it were indicating a problem such as an expiring or expired license -- potentially explaining whatever issue the DB console is actually being used to debug -- such prominence and active claiming of attention would make sense. But when the license is not concerning -- not expired nor expiring imminently -- this treatment doesn't seem aligned with the actual important and relevance to whatever task the DB console is being used for at the moment.

Could we not show this here when the license state is not a cause for concern, and instead show it only on advanced debug (where the license type was previously / still shown)?

Jira issue: CRDB-38014

Epic CRDB-32130

@dt dt added C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. A-webui Triage label for DB Console (fka admin UI) issues. Add this if nothing else is clear. A-cluster-observability Related to cluster observability T-cluster-observability labels Apr 18, 2024
@dt dt added this to To do in DB Server & Security via automation Apr 18, 2024
@blathers-crl blathers-crl bot added the T-server-and-security DB Server & Security label Apr 18, 2024
@dt dt added O-testcluster Issues found or occurred on a test cluster, i.e. a long-running internal cluster T-observability labels Apr 18, 2024
@exalate-issue-sync exalate-issue-sync bot removed the T-server-and-security DB Server & Security label Apr 18, 2024
@ajstorm ajstorm added the P-3 Issues/test failures with no fix SLA label Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-cluster-observability Related to cluster observability A-webui Triage label for DB Console (fka admin UI) issues. Add this if nothing else is clear. C-bug Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior. O-testcluster Issues found or occurred on a test cluster, i.e. a long-running internal cluster P-3 Issues/test failures with no fix SLA T-observability
Projects
Development

No branches or pull requests

4 participants