Skip to content

Single Source of Truth on Health Checks #86

@rcastle1

Description

@rcastle1

What do you want to change?
Work out the best solution with @ezraboley @rdaruwala, but we should really have a single source of truth for the health check bounds. I would tend toward the embedded side, as things like telemetry like pressure can momentarily be out of bounds when transitioning into or out of a state and the embedded side is set up to handle that.

Why make that change?
There were a few times where health checks were updated on the dashboard, but not on the embedded side and vice versa. We worked through these issues quickly, but never the less, it was an issue and if they noticed, it would make our advisers less confident in us.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Feature RequestFurther information is requested

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions