Integrations
ClickHouse
Query robot data where it already lives. The agent queries your fleet events, summaries and metrics in ClickHouse with read-only SQL.
The agent answers fleet-wide questions in SQL against the robot data you already keep in ClickHouse. It shows you the SQL, then opens the recordings behind the rows that matter.
Setup: you connect ClickHouse with a read-only user.
What to use it for
- Count how often an event happens, and on which robots.
- Find regressions after a release before a customer reports them.
- Let support and operations answer fleet questions without an analyst who knows the schema.
- Save results as a CSV file to chart next to the robot's recordings.
Example
Fictional example.
Ask: "Did emergency stops go up after the 4.2 release? If so, where?"
Agent: Yes: from 0.11 to 0.29 per robot-hour, 14 days before and after the rollout. 85% of the rise is at two sites with glass walls. [SQL shown] [Recordings linked]
How to use it
- Any member of your organisation can connect ClickHouse in Alloy under Integrations.
- Use a read-only ClickHouse user. The agent can query any table that user can read.
- Ask in the Alloy app, in Slack or on a Jira ticket.
Related
Google Cloud Storage
Pick up each new run from your Cloud Storage bucket. Alloy copies each new run folder and turns it into a mission. Your bucket stays the original.
NAS and file shares
Upload runs from a file share with Alloy Edge. Alloy Edge, on a machine that reads your network share, uploads each finished recording.