Integrations
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.
Each new run in your Google Cloud Storage bucket becomes a mission the agent can investigate. An engineer can ask about this morning's runs about 20 to 30 minutes after they finish uploading.
Setup: Alloy connects your bucket with you during onboarding.
What to use it for
- Ask about runs without a download, a sync script or a manual upload.
- Compare runs, for example patrols from last night, with replay links to examples.
- Retire the jobs that move runs out of the bucket today.
Example
Fictional example.
Ask: "Which robots stopped for an obstacle more than ten times last night, and was it the same corridors?"
Agent: Two robots. 80% of their stops were in corridors B3 and B4. [Three replay links]
How to use it
- Alloy engineers set up the bucket connection with you during onboarding. You grant read access, and Alloy configures the connection.
- Keep your runs flowing into the bucket. Alloy reads each new run folder and makes it a mission.
- Ask the agent in the Alloy app, Slack or a Jira ticket.
- Google bills your project for the list requests. Keep only recent runs under the watched prefix to keep the cost down.