Managing Services
Learn how to create and manage services on your status page, including grouping and status monitoring
Services (also called components) are the individual elements that your status page monitors. Each service represents a specific part of your system, such as APIs, databases, web servers, or third-party integrations.
Service Properties
Each service has the following properties:
Name - Display name for the service (e.g., "API Server", "Database")
Description - Optional description explaining what the service does
Group - Optional group name for organizing related services
Status - Current operational status of the service
Sort Order - Determines display order within the group
Organizing Services with Groups
Services can be grouped together for better organization. Common groupings include:
Infrastructure
Web Servers
Database Cluster
Cache Layer (Redis/Memcached)
Load Balancers
API Services
REST API
GraphQL API
Authentication Service
Payment Gateway
Third-party Integrations
Email Service (SendGrid, Mailgun)
SMS Service (Twilio)
Payment Processor (Stripe, PayPal)
CDN (CloudFlare, AWS CloudFront)
Service Status Monitoring
Each service displays its current status with:
Status Dot - Colored indicator showing operational state
Status Label - Text description (Operational, Degraded, etc.)
Description - Optional additional context (shown when enabled)
Pulse Animation - Non-operational services show a pulsing indicator
Configuring Service Status
Service status is updated automatically based on:
Active Incidents - Services affected by active incidents show degraded/outage status
Status Updates - You can manually update service status for scheduled maintenance
Automatic Monitoring - Integrate with monitoring tools to auto-update status
Service Status Mappings
The following API status types map to component display statuses:
API StatusDisplay StatusoperationalOperationaldegraded_performanceDegradedpartial_outagePartial Outagemajor_outageMajor OutagemaintenanceDegradedincidentMajor Outage
Best Practices
Group related services together for better organization
Use clear, descriptive names that users understand
Include descriptions for technical services to explain their purpose
Set appropriate sort order to prioritize important services
Only create services that are visible to end-users or critical to operations
Keep service count manageable (10-20 services is typically sufficient)
Was this article helpful?