Alerts, incidents and on-call

Alerts

Setup proposes alerts for your important flows (errors, latency and volume against each flow's own baseline). Create more on Alerts, or ask the agent. Without any rule, the watcher still compares every flow with its usual behaviour and raises findings in your inbox.

Incidents

When an alert fires, Flowhawk opens an incident and builds its page within about two minutes: which flow broke, how many requests and customers it hit, the change behind it (deploys, flags, config), and the traces and logs that prove it. Ask the agent to investigate for a deeper look; each investigation is charged at the price on the billing page. A stakeholder view states only the facts, for people outside engineering.

On-call and paging

Set schedules and escalation policies on On-call. Each person adds their phone and push devices in Settings > On-call contact. Pages go by push and email for free, and by text message or phone call where your workspace turns them on. Acknowledge from the page, the email or Slack.

Status pages

Publish a status page on Status pages: its components follow your flows and uptime checks, and updates can be drafted from the incident. Visitors can subscribe by email or webhook.

Integrations

Alerts and automations can email the workspace's owners and admins (or any address) without connecting anything; that is where setup sends them until you connect a chat tool. Slack, Microsoft Teams, Discord, PagerDuty, Opsgenie, webhooks, GitHub, Jira, Linear and Notion connect in Settings > Integrations.