On October 22, the steps from creating an integration to receiving its first event were rebuilt: rules show their result as you edit them, and the page says which setup step you are on.
Preview rules as you edit them
The rule editor for the alert pipeline and for label enhancement now has a preview card on the right: it runs the current rules on one real raw event, unsaved edits included. The event source is either Recent events — the raw events this integration received, keeping the latest 20 for 7 days and at most one every 10 seconds — or Custom, where you paste or edit the event JSON; a syntax error points at the line and column, and the last preview result stays until it is fixed.
An alert-pipeline preview runs the saved label enhancement first, then the rules here, and shows the title, description, severity, and labels Before (after label enrichment) and After, plus a result per rule: applied, no match, skipped, not run, dropped, inhibited, error. A label-enhancement preview marks every label with Added by rule N, Changed by rule N, or Dropped by rule N. At most 50 rules run at a time; past that, the card asks you to remove some rules.
A five-step finish-setup checklist
After a push-type integration is saved, the detail page opens with a five-step Finish setup checklist above the configuration preview: create the integration, put the push URL into the upstream, receive the first event, label enrichment, alert pipeline — with x/5 done at the top right and the last two steps marked Optional.
While you wait for the first event, the checklist offers Copy curl command: run it on the upstream host to check both the push URL and the network in one go (not every integration type provides one). Clicking Configured, wait for a real alert changes the list to Waiting for the first event. Receiving an event collapses the list to one line — Connected · Latest event … — and swaps the right panel from setup docs to First event (severity, title, description, labels, with a link back to the docs). The "configured" state is remembered per integration in the current browser. Email integrations are connected through a receiving address and do not show this checklist.
Upload an .eml file to try an email integration
The email integration's "Try an email" section gains an Upload .eml source alongside Received and Paste. The file is parsed by the same code that receives email and is capped at 5 MB — the same limit as live email, so a larger file reports that email that large is not received either.
Schedule bots can @-mention the people on duty
The Feishu bot, WeCom bot, and Zoom bot channels of a schedule gain Enable @ mentions: the notification mentions only the people on duty for that notification, and the next shift is shown by name without a mention. Feishu and Zoom also require a compatible User information mapping, and an incompatible one is rejected when you save; WeCom can go without one, in which case members are mentioned by phone number. A new channel starts with the switch off for Feishu and Zoom and on for WeCom. The DingTalk bot always mentions people by phone number and has no such switch; Slack and Telegram bots never mention anyone.
Get started
Go to Flashduty console → Integrations and open any alert integration's detail page.
Product docs: Alert pipeline, Label enhancement, Alert integrations overview, Email integration, Schedule.