Skip to content

Status Page Components

Components represent individual services on your status page.

Adding Components

  1. Edit your status page
  2. Click Add Component
  3. Select the test to link
  4. Enter a display name
  5. Add an optional description
  6. Save

Component Settings

SettingDescription
TestThe Pingward test that determines this component's status
Display NameCustomer-facing name (e.g., "API", "Dashboard")
DescriptionOptional context (e.g., "REST API for mobile apps")
Display OrderPosition on the status page

Status Mapping

Component status is derived from the linked test:

Test StateComponent Status
PassingOperational
Slow (assertion)Degraded Performance
Intermittent failuresPartial Outage
FailingMajor Outage

Manual Override

For planned maintenance, you can manually set status:

  1. Edit the component
  2. Set status to "Maintenance"
  3. Add a maintenance message
  4. Save

Remember to clear the override when maintenance completes.

Reordering Components

Drag and drop components to reorder them, or:

  1. Click the menu on a component
  2. Select Move Up or Move Down

Components at the top are seen first by visitors.

Grouping Strategies

By Service Type

Core Services
├── Web Application
├── API
└── Mobile App

Integrations
├── GitHub
├── Slack
└── Stripe

Infrastructure
├── CDN
└── DNS

By Customer Tier

Enterprise Services
├── Dedicated API
└── SSO Portal

Standard Services
├── Public API
└── Dashboard

By Region

US East
├── API (us-east-1)
└── CDN (us-east)

Europe
├── API (eu-west-1)
└── CDN (eu)

Best Practices

Use Clear Names

Customers don't know your internal naming:

  • prod-api-v2-blue
  • API

Limit Component Count

Too many components overwhelm visitors:

  • 3-7 components: Ideal
  • 8-12 components: Use grouping
  • 12+ components: Consider multiple status pages

Match Customer Mental Model

Organize components how customers think about your product:

  • What services do they use directly?
  • What would impact their work?

Don't Expose Internal Details

Avoid exposing infrastructure:

  • ❌ PostgreSQL Primary Database

  • ✅ Data Storage

  • ❌ Redis Cache Cluster

  • ✅ (Don't include at all - it's internal)

Pingward - API Monitoring Made Simple