Schedule icon
Request icon
Script icon
Process icon
Log icon
Switch icon
SlackIncomingWebhook icon
Fail icon

Apache Doris Tablet Health and Backend Node Sentinel

Audit Apache Doris MPP data warehouse tablet health and offline backends via Prometheus metrics, classify severity, and trigger Slack alerts on tablet errors.

Categories
Data

Automated real-time analytical warehouse sentinel that interrogates Apache Doris Frontend Prometheus metrics on a recurring schedule to audit tablet replication health, detect offline Backend (BE) storage nodes, classify cluster degradation severity, and dispatch Slack incident alerts before real-time ingestion pipelines stall.

How it works

  1. A schedule trigger activates every fifteen minutes to audit the Apache Doris Frontend instance.
  2. An HTTP request task queries the Frontend's /metrics Prometheus endpoint to harvest real-time tablet replication counters and storage backend statuses.
  3. An embedded Python script parses metric lines, extracting doris_fe_tablet_unhealthy_count, doris_fe_backends_down_count, and active client connection volume.
  4. An informational log task records evaluated warehouse metrics and current cluster status classification.
  5. A Switch flow control task branches execution according to the evaluated status:
    • CLUSTER_OPTIMAL: Confirms all partition tablets are healthy and logs nominal storage telemetry.
    • BACKEND_STRESS_WARNING: Emits a non-blocking advisory notification when minor tablet re-balancing occurs within allowable thresholds.
    • CRITICAL_TABLET_CORRUPTION: Dispatches a detailed Slack incident webhook with unhealthy tablet tallies, offline backend counts, execution deep links, and halts execution via a failure gate.
  6. An immutable final audit log records the comprehensive health verdict and cluster metrics in Kestra execution history.

What you get

  • Real-time data warehouse safeguards catching under-replicated tablets before analytical query performance degrades.
  • Automated detection of crashed or unreachable Doris Backend (BE) worker daemons.
  • Immediate Slack notifications alerting data engineering and DBA teams with exact offline node metrics.
  • Automated execution failure gates that halt dependent ELT and dbt transformation flows when storage backends degrade.
  • Complete, immutable audit records tracking analytical storage cluster health across batch windows.

Who it's for

  • Data Platform Engineers and Database Administrators (DBAs) maintaining Apache Doris clusters.
  • Analytics Engineers relying on real-time Doris data ingestion for business intelligence and reporting.
  • Site Reliability Engineers (SREs) managing high-throughput analytical lakehouse infrastructure.

Why orchestrate this with Kestra

  • Declarative YAML orchestrates metrics harvesting, text parsing, and incident dispatching without dedicated sidecar agents.
  • Native secret masking ensures Slack webhook URLs and administrative credentials remain confidential during automated runs.
  • Built-in conditional branching enables granular escalation policies tailored to tablet replication thresholds.
  • Centralized execution timelines provide instant diagnostic visibility into historical data warehouse failure patterns.

Prerequisites

  • Running Apache Doris cluster (Frontend and Backend nodes) with the Prometheus metrics endpoint enabled (default port 8030).
  • Network reachability between Kestra and the Doris Frontend HTTP interface.

Secrets

  • SLACK_WEBHOOK_URL: Slack Incoming Webhook URL used to transmit critical data warehouse incident alerts.

Quick start

  1. Configure the SLACK_WEBHOOK_URL secret in your Kestra namespace or environment variables.
  2. Import this blueprint into your Kestra instance under company.data.
  3. Run a manual test execution pointing to your Doris Frontend endpoint to verify metric connectivity and parsing.
  4. Enable the doris_audit_schedule trigger to maintain continuous 15-minute cluster monitoring.

How to extend

  • Add an automated tablet repair trigger via Doris MySQL interface (ADMIN REPAIR TABLE) in the remediation branch.
  • Correlate unhealthy tablet counts with underlying Backend disk utilization metrics (doris_be_disk_state).
  • Route separate alerts to PagerDuty or Opsgenie when offline Backend nodes threaten cluster data durability.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.