Github/authentik
1
0
Fork 0
mirror of https://github.com/goauthentik/authentik.git synced 2026-08-30 18:51:39 -07:00
Code Issues Packages Projects Releases Wiki Activity

website/docs: correct worker healthcheck claim and outpost list

Browse Source 
`ak healthcheck` requests /-/health/live/, which confirms the worker
processes are alive but does not touch the database, so the claim that it
verifies a PostgreSQL connection was wrong.

The /-/health/ready/ sentence was correct and is restored, now naming the
port it is served on. That endpoint runs its own SELECT 1 in the worker's
Rust health router and is bound to listen.http in worker mode.

Also lists all four outpost types instead of two; the LDAP, RADIUS, and
RAC outposts share the same ping handler, and the Rust proxy registers it
too.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Dominic Roy
2026-08-13 11:23:28 -04:00
parent 81cb6a90f2
commit c12e247474
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
website/docs/sys-mgmt/ops/monitoring.md
View File

@@ -10,13 +10,13 @@ Configure your monitoring software to send requests to `/-/health/live/`, which
## Worker monitoring
The worker container can be monitored by running `ak healthcheck` in the worker container. This will check that the worker is running and ensure that a PostgreSQL connection can be established correctly.
The worker container can be monitored by running `ak healthcheck` in the worker container. This checks that the worker process is running and responding.
You can also send HTTP requests to `/-/health/ready/`, which will return `HTTP 200` if a PostgreSQL connection can be established correctly.
You can also send HTTP requests to `/-/health/ready/`, which will return `HTTP 200` if the worker processes are responding and a PostgreSQL connection can be established correctly. The worker serves this on the port set by [`AUTHENTIK_LISTEN__HTTP`](../../install-config/configuration/configuration.mdx#authentik_listen__http).
## Outpost monitoring
Both kinds of outpost (proxy and LDAP) listen on a separate port (9300) and can be monitored by sending HTTP requests to `/outpost.goauthentik.io/ping`.
All outposts (proxy, LDAP, RADIUS, and RAC) listen on a separate port (9300) and can be monitored by sending HTTP requests to `/outpost.goauthentik.io/ping`.
---