// IPSonic MONITORING TOOLKIT / DOCUMENTATION
ipsonic-probe rainbow unicorn

ipsonic-probe ✦

YAML-driven infrastructure validation. Platform-agnostic checks. Zero cloud dependencies.

DNSTCPHTTP / TLSYAML CONFIGCLI FIRSTKISSOFFLINE READY

Part of the ipsonic project ↗ Visit the main website

Validate multiple backends

68-http-backends.yaml

HTTP(S)

What this example does

Multi-node infrastructure verification: Validate multiple backends. This can reveal differences between individual service backends.

Checks and behavior

  • Sends an GET request to https://api.example.com/health.
  • Checks allowed/denied HTTP status codes.
  • Runs against explicitly configured backends.
  • Retries failures to reduce transient false alarms.
  • Formats results for nagios output.

Adapt example domains, addresses, credentials and thresholds to your environment before use.

YAML configuration

Download original YAML

# Copyright (c) 2026 mati peterson. Maintainer: mati peterson <ipsonic@mailbox.org>. Project: https://ipsonic.com/probe/. Disclaimer: Provided AS IS, without warranty of any kind. Use at your own risk; validate checks and configurations before production use.
name: Validate multiple backends
url: https://api.example.com/health
request:
  method: GET
execution:
  retries: 1
  retry_delay: 1
  success_required: 1
  backends:
    - name: backend-a
      resolve: {api.example.com: 192.0.2.10}
    - name: backend-b
      resolve: {api.example.com: 192.0.2.11}
tests:
  status:
    allow: [200]
monitoring:
  output: nagios
  assertions:
    - id: http.status
      severity: critical