USE CASE · PLATFORM ENGINEERING

From alarm to the right person, without waking the whole team

An alarm fires, Flomation gathers the context around it, works out who owns the thing that broke, and asks that person a clear question in the channel they are already in.

Best for
On-call and platform teams
Triggers on
CloudWatch, webhooks, log patterns
Works with
AWS, Slack, Telegram, your tracker

The alert is the easy part

An alarm tells you something is wrong. Everything after that, what changed, who owns it, whether it is already being handled, is done by a human at an awkward hour.

  • Alert fatigue. The channel fills with notices nobody can act on.
  • Context gathering. The first ten minutes go on logs, recent deploys and dashboards.
  • Ownership. Finding who to wake takes longer than the fix sometimes does.
  • The write-up. The timeline is reconstructed afterwards, from memory.

Triage before a human is involved

The flow does the gathering, applies the rules you would have applied, and only then puts it in front of somebody.

Context attached automatically

Recent deploys, matching log lines and the current metric are collected the moment the alarm fires, and travel with the alert.

Routed by ownership, not by rota

Look up who owns the service, check whether it is already being handled, and escalate only when the first person does not answer.

A decision, not a notification

Ask a clear question with buttons: acknowledge, escalate, or silence for an hour. What was chosen, and by whom, is recorded.

What triage looks like in Flomation

One alarm in, one well-formed question out to the person who can answer it.

  1. TriggerAlarm or log patternCloudWatch, webhook or log filter
  2. ActionGather contextDeploys, logs, metrics, open incidents
  3. HumanAsk the ownerAcknowledge, escalate or silence
  4. OutputRecord and follow upTicket raised, timeline written as it happens

Fewer pages, better ones

Context first
gathered before anyone is paged
One owner
asked, not the whole channel
Written as it happens
not reconstructed after
Quieter nights
noise handled without a human

Let the flow do the first ten minutes

Point one alarm at Flomation and see what arrives in the channel. Add the next alarm once the first one has stopped needing you.

Get started