Clear Pulsar backlogs held by subscriptions nobody consumes
Detect Apache Pulsar subscriptions with no consumers that still pin a large backlog, then clear or remove them behind a dry run, an approval pause and a live re-read that fails the run.
Monitor Pyrra SLO compliance, track error budget burn rates, detect service level degradation, and dispatch automated Slack incident alerts with Kestra.
Continuously monitors Pyrra Service Level Objective (SLO) tracking services, inspects multi-window error budget burn rates for critical tier-1 microservices, and dispatches actionable Slack incident notifications upon error budget exhaustion or API degradation.
Schedule trigger initiates the sentinel audit workflow every hour (disabled by default for on-demand configuration).probe_pyrra_readiness task executes a GET request against Pyrra's /readyz endpoint to confirm controller readiness and Prometheus connectivity.probe_active_objectives task queries /api/v1/objectives to verify active SLO CRD synchronization and objective definitions.probe_service_slo_status task calls /api/v1/objectives/status to evaluate real-time multi-window error budget burn rates and availability status for target microservices.evaluate_slo_compliance task uses Pebble conditionals inside a Switch task to categorize outcomes into COMPLIANT, ENGINE_UNHEALTHY, OBJECTIVES_UNAVAILABLE, or SLO_STATUS_ERROR.io.kestra.plugin.slack.notifications.SlackIncomingWebhook with diagnostic status codes, and an audit trail is recorded in Kestra's execution history.{{ secret(...) }} without plaintext exposure.Switch tasks.SLACK_WEBHOOK_URL: Slack Incoming Webhook URL used for dispatching reliability alerts and incident notifications.SLACK_WEBHOOK_URL secret in your target Kestra namespace settings.company.sre).pyrra_api_endpoint and target_service_name.scheduled_sentinel_audit trigger to establish recurrent automated SLO surveillance.Loop task to evaluate error budgets across all frontend, payment, and inventory services in a single workflow.ENGINE_UNHEALTHY events directly to PagerDuty or Opsgenie on-call escalation schedules.