Skip to main content

​
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

1

Open Your Stack

Navigate to Monitoring → Stacks and select your Stack
2

Click Add Component

In the Components section, click “Add Component” button
3

Search for Service

Use the search bar to find your service:
Type the service name:
  • “GitHub”
  • “AWS”
  • “Stripe”
  • “Cloudflare”
4

Select Components

Choose which components to monitor:Select ComponentsTips:
  • ✅ 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
5

Review and Add

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

​
Cloud Providers

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
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
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
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

Available Components:
  • Git Operations
  • API Requests
  • Webhooks
  • GitHub Pages
  • GitHub Actions
  • GitHub Packages
  • Codespaces
Recommended for:
  • Development teams
  • CI/CD pipelines
  • Deployment automation
Available Components:
  • Git Operations
  • API
  • Pages
  • CI/CD Pipelines
  • Container Registry
Recommended for:
  • Self-hosted Git
  • DevOps workflows
  • Enterprise development
Available Components:
  • Edge Network
  • Build System
  • Serverless Functions
  • Analytics
  • Image Optimization
Recommended for:
  • Frontend deployments
  • Next.js applications
  • Jamstack sites
Available Components:
  • Build System
  • CDN
  • Functions
  • Forms
  • Identity
Recommended for:
  • Static sites
  • Jamstack applications
  • CI/CD for frontend

​
SaaS & Business Tools

Available Components:
  • API
  • Checkout
  • Dashboard
  • Connect
  • Billing
  • Webhooks
Recommended for:
  • Payment processing
  • Subscription billing
  • E-commerce platforms
Available Components:
  • Storefront
  • Admin API
  • Checkout
  • Payments
  • Apps
Recommended for:
  • E-commerce sites
  • Online stores
  • Retail operations
Available Components:
  • Sales Cloud
  • Service Cloud
  • Marketing Cloud
  • API
  • Community Cloud
Recommended for:
  • CRM systems
  • Sales operations
  • Customer service

​
Infrastructure & CDN

Available Components:
  • DNS
  • CDN
  • SSL/TLS
  • Workers
  • Pages
  • Stream
  • R2 Storage
Recommended for:
  • DNS management
  • DDoS protection
  • Edge computing
Available Components:
  • CDN
  • Edge Cloud
  • Image Optimizer
  • Next-Gen WAF
Recommended for:
  • High-performance CDN
  • Video streaming
  • Edge computing

​
Databases & Data

Available Components:
  • Cluster Operations
  • Data API
  • Backup Service
  • Search
  • Charts
Recommended for:
  • NoSQL databases
  • Document storage
  • Cloud databases
Available Components:
  • Database Operations
  • Pub/Sub
  • JSON
  • Search
  • TimeSeries
Recommended for:
  • Caching layer
  • Session storage
  • Real-time applications
Available Components:
  • Database Operations
  • Branching
  • Insights
  • Deploy Requests
Recommended for:
  • MySQL databases
  • Serverless databases
  • Schema management

​
Communication & Collaboration

Available Components:
  • Messaging
  • Calls
  • Workspace
  • Apps/Integrations
  • Enterprise Grid
Recommended for:
  • Team communication
  • Integration dependencies
  • Notification delivery
Available Components:
  • API
  • Voice
  • Media Proxy
  • Third-party Networks
Recommended for:
  • Community platforms
  • Gaming applications
  • Real-time chat
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

1

Open Stack

Navigate to your Stack in the dashboard
2

Find Component

Locate the component you want to remove
3

Click Remove

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

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:
  1. Open Stack settings
  2. Navigate to “Component Order” section
  3. Drag and drop components to reorder
  4. 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

1

Open Stack Settings

Click the ⚙️ Settings icon in your Stack
2

Navigate to Groups

Go to “Component Groups” section
3

Create Group

Click “Add Group” and enter:
  • Group Name (e.g., “Core Services”, “Infrastructure”)
  • Description (optional)
  • Collapse by Default (show/hide components)
4

Assign Components

Drag components into the appropriate groups
5

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

  1. Click the ⋮ menu next to a component
  2. Select “Edit Display Name”
  3. Enter your custom name
  4. 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

1

Open Stack Settings

Navigate to Stack → Settings
2

Find Auto-Add Section

Scroll to “Auto-Add Components”
3

Select Sources

Choose which Sources should auto-add new components:
  • ✅ Enable for stable Sources (AWS, GitHub)
  • ❌ Disable for noisy Sources (might add unwanted components)
4

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

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:
  1. Week 1: Core infrastructure (hosting, database)
  2. Week 2: Critical dependencies (payments, auth)
  3. Week 3: Communication services (email, SMS)
  4. Week 4: Nice-to-have integrations
Focus on customer-facing services
  • ✅ Payment processing (Stripe)
  • ✅ Email delivery (SendGrid)
  • ✅ CDN (Cloudflare)
  • ✅ Hosting (Vercel, AWS)
  • ❌ Internal admin tools
  • ❌ Development environments
  • ❌ Rarely-used integrations
Customize component display namesGeneric names:
  • “API”
  • “Database”
  • “Storage”
Descriptive names:
  • “Production API (us-east-1)”
  • “Customer Database (PostgreSQL)”
  • “User Uploads (S3)”
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:
  1. Check spelling and try alternative names (e.g., “AWS” vs “Amazon Web Services”)
  2. Browse by category instead of searching
  3. Request the Source via “Request Source” button
  4. Use a custom monitor if it’s your own service

​
Component Status Not Updating

Issue: Component shows stale or incorrect status Possible causes:
  1. Source temporarily unavailable (wait 5 minutes)
  2. StatusStack connectivity issue
  3. Source changed their status page format
Solutions:
  1. Refresh the page and wait 5 minutes
  2. Check StatusStack’s status
  3. Remove and re-add the component
  4. Contact support if issue persists

​
Too Many Components

Issue: Stack is cluttered with too many components Solutions:
  1. Remove unused or rarely-needed components
  2. Create separate Stacks for different purposes
  3. Use component grouping to organize
  4. 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