Statux Alerts Help Center

Everything you need to manage alerts, coordinate on-call teams, and respond to incidents quickly and effectively.

Browse Topics

Getting Started

New to Statux Alerts? Follow these steps to set up your alerting pipeline and start responding to issues faster.

Step 1: Create Your Account

Sign up at statux.io/sign-in with your email address. You can also sign in directly at alerts.statux.io/sign-in. All Statux products share a single account, so if you already use Statux Pages or Statux Synthetics, you are ready to go.

Free trial: Every new account starts with a free trial so you can explore all features before choosing a plan.

Step 2: Create an Organization

Organizations are the top-level container for everything in Statux Alerts — services, escalation policies, schedules, teams, and billing all belong to an organization.

  • After signing in, click Create Organization from the dashboard.
  • Enter a name for your organization (for example, “Acme Corp”).
  • Choose a unique slug (for example, acme-corp).
  • You can invite additional team members later from the Organization settings.

Step 3: Understand the Alert Pipeline

The core workflow in Statux Alerts follows a straightforward pipeline:

  • Alerts come in — Monitoring tools, integrations, or manual creation generate alerts that land in your alert queue.
  • Alerts get triaged — On-call responders acknowledge alerts, investigate the root cause, and take action.
  • Incidents are created (optional) — For significant or multi-alert issues, group related alerts into an incident for coordinated tracking.
  • Alerts resolve — Once the underlying issue is fixed, alerts are marked as resolved. Incidents are closed when all linked alerts are handled.
Tip: You do not need to create an incident for every alert. Incidents are best suited for significant issues that require coordination across your team or affect multiple services.

Step 4: Set Up Your First Service

Services represent the systems and applications your team is responsible for. When an alert arrives, it is routed through the service's assigned escalation policy.

  • Navigate to Services in the sidebar.
  • Click Create Service.
  • Give it a descriptive name (for example, “Payment API” or “User Database”).
  • Optionally assign an escalation policy now, or come back to this after creating one.

See Services for the full guide.

Step 5: Create an Escalation Policy

Escalation policies define who gets notified when an alert fires and what happens if no one responds in time.

  • Go to Escalation Policies in the sidebar.
  • Click Create Escalation Policy.
  • Add at least one escalation level (for example, “Level 1: Notify the on-call engineer, wait 5 minutes”).
  • Add additional levels for backup responders or managers.
  • Assign the policy to one or more services.

See Escalation Policies for the full guide.

Step 6: Build Your On-Call Schedule

Schedules determine who is on call at any given time. When an escalation policy references a schedule, the person currently on call receives the notification.

  • Go to Schedules in the sidebar.
  • Click Create Schedule.
  • Add team members to the rotation and configure the rotation interval (daily, weekly, or custom).
  • Set the handoff time and timezone.

See Schedules for the full guide.

Recommended order: Create your services first, then your escalation policies, and finally your on-call schedules. This way you can link everything together as you go.

Need Help?

Cannot find what you are looking for? Our support team is here to help.