Flamio On-Live

Get critical problems in Slack

Turn on critical alerts — every 30 minutes Flami looks at what changed on your site and posts the problems it judges critical to a Slack channel.

Critical alerts tell your team in Slack when something critical happens on your site, without anyone watching the dashboard. Every 30 minutes Flami looks at the problems whose state changed and posts the ones it judges critical to the channel you pick — each once, with its reason and a link.

Before you begin

  • To turn the alerts on or off, or to change their channel, you need the Editor, Admin or Owner role. Everyone else sees whether they are on and where they post.
  • Slack is connected to your organization. See Connect Slack. The alerts post to a public channel; private channels are not listed.
  • A look that asks Flami spends coins from your balance. A look where nothing changed is free.

Open Critical alerts

In the sidebar, under Flamio On-Live, click Digests. The Critical alerts panel is under the feed.

Pick the channel

Under Channel, select the public Slack channel your team watches.

Turn the alerts on

Turn on Post critical problems to Slack. The problems open at that moment are recorded as known: only what changes from then on is put to Flami.

Result

Every 30 minutes Flami looks at the problems that changed since its last look — whether your visitors met them or Scout found them:

  • a problem that newly shows as High severity on the Issues page,
  • a problem that came back after it was resolved,
  • a problem seen again after it was fixed in a release.

Flami posts the ones it judges critical to the channel, each with its one-sentence reason, the page, how many people met it and a link to the problem. A problem is posted again only when its state changes again. A look where nothing changed posts nothing.

Flami judges a problem critical when it stops or seriously hurts the people using your site — an action fails, or what someone entered is lost — or will as soon as they reach it, and your team should look at it today. Visitors leaving, a slow page or an error in the console are not enough on their own, since pages that work have them too: such a problem reads Not critical with Flami's reason and stays on the Issues page.

Latest checks lists what each look came to:

  • Nothing new — nothing changed. A run of quiet looks reads as one row.
  • Posted to Slack — Flami judged a problem critical and posted it.
  • Nothing critical — Flami looked at the changes and judged none of them critical.
  • Out of coins — the changes wait until your balance is topped up.
  • Failed — with what went wrong. While Slack cannot take a post — it was disconnected, or the channel is gone — Flami is not asked and the changes wait for Slack.

Under a look, each problem Flami was asked about reads Critical or Not critical, with what put it in front of Flami and Flami's reason. Click a problem to open it.

To move the alerts, select another Channel — they move at once. To stop them, turn off Post critical problems to Slack; the channel is kept for next time.

What alerts do not do

  • There is no alert rule of your own — no threshold on a metric, and nothing that fires when traffic stops.
  • Alerts go to Slack only, not by email. For numbers on a schedule, use the digest with New critical issues and Growing critical issues.