Preproduction combined checks
36-combined-preprod.yaml
HTTP(S)
What this example does
This example demonstrates preproduction combined checks.
Checks and behavior
- Sends an GET request to https://api.example.com/health.
- Checks allowed/denied HTTP status codes.
- Validates required, forbidden or matching HTTP headers.
- Looks for expected response content and/or rejects known error markers.
- Inspects structured JSON response values.
- TLS settings cover certificate trust, certificate expiry.
Adapt example domains, addresses, credentials and thresholds to your environment before use.
YAML configuration
# 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: Preproduction combined checks
url: https://api.example.com/health
connection:
resolve:
api.example.com: 10.20.30.40
request:
method: GET
user_agent: httptest/2.0
follow_redirects: false
timeouts:
connect: 3
response: 8
tls:
verify: true
min_valid_days: 30
tests:
status:
allow:
- 200
headers:
exists:
- Content-Type
not_contains:
Server:
- Apache/2.2
body:
not_contains:
- traceback
- exception
response:
min_bytes: 5
max_bytes: 200000
content_type: application/json
json:
paths:
- path: status
equals: healthy
security:
hsts_min_age: 31536000