docs: add section on conf. monitoring with Gatus (status.hamburg.ccc.de)
This commit is contained in:
parent
1523b15952
commit
c6c0272448
1 changed files with 13 additions and 0 deletions
|
|
@ -97,3 +97,16 @@ ansible-playbook playbooks/deploy.yaml --inventory inventories/chaosknoten/hosts
|
||||||
Do not forget to commit your changes, whether it's a new host or you are making changes to an existing host.
|
Do not forget to commit your changes, whether it's a new host or you are making changes to an existing host.
|
||||||
|
|
||||||
And always `git pull` before you run Ansible so avoid reverting anything!
|
And always `git pull` before you run Ansible so avoid reverting anything!
|
||||||
|
|
||||||
|
# Monitoring
|
||||||
|
|
||||||
|
## Gatus (`status.hamburg.ccc.de`)
|
||||||
|
|
||||||
|
After you configured a new service or website, add it to our status and uptime monitoring.
|
||||||
|
Take a look at the configuration in `resources/external/status/docker_compose/config` and extend it to cover the newly added service or website. The configuration should probably happen in either `services-chaosknoten.yaml` or `websites.yaml`. Taking the existing configuration as a reference should give guidance on how to configure new checks. Additionally there's also the comprehensive [Gatus Documentation](https://github.com/TwiN/gatus?tab=readme-ov-file#table-of-contents).
|
||||||
|
|
||||||
|
After you've added some checks, the configuration can be deployed using:
|
||||||
|
|
||||||
|
```sh
|
||||||
|
ansible-playbook playbooks/deploy.yaml --inventory inventories/external --limit status
|
||||||
|
```
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue