Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Couple suggestions for the coder deployment issues banner #9692

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

Closed
smolinari opened this issue Sep 15, 2023 · 4 comments · Fixed by #10193
Closed

Couple suggestions for the coder deployment issues banner #9692

smolinari opened this issue Sep 15, 2023 · 4 comments · Fixed by #10193
Assignees
Labels
site Area: frontend dashboard

Comments

@smolinari
Copy link

smolinari commented Sep 15, 2023

Hi,

image

I have my k8s cluster in an el-cheapo VPS setup and sometimes it isn't the "smoothest" experience. It's all just POC stuff mainly anyway, so because of the low performance, I get the "coder deployment issues" banner here and there and it is...well..... annoying. I get the banner mainly due to the database connection latency, I think. I don't know, because I am given no information as to why there is a test failure and according to the image above, latency isn't all that bad.

Here are my suggestions.

  1. Make the banner dismissable (or do it differently altogether - see point 4).

  2. Offer a button to be able to retest the condition.

  3. Offer better feedback as to why the failure is noted. "healthy": false, says nothing to the condition needing rectification for the database, which again, is the issue I run into most.

  4. Offer a less "in your face" error warning. Like maybe a red dot with a white exclamation mark icon on the user's avatar and when clicking on the avatar, have a menu item leading to the health issue or the health page. Or put the exclamation icon on the "Deployment" tab and on the "Health" menu item under "Deployment". That will lead the admin (hopefully the admin only sees this) to the issue report.

That's all. Thanks for considering these suggestions in advance.

Scott

@cdr-bot cdr-bot bot added the feature label Sep 15, 2023
@matifali
Copy link
Member

matifali commented Sep 15, 2023

@smolinari This is marked as healthy when latency is less than 15 ms. I agree that it should be reflected and marked as a warning.
We have this on our roadmap. See #8971, #8970, and #9381

@matifali
Copy link
Member

@aslilac I would appreciate your thoughts in the context of #8971 for improving the UX.

@aslilac
Copy link
Member

aslilac commented Sep 15, 2023

My test license expires in like 20 days, so I've had a similarly frustrating banner while working, and am definitely interested in seeing improvements here :p

I like the idea of having it just be a little badge on something that you can expand into a more lengthy explanation of what is happening. Also that it should really only be shown to admins/people who we expect can actually take action on whatever the issue is.

@matifali
Copy link
Member

Railway.app does not support derp, and the Coder's health check keeps showing a constant red banner that something is wrong.

@matifali matifali added the site Area: frontend dashboard label Sep 17, 2023
@aslilac aslilac self-assigned this Sep 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
site Area: frontend dashboard
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants