Skip to content

☂️ Coder deployment health check #8971

Closed

Activity

  1. changed the title [-]☂️: Coder deployment health[/-] [+]☂️ Coder deployment health[/+] on Aug 10, 2023
  2. bpmct commented on Sep 6, 2023

    @bpmct
    Member

    added #9558

  3. added this to the healthcheck GA milestone on Sep 19, 2023
  4. changed the title [-]☂️ Coder deployment health[/-] [+]☂️ Coder deployment health check[/+] on Sep 29, 2023
  5. self-assigned this
    on Nov 10, 2023
  6. mtojek commented on Nov 10, 2023

    @mtojek
    Member

    I'm starting with #9470. Let's see how far I can go.

  7. mtojek commented on Nov 14, 2023

    @mtojek
    Member

    I prepared a draft navigating through the design & implemention details: notion page. Let's consider it to be kick off.

  8. BrunoQuaresma commented on Nov 16, 2023

    @BrunoQuaresma
    Contributor

    Should we add a task for the page redesign including all those changes in the API?

  9. mtojek commented on Nov 16, 2023

    @mtojek
    Member

    Replied in slack, let me copy it here:

    Actually we can do the same way as we did last time, so somebody (me?) will finish the backend side, and then reassign issues to you

  10. matifali commented on Nov 16, 2023

    @matifali
    ContributorAuthor

    @BrunoQuaresma yes you may create a new issue for design and add to the list and milestone.

  11. bpmct commented on Dec 3, 2023

    @bpmct
    Member

    👋🏼 Catching up now with these health check enhancements. This is awesome!

    I noticed the health check does not show up in the bottom bar anymore. Is this just because dev.coder.com is currently healthy?

    If not, are there plans to add it back again? I like that it can be discovered outside of the Deployment > Health when there errors so that an admin can identify and self-resolve without knowing the page exists or contacting support.

  12. BrunoQuaresma commented on Dec 4, 2023

    @BrunoQuaresma
    Contributor

    Yes, the warning is only displayed when it is unhealthy but we definitely need to improve its discoverability

  13. mtojek commented on Dec 4, 2023

    @mtojek
    Member

    @BrunoQuaresma Do you have spare time to implement the FE changes this week? I guess we all agreed on the design.

  14. BrunoQuaresma commented on Dec 4, 2023

    @BrunoQuaresma
    Contributor

    @mtojek sure thing. I was planning to take a look into the flakes but I'm going to prioritize the new health UI this week

  15. matifali commented on Jan 12, 2024

    @matifali
    ContributorAuthor

    One last thing. Don't we also want to add a YAML page to each health check to allow the operator to copy raw health check response? Similar to previous behavior.
    cc: @johnstcn @mtojek @BrunoQuaresma

  16. johnstcn commented on Jan 12, 2024

    @johnstcn
    Member

    We could add a link to the API endpoint very cheaply?

  17. mtojek commented on Jan 12, 2024

    @mtojek
    Member

    @matifali Could you please a separate issue or post-GA epic? We have merged the healthcheck changes, so it is a bit late.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions