HTTPS via explicit proxy and private CA
118-https-explicit-proxy-private-ca.yaml
HTTP(S)
What this example does
Enterprise network connectivity: HTTPS via explicit proxy and private CA. Use it when probes must respect an approved HTTP(S) proxy.
Checks and behavior
- Sends an GET request to https://service.internal.example/health.
- Checks allowed/denied HTTP status codes.
- TLS settings cover certificate trust, private CA bundle.
- Uses explicit proxy configuration.
- Formats results for icinga2 output.
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.
# export PROBE_HTTPS_PROXY=http://proxy.internal.example:3128
# export PROBE_CA_BUNDLE=/etc/ipsonic-probe/private-roots.pem
# The CA file contains trusted PEM root/intermediate CA certificates.
name: HTTPS via explicit proxy and private CA
url: https://service.internal.example/health
proxy:
mode: explicit
https_env: PROBE_HTTPS_PROXY
tls:
verify: true
ca_file_env: PROBE_CA_BUNDLE
timeouts:
connect: 5
response: 15
tests:
status:
allow: [200]
monitoring:
service_name: Private CA service via proxy
output: icinga2
on_failure: critical