DumbMonit
用 DumbMonit 监控 authentik
测试版Readiness, workers, failed system tasks, outpost connections, version updates, users.
产品说明为英文，与产品内一致。页面标签使用您的语言。
DumbMonit 监控的内容
Whether authentik can still sign people in and keep its background work running: readiness, workers, failed system tasks, outposts that stopped reporting, version updates and the number of users.
典型用途. Identity: readiness, workers, failed tasks, outposts, updates
示例
- authentik 2025.x
连接方式
您需要准备
- API tokenThe key of an API token created for a service account, sent as "Authorization: Bearer …".
需要开放的网络端口
9000/TCPAPI (HTTP, default)9443/TCPOnly with the https scheme on authentik's own HTTPS port443/TCPOnly with the https scheme behind a reverse proxy
设置步骤: Create an API token in authentik
In authentik, open Directory → Users → Create a service account and name it as follows, without a random password.
dumbmonitPut that user in a group that can open the authentik interface, so it can read the system pages.
Open Directory → Tokens and App passwords, create a token for that user with the intent API Token and no expiry, and copy its key.
In DumbMonit, enter authentik's address and paste the key.
注意. authentik has no read-only role for its system pages: the token's user must be allowed into the interface, so keep the key only in DumbMonit. Pages the token cannot read are skipped, not failed.