hydrolix

Bulk-delete ephemeral test projects on a Hydrolix cluster (default pattern `bundle_verification_*`, produced by the Rust validator's `--guid` flag). Lists matching projects, confirms with the user, then deletes sequentially. Use when the user wants to clean up leftover GUID test projects, or projects matching a name prefix, on a cluster.

Ingest N rows of realistic test data into any Hydrolix table. Automatically finds the transform's sample_data from bundle files, sets timestamps distributed across a given date range, and handles all authentication variants (JWT-only or JWT + table ingest token). Use whenever the user wants to populate a table with test data, seed data for dashboard testing, ingest sample events, or run ingestion tests on any cluster. Trigger on phrases like "ingestar datos de prueba", "ingest sample data", "populate table", "seed the table", "datos de testing", "quiero datos en la tabla", "ingestar en la tabla".

Validate Hydrolix transforms for a project before pushing to the cluster. Runs local schema validation (catches invalid datatype names like "float" that only fail at push time) and API validation (catches SQL errors and sample_data ingestion issues). Use before any hdx push, or standalone when the user wants to check transforms, verify datatype correctness, or pre-flight a deployment. Trigger on phrases like "validate transforms", "check transforms", "verify datatypes", "pre-flight validation".

Create a new project on a Hydrolix cluster and apply any bundle from latest_versions.yaml to it, including Grafana org and dashboards. Trigger when user wants to create a project + apply a bundle on any cluster.

Reset a previously-configured bundle to raw state so CI can re-run the full pipeline. Restores originals, removes pipeline-generated files, and pushes for CI. Use when a bundle needs to be re-processed through automation after pipeline or validator changes.

Commit, push, and open a PR for the current branch. If the PR targets hydrolix/integration-deployment-templates, also sends a Slack notification to

Batch upload Hydrolix functions and dictionaries to a cluster via the config API. Use when the user wants to upload functions, dictionaries, or both to a Hydrolix cluster.

Configure a Hydrolix integration deployment bundle with proper template variables, dashboard structure, and bundle.json. Use when the user wants to set up or fix a Hydrolix integration bundle.

Use when investigating bot scoring, classification confidence, bot intent, verified bot ownership, attack data, crawler governance, bot-driven CDN impact, suspicious automation, SIEM/spoofing evidence, control or policy-change review, protected-population collateral, entity scorecards, saved Bot Insights report artifacts, bot-share spikes, 429 surges, automation incidents or anomalies, cross-window comparisons, or capacity planning against historical bot traffic.

Diagnose and tune slow, failing, or resource-heavy Hydrolix SQL queries by classifying errors, capturing X-HDX-Query-Stats or hdx.active_queries data, mapping circuit breakers to safe first actions, and choosing query rewrites or scoped SETTINGS before persistent changes. Use when a Hydrolix query is timing out, OOMing, returning DB::Exception or HdxStorageError, hitting a circuit breaker (max_timerange, max_partitions, max_columns, max_result_rows/bytes), being canceled by the query head, or running slower than expected over MCP, the HTTP Query API, or another SQL client.

Review a pull request and post structured feedback as a comment.