New to Kestra?
Use blueprints to kickstart your first workflows.
Audit LanceDB vector datasets for small file fragments, evaluate compaction thresholds, and alert MLOps via Slack in Kestra.
LanceDB is a serverless, columnar vector database engineered for AI and multimodal workflows. During continuous append or streaming vector ingestion, tables accumulate dozens of small fragment files. Over time, excessive fragments degrade scan speed, increase metadata overhead, and slow down vector similarity queries.
This blueprint implements an automated SRE and MLOps sentinel that continuously tracks LanceDB table fragment counts, compares them against configured operational thresholds, and alerts teams via Slack when compaction or index rebuilding is required.
inspect_lancedb_fragment_health): Analyzes the LanceDB dataset manifest, tracking fragment counts, total rows, and disk footprint.evaluate_compaction_guard): Compares active fragments against inputs.max_fragment_threshold.log_telemetry_metrics): Emits structured shell metrics logs for upstream observability collectors.errors): Captures storage access errors and posts execution details to Slack.{{ secret('SLACK_WEBHOOK_URL') }}.SLACK_WEBHOOK_URL.SLACK_WEBHOOK_URL: Your Slack incoming webhook URL.SLACK_WEBHOOK_URL secret in your Kestra namespace.inputs.dataset_uri to your target LanceDB directory.then: branch that calls table.compact_files() directly upon breach.