Scheduling Health Checks

pg_health_framework deliberately does not schedule or trigger runs itself — that choice is left entirely to whatever fits your own environment: a cron job, an external orchestrator, or simply a person running psql by hand. Call the collection and evaluation engines (or the combined convenience call that does both in one step — see Using the Seed Catalog) from wherever makes sense for your setup.

Reading results back out afterwards works exactly the same way for any historical run, whether it was triggered by a schedule or run manually — there's nothing schedule-specific about the reporting functions described in How Threshold Evaluation Works.

If you'd like something to happen automatically the very moment a check's severity actually changes — rather than only finding out when someone goes and looks — that's what the optional events layer is for. See Events at a Glance next.

Continue to Events at a Glance.