Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

The Canary Workflow: A Fake n8n Job That Pages Me Before Clients Notice

说明与用途

问题:n8n 中的客户工作流可能会在平台层面无声失效。解决方案:每小时运行一次“金丝雀”工作流,检查 LLM API、Gmail、Webhook 和 n8n API,并通过 Telegram 发送警报。六个月内,它在客户发现之前捕获了四起事件,避免了投诉。

问题

Client workflows can fail silently on the platform layer, causing clients to notice outages before the owner does.

结果

In six months the canary detected four incidents—revoked OAuth token, model deprecation, queue backup, TLS cert expiry—before any client noticed, preventing any client complaints.

工作流

  • Schedule canary to run hourly
  • Probe LLM API with 10‑token prompt and 30s timeout
  • Probe Gmail by sending and searching for a unique email
  • Probe webhook by POSTing signed payload and checking 200 within 10s
  • Probe n8n API for own execution history
  • Log results and page via Telegram on failure
  • If two probes fail, start 15‑minute re‑check loop

证据

The canary tells me first, every time.

来源

The canary runs every hour and produces nothing of value. Its only job is to touch the four things every real workflow in my fleet depends on: LLM API, Gmail round‑trip, Webhook echo, n8n API self‑query.

来源

In six months, four real incidents — and in all four, the canary paged me before any client noticed.

来源

Rule 1: the canary must be cheaper than what it protects.

来源

  • 记录日期: 2026-10-18T02:56:01.215Z