Reload Configuration and Verify It Applied
A 5-step recipe with Prometheus. We can help you get access.
Recipe · 5 steps
Reload Configuration and Verify It Applied
with Prometheus
Reload the configuration and confirm it took effect.
- Read the currently loaded configuration so there is a before image to compare against, and a record of what to restore if the reload goes wrong.
- Trigger the reload of the configuration file and all rule files. A 500 here means the new configuration failed to parse and the server has kept running on the old one.
- Read the runtime info and check reloadConfigSuccess. This is the field that separates a reload the server accepted from one it actually adopted, and lastConfigTime dates the adoption.
- Re-read the loaded configuration and confirm the running server is serving the new content rather than the before image.
- List the rule groups now loaded. A reload can succeed on the main configuration while a referenced rule file quietly contributes nothing, so confirming the expected groups are present closes the loop.
What you'll need to have ready
- ruleType: Optional rule type filter for the post-reload rule listing — alert or record. Omit to list both.
For your developer
Arazzo workflow prometheus:reload-config-verify, 5 operations: getConfig → reloadConfig → getRuntimeInfo → getConfig → getRules. Specs on APIs.io.