Health and warnings

Edition: Community and Enterprise Offering: Self-managed

"Admin" > "System health" shows every sealfix process, the configuration version it runs, and the warnings of the applied configuration.

Processes

Column	Shows
Process	api, executor, notifier, gitsync, siem
Status	Running, not seen recently, or restart needed
Configuration	The version it started with. A process on an older version needs a restart

Warnings

Some choices belong to your infrastructure, not to sealfix: how your directory is reached, how the databases are connected. sealfix never refuses them. It shows one warning on System health for as long as the choice stands, with the setting, its effect and the remedy.

Example

The directory is reached over plain ldap:// without StartTLS (ldap.allow_plaintext): passwords cross the network unprotected. Use ldaps://, or ldap:// with StartTLS, and turn the setting off.

The rules of sealfix itself are different: a requester approving their own fix, a value written into SQL, a row count that differs from the dry run. Those are always refused.

Probes

Endpoint	For	Answers
/healthz	Liveness	pass while the process serves; fail (503) only while it shuts down. It never asks the database
/readyz	Readiness, your proxy	200 when the metadata store answers, the executor's public key is loaded and the executor was seen in the last 3 minutes; 503 otherwise

Only clients in health.readyz_networks see the state of each component; everyone else sees the overall status alone.