Exchange HTTPS load balancer backend checks
137-exchange-backend-https.yaml
HTTP(S)
What this example does
Exchange infrastructure monitoring: Exchange HTTPS load balancer backend checks. It helps operators check the availability of this client-access or mail-routing dependency.
Checks and behavior
- Sends an GET request to https://mail.example.com/owa/.
- Checks allowed/denied HTTP status codes.
- TLS settings cover certificate trust, certificate expiry.
- Runs against explicitly configured backends.
- Formats results for nagios output.
Adapt example domains, addresses, credentials and thresholds to your environment before use. HTTP availability does not confirm an authenticated Exchange workflow.
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.
# Exchange example: replace placeholder domains/IPs and adapt expected HTTP statuses to your deployment.
# HTTP status alone does NOT prove successful Exchange authentication or mailbox functionality.
name: Exchange HTTPS load balancer backend checks
url: https://mail.example.com/owa/
timeouts:
connect: 4
response: 12
request:
method: GET
follow_redirects: false
tls:
verify: true
min_valid_days: 21
execution:
backends:
- name: exchange-node-a
resolve:
mail.example.com: 192.0.2.10
- name: exchange-node-b
resolve:
mail.example.com: 192.0.2.11
tests:
status:
allow:
- 200
- 302
- 401
- 403
monitoring:
service_name: Exchange HTTPS load balancer backend checks
output: nagios
on_failure: critical