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. The page shows which flow broke, how many requests and customers it hit, the deploy, flag or config change most likely behind it, and the traces and logs that back this up. For a deeper look, ask the agent to investigate. Each investigation is charged at the price on the billing page. There is also a stakeholder view with just 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 or the email.

Status pages

You can publish a status page from 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. Setup sends alerts there until you connect a chat tool. Microsoft Teams, Google Chat, Discord, Mattermost, PagerDuty, Opsgenie, incident.io, Rootly and signed webhooks connect in Settings > Integrations, and so do deploy and flag sources such as GitHub Actions, GitLab, Vercel and LaunchDarkly webhooks. Slack, and GitHub, Jira, Linear and Notion for issues and pull requests, aren't available on hosted workspaces yet, and Settings > Integrations says so.