Use casesStatus page and uptime monitoring

Build your status page and uptime monitoring.

Keep monitoring observations and approved service updates separate.

How to build your status page and uptime monitoring

  1. Describe the job

    Keep monitoring observations and approved service updates separate.

  2. Review the first version

    Choose how the support analyst records the service and how the engineering owner reviews the next step.

  3. Refine the views

    Ask First to adjust the fields and views for the people who will use the app.

  4. Test before sharing

    Walk through the process with a sample record and check who owns the next action.

A status page and uptime monitoring example

A test check fails once while the service owner has not confirmed an incident.

Illustrative workflowStatus page and uptime monitoring

Status page and uptime monitoring example

Record
Status page and uptime monitoring · 01
Owner
Support analyst

Current stage · Support analyst

Open the service

A test check fails once while the service owner has not confirmed an incident.

Read the full walkthrough
  1. Open the service

    A test check fails once while the service owner has not confirmed an incident.

    Record:
    Status page and uptime monitoring · 01
    Owner:
    Support analyst
  2. Review the resolution evidence

    Keep the observation separate from an approved public status update.

    Stage:
    Awaiting engineering owner review
    Owner:
    Engineering owner
  3. Wait for the service owner's review

    Wait for the service owner's review before publishing an incident statement.

    Next action:
    Wait for the service owner's review before publishing an incident statement.
    Owner:
    Release reviewer

What to include in your status page and uptime monitoring

  • Keep the service in context

    Keep service, observation source, incident, update draft, review owner and resolution evidence together so the next person can understand the request or record.

  • When the next step needs a decision

    A test check fails once while the service owner has not confirmed an incident. Keep the observation separate from an approved public status update.

  • Keep resolution evidence visible

    Wait for the service owner's review before publishing an incident statement.

  • Choose what each person needs

    Give the support analyst a working view and the engineering owner a review view. Keep service and observation source attached to the decision as the work moves between them.

Questions about status page and uptime monitoring

Start with service, observation source, incident, update draft, review owner and resolution evidence. Describe who enters the information and who reviews the next step.

Build your status page and uptime monitoring.

Start with your workflow and make it yours.

Get started