29 lines
1.2 KiB
YAML
29 lines
1.2 KiB
YAML
|
---
|
||
|
|
# One invocation writes ONE file into Gatus's endpoints directory. Gatus merges
|
||
|
|
# every *.yaml under GATUS_CONFIG_PATH and appends lists, so each caller owns
|
||
|
|
# its own file and they compose without coordinating - the same shape as
|
||
|
|
# caddy_site, where each service contributes its own vhost.
|
||
|
|
|
||
|
|
# Filename stem: <name>.yaml
|
||
|
|
gatus_endpoint_name: ""
|
||
|
|
|
||
|
|
# PULLED endpoints - Gatus makes the request and evaluates conditions.
|
||
|
|
# - {name, group, url, interval, conditions: [...], alerts: [...]}
|
||
|
|
gatus_endpoint_pulled: []
|
||
|
|
|
||
|
|
# EXTERNAL endpoints - the host pushes its own result. Gatus never reaches out,
|
||
|
|
# which is what makes this work for machines behind NAT and for state that has
|
||
|
|
# no pollable surface at all (disk usage, ZFS health, UPS mains).
|
||
|
|
#
|
||
|
|
# - {name, group, token, heartbeat, alerts: [...]}
|
||
|
|
#
|
||
|
|
# `heartbeat` is the important one: if nothing reports within that window Gatus
|
||
|
|
# alerts. That is what makes a push check detect its own failure - a dead timer
|
||
|
|
# looks exactly like a dead host, which is the correct reading.
|
||
|
|
gatus_endpoint_external: []
|
||
|
|
|
||
|
|
# Where the files live. Matches roles/gatus.
|
||
|
|
gatus_config_dir: /opt/gatus/config
|
||
|
|
gatus_endpoints_dir: "{{ gatus_config_dir }}/endpoints"
|
||
|
|
gatus_gid: 10001
|