Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Health Check Service #57

Open
bbengfort opened this issue Jun 25, 2021 · 0 comments
Open

Health Check Service #57

bbengfort opened this issue Jun 25, 2021 · 0 comments
Labels
enhancement New feature or request

Comments

@bbengfort
Copy link
Collaborator

Implement a health check service that routinely loops through verified VASPs and performs a health check if the VASP implements the TRISAHealth Service. Note that mTLS may be required to connect to the status endpoint and also note that the status endpoint is optional, so expect or handle Unavailable or NotImplemented codes.

When sending health checks, the directory service should be polite, and notify the node the number of failed attempts prior to this check and the last time the check occurred. The node may return rate limiting/accelerating information using not before and not after, which the directory service should also respect.

The health check service should store the last known service state with the VASP and any health check metadata (e.g. next time to check, number of attempts in the GDSExtra protocol buffer).

No historical or timeseries data is required, in the future, this information will be posted to Prometheus.

@bbengfort bbengfort added the enhancement New feature or request label Jun 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant