Repair stale Pushgateway labels for a live Kestra batch job
Reconcile stale Pushgateway labels with Kestra execution history then rewrite the batch metrics behind approval.
Monitor any page for content changes using KV-persisted hashes and Slack alerts.
Competitor pricing pages, status pages of vendors, policy documents, a landing page before a launch — things you refresh manually today. This blueprint hashes the page on a schedule, persists the hash in the Kestra KV store, and only tells you when the hash actually moved.
load_previous_hash (io.kestra.plugin.core.kv.Get) reads the last hash, tolerating a missing key on first run.fetch_and_hash (io.kestra.plugin.scripts.python.Script) fetches the page, normalizes whitespace, and emits a SHA-256 via the ::{"outputs": ...}:: protocol.compare_hashes (io.kestra.plugin.core.flow.If) alerts via alert_change only when a stored hash exists and differs; otherwise log_unchanged.store_new_hash (io.kestra.plugin.core.kv.Set) persists the fresh hash — this is what makes the schedule stateful.errors block alerts Slack when the fetch fails.page_hash output for downstream comparison steps.A cron job that prints a hash goes nowhere. The flow adds state (KV), a branch (change vs not), an alert, failure reporting, and history — and the next step (snapshot diff, archive to S3, open a ticket) is one task away.
SLACK_WEBHOOK_URL: webhook for change and failure alerts.url and a unique kv_key per watched page.watch_schedule.