Core Concepts

Understanding the key concepts in ReliaPulse will help you use the application effectively.

Organizations

An Organization is the top-level entity that contains all your status page data. Organizations provide:

• Multi-tenancy: Each organization has its own components, incidents, status pages, and settings
• Team collaboration: Multiple users can belong to an organization with different roles
• Isolation: Data is completely separated between organizations

User Roles

A user can belong to multiple organizations and switch between them.

Components

Components represent the services, systems, or infrastructure you want to track and display on your status page.

Component Types

Component Hierarchy

Components can be organized hierarchically:

├── Backend Services (SERVICE - group)
│   ├── API Gateway (ENDPOINT)
│   ├── Authentication (ENDPOINT)
│   └── Database Cluster (SERVICE)
│       ├── Primary DB (METRIC - CPU usage)
│       └── Replica DB (METRIC - replication lag)
└── Frontend (SERVICE - group)
    ├── Web App (ENDPOINT)
    └── CDN (SERVICE)

Component Status

Incidents

Incidents represent service disruptions or issues that affect your users.

Incident Lifecycle

┌─────────────┐     ┌──────────────┐     ┌──────────────┐
│ Investigating│ ──► │  Identified  │ ──► │  Monitoring  │
└─────────────┘     └──────────────┘     └──────────────┘
                                                │
                                                ▼
                                         ┌──────────────┐
                                         │   Resolved   │
                                         └──────────────┘

Incident Components

Each incident can affect one or more components. When you create an incident:

1. Select affected components
2. Choose the impact level for each component
3. Components automatically update their status

Incident Updates

Add updates to keep users informed:

• Each update has a status (Investigating, Identified, etc.)
• Updates are displayed chronologically on the status page
• Subscribers receive notifications for each update

Postmortems

After resolving an incident, you can add a postmortem:

• Root cause analysis - What went wrong
• Impact summary - Who/what was affected
• Timeline - Sequence of events
• Action items - Steps to prevent recurrence

Maintenances

Maintenances are scheduled events that may affect service availability.

Maintenance States

Auto-Transitions

ReliaPulse automatically transitions maintenances:

• Scheduled → In Progress: When start time is reached
• In Progress → Completed: When end time is reached (if auto-complete enabled)

Status Pages

A Status Page is a public-facing page that displays your service status.

Key Features

• Custom URL: Each page has a unique slug (e.g., /status/my-company)
• Multiple pages: Create different pages for different audiences
• Widgets: Drag-and-drop components like status cards, uptime charts, incident feeds
• Branding: Custom logos, colors, and themes
• Visibility: Public, private (password), or draft

Widget Types

Monitors

Monitors are automated health checks for ENDPOINT components.

How Monitoring Works

1. Worker runs checks at configured intervals (e.g., every 60 seconds)
2. Each check evaluates conditions (status code, response time, JSON path)
3. Failures trigger alerts and optionally create incidents
4. Recovery clears alerts and resolves auto-created incidents

Monitor Conditions

Subscribers

Subscribers are users who want to receive notifications about status changes.

Subscription Channels

What Subscribers Receive

• New incident notifications
• Incident updates
• Incident resolutions
• Scheduled maintenance announcements
• Maintenance status changes

Integrations

Integrations connect ReliaPulse with external monitoring and metrics systems.

Supported Integrations

Metrics Flow

Integration → Metrics Query → Polling (Worker) → Data Points → Display

Next Steps

Now that you understand the concepts:

1. Create your first status page
2. Create your first incident
3. Explore the User Guide