We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are numerous tools that could do monitor, but I like the simplicity of tinystatus: https://github.com/harsxv/tinystatus
The script generates an html file that can be served by a web server of our choice - caddy.
checks.yaml could be generated by Puppet based on the cluster config (i.e.: terraform_data.yaml content).
checks.yaml
terraform_data.yaml
If the proxy is down, the status page won't be available publicly, but there is a json record file with the timestamp.
The json and html files could be forwarded out of the cluster to alleviate the proxy as a single point of failure for status display.
The text was updated successfully, but these errors were encountered:
cmd-ntrf
No branches or pull requests
There are numerous tools that could do monitor, but I like the simplicity of tinystatus:
https://github.com/harsxv/tinystatus
The script generates an html file that can be served by a web server of our choice - caddy.
checks.yaml
could be generated by Puppet based on the cluster config (i.e.:terraform_data.yaml
content).If the proxy is down, the status page won't be available publicly, but there is a json record file with the timestamp.
The json and html files could be forwarded out of the cluster to alleviate the proxy as a single point of failure for status display.
The text was updated successfully, but these errors were encountered: