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
Currently, Coder generates healthcheck warnings to notify users of potential issues. However, there are instances where these warnings are triggered by false alarms or where admins need the flexibility to temporarily acknowledge a failure without initiating a full resolution process.
To address this, I propose the implementation of an API that allows admins to temporarily disable and enable specific healthcheck warnings. This feature would provide users with the ability to manage false alarms or acknowledge failures on a temporary basis without affecting the overall health monitoring system.
The text was updated successfully, but these errors were encountered:
I reviewed possible solutions, and it seems that the best option would be using site_configs to store information about dismissed_healthchecks. API would look similar to /api/v2/appearance.
Currently, Coder generates healthcheck warnings to notify users of potential issues. However, there are instances where these warnings are triggered by false alarms or where admins need the flexibility to temporarily acknowledge a failure without initiating a full resolution process.
To address this, I propose the implementation of an API that allows admins to temporarily disable and enable specific healthcheck warnings. This feature would provide users with the ability to manage false alarms or acknowledge failures on a temporary basis without affecting the overall health monitoring system.
The text was updated successfully, but these errors were encountered: