Skip to content

Proxy Origin Health Check #658

@ecv

Description

@ecv

High-Level Summary

Confronted with an unreachable proxy, users cannot currently tell if a proxy is unreachable due to an issue on our side or theirs.

Each proxy should healthcheck its origin every N minutes and throw a flag yea/nay, a red light in the portal, and a boolean attribute label on the resource.

Response codes other than the 500 class are passes, a 500 or a nonresponse is a fail.

Motivation

Let users discover whether Datum is to blame for a nonresponsive proxy.

Goals

Clarify for users whether origins are reachable by Datum proxies, whenever a user might suspect.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions