Identity Service Health Monitoring
Identity Service Health Monitoring is a feature used as part of Identity Continuity and is available for OIDC, SAML, and LDAP identity services. When enabled, this feature allows the orchestrator to continuously poll the identity service and trigger an alert if it can't be reached. In addition, you can create a manual failover mechanism for break-glass scenarios with the custom health check endpoint capability.
You will need to configure Identity Service Health Monitoring for each identity service used in your continuity strategy.
When this feature is enabled, the following fields can be configured:
| Name | Description | Example |
|---|---|---|
| Polling Frequency | The interval between each health check of the identity service. Can be set in seconds, minutes, or hours. | 30s |
| Timeout | The maximum wait time for a response. Can be set in seconds, minutes, or hours. | 5s |
| Failover Threshold | The number of consecutive negative (down) health check results to trigger a failover. | 4 |
| Fallback Threshold | The number of consecutive positive (up) health check results to trigger a fallback. | 4 |
| Custom Health Check | Enabling this allows you to override the behavior of monitoring IDP availability. This can be used use custom signals for IDP health or for a break-glass scenario to manually trigger failover and fallback behaviors. | |
| Custom Health Check Endpoint | The endpoint to use for the custom health check. The value must be a fully qualified URL. | https://example.com/health |
| Expected Status Codes | (Optional) The HTTP status codes that the custom health check returns to be considered healthy. | 200, 201 |
| Response Body Matcher | (Optional) A matcher that verifies the expected value in the response body of a health check. | '"status": "up"' |