You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
Make the banner dismissable (or do it differently altogether - see point 4).
Offer a button to be able to retest the condition.
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.
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
The text was updated successfully, but these errors were encountered:
@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
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.
Hi,
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.
Make the banner dismissable (or do it differently altogether - see point 4).
Offer a button to be able to retest the condition.
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.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
The text was updated successfully, but these errors were encountered: