Adding Services - StatusStack Documentation

Overview

StatusStack monitors 5,200+ sources out of the box. This guide shows you how to add services to your Stacks and configure component-level monitoring.

Understanding Sources and Components

Sources

External services like GitHub, AWS, Stripe, CloudflareSources are the third-party services StatusStack monitors automatically

Components

Individual parts of a Source (e.g., AWS EC2, S3, RDS)Components are the specific services within a Source you want to monitor

Example: GitHub as a Source

Source: GitHub
  ├─ Component: Git Operations
  ├─ Component: API Requests
  ├─ Component: Webhooks
  ├─ Component: GitHub Pages
  ├─ Component: GitHub Actions
  └─ Component: GitHub Packages

You can add all or just select components to your Stack.

Adding Third-Party Services

Open Your Stack

Navigate to Monitoring → Stacks and select your Stack

Click Add Component

In the Components section, click “Add Component” button

Search for Service

Use the search bar to find your service:

Search by Name
Browse by Category
Popular Services

Type the service name:

“GitHub”
“AWS”
“Stripe”
“Cloudflare”

Select Components

Choose which components to monitor: Select Components

Tips:

✅ Select only components you actually use
✅ Read component descriptions to understand what they monitor
❌ Don’t add all components just because they’re available
❌ Avoid monitoring deprecated or legacy components

Review and Add

Review your selections and click “Add to Stack” Components Added

Popular Services by Category

Cloud Providers

Amazon Web Services (AWS)

Available Components:

EC2 (Elastic Compute Cloud)
S3 (Simple Storage Service)
RDS (Relational Database Service)
Lambda (Serverless Functions)
CloudFront (CDN)
Route 53 (DNS)
DynamoDB (NoSQL Database)
SQS (Message Queue)
And 20+ more…

Recommended for:

Infrastructure monitoring
Cloud-native applications
Multi-service dependencies

Microsoft Azure

Available Components:

Virtual Machines
App Service
SQL Database
Blob Storage
Azure Functions
Azure CDN
Azure Active Directory
And more…

Recommended for:

Microsoft-centric infrastructure
Enterprise applications
Hybrid cloud deployments

Google Cloud Platform (GCP)

Available Components:

Compute Engine
Cloud Storage
Cloud SQL
Cloud Functions
Cloud CDN
Cloud DNS
And more…

Recommended for:

Data-intensive applications
Machine learning workloads
Google Workspace integration

DigitalOcean

Available Components:

Droplets
Managed Databases
Spaces (Object Storage)
App Platform
Load Balancers

Recommended for:

Simple infrastructure
Startups and small teams
Cost-effective hosting

Development & CI/CD

GitHub

Available Components:

Git Operations
API Requests
Webhooks
GitHub Pages
GitHub Actions
GitHub Packages
Codespaces

Recommended for:

Development teams
CI/CD pipelines
Deployment automation

GitLab

Available Components:

Git Operations
API
Pages
CI/CD Pipelines
Container Registry

Recommended for:

Self-hosted Git
DevOps workflows
Enterprise development

Vercel

Available Components:

Edge Network
Build System
Serverless Functions
Analytics
Image Optimization

Recommended for:

Frontend deployments
Next.js applications
Jamstack sites

Netlify

Available Components:

Build System
CDN
Functions
Forms
Identity

Recommended for:

Static sites
Jamstack applications
CI/CD for frontend

SaaS & Business Tools

Stripe

Available Components:

API
Checkout
Dashboard
Connect
Billing
Webhooks

Recommended for:

Payment processing
Subscription billing
E-commerce platforms

Shopify

Available Components:

Storefront
Admin API
Checkout
Payments
Apps

Recommended for:

E-commerce sites
Online stores
Retail operations

Salesforce

Available Components:

Sales Cloud
Service Cloud
Marketing Cloud
API
Community Cloud

Recommended for:

CRM systems
Sales operations
Customer service

Infrastructure & CDN

Cloudflare

Available Components:

DNS
CDN
SSL/TLS
Workers
Pages
Stream
R2 Storage

Recommended for:

DNS management
DDoS protection
Edge computing

Fastly

Available Components:

CDN
Edge Cloud
Image Optimizer
Next-Gen WAF

Recommended for:

High-performance CDN
Video streaming
Edge computing

Databases & Data

MongoDB Atlas

Available Components:

Cluster Operations
Data API
Backup Service
Search
Charts

Recommended for:

NoSQL databases
Document storage
Cloud databases

Redis Cloud

Available Components:

Database Operations
Pub/Sub
JSON
Search
TimeSeries

Recommended for:

Caching layer
Session storage
Real-time applications

PlanetScale

Available Components:

Database Operations
Branching
Insights
Deploy Requests

Recommended for:

MySQL databases
Serverless databases
Schema management

Communication & Collaboration

Slack

Available Components:

Messaging
Calls
Workspace
Apps/Integrations
Enterprise Grid

Recommended for:

Team communication
Integration dependencies
Notification delivery

Discord

Available Components:

API
Voice
Media Proxy
Third-party Networks

Recommended for:

Community platforms
Gaming applications
Real-time chat

Microsoft Teams

Available Components:

Messaging
Calls & Meetings
Calendar
Apps
Admin Center

Recommended for:

Enterprise communication
Microsoft 365 integration
Corporate collaboration

Component Management

Viewing Component Status

Each component in your Stack displays:

Current Status

Real-time status indicator (Operational, Degraded, Critical)

Last Updated

Timestamp of the last status check

Uptime Percentage

Historical uptime over 7/30/90 days

Incident History

Recent outages and status changes

Removing Components

Open Stack

Navigate to your Stack in the dashboard

Find Component

Locate the component you want to remove

Click Remove

Click the ⋮ menu next to the component and select “Remove from Stack”

Confirm

Confirm the removal when prompted

Removing a component does not delete historical data, but it will no longer be monitored or appear on your status page.

Reordering Components

Customize the order components appear on your status page:

Open Stack settings
Navigate to “Component Order” section
Drag and drop components to reorder
Click “Save Order”

Recommended order:

Most critical services first
Group related services together
Customer-facing services before internal ones

Component Grouping

Organize components into logical groups for better visualization:

Creating Component Groups

Open Stack Settings

Click the ⚙️ Settings icon in your Stack

Navigate to Groups

Go to “Component Groups” section

Create Group

Click “Add Group” and enter:

Group Name (e.g., “Core Services”, “Infrastructure”)
Description (optional)
Collapse by Default (show/hide components)

Assign Components

Drag components into the appropriate groups

Save Changes

Click “Save Groups”

Example Grouping Structure

Production Stack
  ├─ 🔧 Core Services (Expanded)
  │    ├─ Production API
  │    ├─ Database
  │    └─ Cache Layer
  │
  ├─ 🌐 Infrastructure (Expanded)
  │    ├─ AWS EC2
  │    ├─ AWS S3
  │    └─ Cloudflare CDN
  │
  ├─ 💳 Payment Processing (Collapsed)
  │    ├─ Stripe API
  │    └─ Stripe Webhooks
  │
  └─ 📧 Communication (Collapsed)
       ├─ SendGrid Email
       └─ Twilio SMS

Custom Component Display Names

Rename components for clarity on your status page:

Why Customize Names?

Add context: “Production API” instead of “API”
Clarify purpose: “Customer Database” instead of “AWS RDS”
Match internal naming: Align with your team’s terminology

How to Customize

Click the ⋮ menu next to a component
Select “Edit Display Name”
Enter your custom name
Click “Save”

The custom name only affects how it appears on your status page, not the actual monitoring.

Auto-Adding Components

Automatically add new components when a Source adds them:

Enabling Auto-Add

Open Stack Settings

Navigate to Stack → Settings

Find Auto-Add Section

Scroll to “Auto-Add Components”

Select Sources

Choose which Sources should auto-add new components:

✅ Enable for stable Sources (AWS, GitHub)
❌ Disable for noisy Sources (might add unwanted components)

Save Settings

Click “Save Preferences”

Use with caution: Some Sources frequently add/remove components. This can clutter your Stack with unused components.Recommended: Only enable for Sources where you want comprehensive monitoring.

Monitoring Multiple Sources

Scenario: Full-Stack Application

For a typical web application, you might monitor:

Production Stack:
  # Cloud Infrastructure
  - AWS EC2 (Compute)
  - AWS RDS (Database)
  - AWS S3 (File Storage)
  - Cloudflare (CDN & DNS)

  # Development & Deployment
  - GitHub (Code Repository)
  - Vercel (Frontend Hosting)

  # Third-Party Services
  - Stripe (Payments)
  - SendGrid (Email)
  - Twilio (SMS)

  # Monitoring & Tools
  - Sentry (Error Tracking)
  - PostHog (Analytics)

Scenario: SaaS Platform

Production Stack:
  # Core Infrastructure
  - Google Cloud Platform (Compute, Storage, Database)
  - Cloudflare (CDN, DNS, DDoS Protection)

  # Application Services
  - Production API (Custom Monitor)
  - Production Website (Custom Monitor)

  # Dependencies
  - Stripe (Subscription Billing)
  - Customer.io (Marketing Automation)
  - Intercom (Customer Support)
  - Segment (Analytics Pipeline)

Best Practices

Start Small, Grow Gradually

Don’t add everything at once

Start with 5-10 most critical services
Add more as you identify dependencies
Monitor what actually impacts your users

Example progression:

Week 1: Core infrastructure (hosting, database)
Week 2: Critical dependencies (payments, auth)
Week 3: Communication services (email, SMS)
Week 4: Nice-to-have integrations

Monitor What Impacts Users

Focus on customer-facing services

✅ Payment processing (Stripe)
✅ Email delivery (SendGrid)
✅ CDN (Cloudflare)
✅ Hosting (Vercel, AWS)
❌ Internal admin tools
❌ Development environments
❌ Rarely-used integrations

Use Descriptive Names

Customize component display namesGeneric names:

“API”
“Database”
“Storage”

Descriptive names:

“Production API (us-east-1)”
“Customer Database (PostgreSQL)”
“User Uploads (S3)”

Organize for clarity

✅ Good Grouping:
  Core Services
    - API
    - Database
    - Cache

  Infrastructure
    - AWS
    - Cloudflare

  Third-Party
    - Stripe
    - SendGrid

❌ Poor Grouping:
  Important Stuff
    - Everything

Regular Maintenance

Keep your Stack cleanMonthly tasks:

Remove deprecated components
Add newly-integrated services
Update component display names
Verify grouping still makes sense
Check for unused Sources

Troubleshooting

Component Not Found

Issue: Can’t find a service you want to monitor Solutions:

Check spelling and try alternative names (e.g., “AWS” vs “Amazon Web Services”)
Browse by category instead of searching
Request the Source via “Request Source” button
Use a custom monitor if it’s your own service

Component Status Not Updating

Issue: Component shows stale or incorrect status Possible causes:

Source temporarily unavailable (wait 5 minutes)
StatusStack connectivity issue
Source changed their status page format

Solutions:

Refresh the page and wait 5 minutes
Check StatusStack’s status
Remove and re-add the component
Contact support if issue persists

Too Many Components

Issue: Stack is cluttered with too many components Solutions:

Remove unused or rarely-needed components
Create separate Stacks for different purposes
Use component grouping to organize
Disable auto-add for noisy Sources

Next Steps

Custom Monitoring

Monitor your own websites and APIs

Notification Setup

Get alerted when services go down

Status Pages

Customize your public status page

Source Concepts

Deep dive into Sources and Components

​Overview

​Understanding Sources and Components

Sources

Components

​Example: GitHub as a Source

​Adding Third-Party Services

​Popular Services by Category

​Cloud Providers

​Development & CI/CD

​SaaS & Business Tools

​Infrastructure & CDN

​Databases & Data

​Communication & Collaboration

​Component Management

​Viewing Component Status

Current Status

Last Updated

Uptime Percentage

Incident History

​Removing Components

​Reordering Components

​Component Grouping

​Creating Component Groups

​Example Grouping Structure

​Custom Component Display Names

​Why Customize Names?

​How to Customize

​Auto-Adding Components

​Enabling Auto-Add

​Monitoring Multiple Sources

​Scenario: Full-Stack Application

​Scenario: SaaS Platform

​Best Practices

​Troubleshooting

​Component Not Found

​Component Status Not Updating

​Too Many Components

​Next Steps

Custom Monitoring

Notification Setup

Status Pages

Source Concepts

Overview

Understanding Sources and Components

Example: GitHub as a Source

Adding Third-Party Services

Popular Services by Category

Cloud Providers

Development & CI/CD

SaaS & Business Tools

Infrastructure & CDN

Databases & Data

Communication & Collaboration

Component Management

Viewing Component Status

Removing Components

Reordering Components

Component Grouping

Creating Component Groups

Example Grouping Structure

Custom Component Display Names

Why Customize Names?

How to Customize

Auto-Adding Components

Enabling Auto-Add

Monitoring Multiple Sources

Scenario: Full-Stack Application

Scenario: SaaS Platform

Best Practices

Troubleshooting

Component Not Found

Component Status Not Updating

Too Many Components

Next Steps