Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions content/configuration/healthcheck.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
title: Health Check
description: Configuration for the server health check service.
---

:partial{content="config-env-vars"}

The health check service powers the `/server/health` endpoint, which reports the status of connected services like the database, edis, storage, and email. Results are cached and shared across requests to avoid excessive checks.

| Variable | Description | Default Value |
| ----------------------- | ----------------------------------------------------------------------------------------------------- | ------------------------------ |
| `HEALTHCHECK_ENABLED` | Whether or not to enable the `/server/health` endpoint. | `true` |
| `HEALTHCHECK_NAMESPACE` | Namespace used for health check cache keys to prevent conflicts with other cached data. | `directus:healthcheck` |
| `HEALTHCHECK_SERVICES` | Comma-separated list of services to check. Supported values: `database`, `redis`, `storage`, `email`. | `database,redis,storage,email` |
| `HEALTHCHECK_CACHE_TTL` | How long the cached health check result is valid before services are re-checked. | `5m` |

Individual services also support their own health check threshold configuration. See [Database](/configuration/database), [Cache](/configuration/cache), [Files](/configuration/files), and [Security & Limits](/configuration/security-limits) for `*_HEALTHCHECK_THRESHOLD` variables.