skyfleet
ClickStack
Every firing ClickStack alert gets an agent. Paste an API key and Skyfleet wires your alerts.
Go to Connections, press Add on ClickStack under Alerts and incidents, paste a ClickHouse Cloud API
key as KEY_ID:KEY_SECRET and press Connect. Make the key under Organization → API keys with a role that can
manage ClickStack. If it reaches more than one service, pick the Service and press Connect to this service.
This adds the Incident response use case to your Dashboard. Skyfleet then makes the ClickStack side and lists what
it made:
A webhook that posts to Skyfleet with your source's token and a body Skyfleet understands: the alert's status, a fingerprint from the alert and its group, its title and its link.
Your alerts send to it. The webhook is added to every alert on that service, keeping the channels each one already has. A service with no alerts yet gets none: pick the webhook on an alert in ClickStack later.
Deleting the source takes the webhook off those alerts and deletes it.
The same alert is one issue in your Inbox; repeats only count. A recovery never starts an agent. ClickStack's own Test Webhook button sends a masked header, so it always fails against Skyfleet: test with a real alert instead.
Give every agent the ClickStack tools
Press Let agents use ClickStack's tools too → once ClickStack is added, or Connect on Logs in a use case and pick ClickStack tools. Paste your Service id (in ClickStack, under Team Settings → API & Agents), then Continue to ClickStack and sign in with ClickHouse. Agents can then search your logs and traces through your login.