new-site/monitoring/blackbox.yml
justin b190bcef92 Fix ERPNext and Forgejo probes
- ERPNext: custom blackbox module with Host: performancewest.net header
  (ERPNext multitenancy requires site name in Host for routing)
- Forgejo: add extra_hosts to blackbox-exporter so it can resolve
  host.docker.internal to reach forgejo on port 3000
- Blackbox http_erpnext module: sets Host header, expects 200

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-05-01 03:35:45 -05:00

36 lines
923 B
YAML

modules:
http_2xx:
prober: http
timeout: 10s
http:
valid_http_versions: ["HTTP/1.1", "HTTP/2.0"]
valid_status_codes: [200, 301, 302]
follow_redirects: true
preferred_ip_protocol: ip4
tls_config:
insecure_skip_verify: false
# Permissive module for internal services (Python SimpleHTTPServer, etc.)
http_internal:
prober: http
timeout: 10s
http:
valid_http_versions: ["HTTP/1.0", "HTTP/1.1", "HTTP/2.0"]
valid_status_codes: [200, 301, 302, 401, 403]
follow_redirects: false
preferred_ip_protocol: ip4
# ERPNext requires Host header matching the site name
http_erpnext:
prober: http
timeout: 10s
http:
valid_http_versions: ["HTTP/1.1", "HTTP/2.0"]
valid_status_codes: [200]
headers:
Host: performancewest.net
preferred_ip_protocol: ip4
tcp_connect:
prober: tcp
timeout: 5s