Skip to main content

Getting Started

This guide gets you from zero to a working StatiBeat setup using the actual application surfaces that exist today.

1. Define the services your customers care about​

Start with the things customers actually understand:

  • products
  • regions
  • services
  • major components

This gives your status page a structure customers can follow when incidents happen.

2. Set up your public status page​

Your status page should make it easy for users to answer three questions:

  1. Is something wrong?
  2. What is affected?
  3. Is the team working on it?

StatiBeat is designed to make those answers visible quickly.

3. Prepare incident and maintenance templates​

Templates help your team move faster when the pressure is on. Prepare common update patterns ahead of time so nobody has to write from scratch during a stressful incident.

4. Decide who can publish updates​

Before your first serious incident, make sure the right people have access to publish updates, plan maintenance, and manage service structure.

If you plan to automate those workflows, read the API Reference and API Tokens early rather than bolting the API on later.

5. Test the workflow​

Run through a mock incident:

  • mark an affected service
  • post a customer-facing update
  • resolve the incident
  • review how the timeline reads from a customer perspective

That gives your team confidence before the real thing.

6. Add proactive monitoring if you want automated drafts​

If you want StatiBeat to help spot issues before customers report them, add one or two Beats for your most important customer-facing paths first.

Good early candidates are:

  • a public homepage or status-page HTTP check
  • a core API health endpoint
  • an SSL certificate check for a customer-facing hostname

Start small, confirm the thresholds make sense, and decide whether warning or critical stages should stay as reviewable drafts or post automatically.

  1. Read Designing Your Hierarchy
  2. Read Public Status Pages
  3. Read Incidents and Maintenance
  4. Read Beats if you want synthetic checks and automated incident drafts
  5. Read Using the Slack App if your team works in Slack
  6. Read API Reference or API Tokens if you want automation
  7. Read Terraform Workspace and Export or Terraform Provider Overview if you want config as code