> ## Documentation Index
> Fetch the complete documentation index at: https://docs.statusstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Adding Services

> Learn how to add third-party services and components to your Stacks

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

<CardGroup cols={2}>
  <Card title="Sources" icon="globe">
    **External services** like GitHub, AWS, Stripe, Cloudflare

    Sources are the third-party services StatusStack monitors automatically
  </Card>

  <Card title="Components" icon="puzzle-piece">
    **Individual parts** of a Source (e.g., AWS EC2, S3, RDS)

    Components are the specific services within a Source you want to monitor
  </Card>
</CardGroup>

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

<Steps>
  <Step title="Open Your Stack">
    Navigate to **Monitoring** → **Stacks** and select your Stack
  </Step>

  <Step title="Click Add Component">
    In the Components section, click **"Add Component"** button
  </Step>

  <Step title="Search for Service">
    Use the search bar to find your service:

    <Tabs>
      <Tab title="Search by Name">
        Type the service name:

        * "GitHub"
        * "AWS"
        * "Stripe"
        * "Cloudflare"
      </Tab>

      <Tab title="Browse by Category">
        Select a category:

        * **Cloud Providers** (AWS, Azure, GCP)
        * **Development** (GitHub, GitLab, CircleCI)
        * **SaaS** (Stripe, Shopify, Salesforce)
        * **Infrastructure** (Cloudflare, MongoDB, Redis)
        * **Communication** (Slack, Discord, Twilio)
      </Tab>

      <Tab title="Popular Services">
        View most commonly monitored services:

        * GitHub
        * AWS
        * Cloudflare
        * Stripe
        * Vercel
      </Tab>
    </Tabs>
  </Step>

  <Step title="Select Components">
    Choose which components to monitor:

    <img src="https://mintlify.s3.us-west-1.amazonaws.com/statusticker/images/guides/select-components.png" alt="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
  </Step>

  <Step title="Review and Add">
    Review your selections and click **"Add to Stack"**

    <img src="https://mintlify.s3.us-west-1.amazonaws.com/statusticker/images/guides/components-added-success.png" alt="Components Added" />
  </Step>
</Steps>

***

## Popular Services by Category

### Cloud Providers

<AccordionGroup>
  <Accordion title="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
  </Accordion>

  <Accordion title="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
  </Accordion>

  <Accordion title="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
  </Accordion>

  <Accordion title="DigitalOcean">
    **Available Components:**

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

    **Recommended for:**

    * Simple infrastructure
    * Startups and small teams
    * Cost-effective hosting
  </Accordion>
</AccordionGroup>

### Development & CI/CD

<AccordionGroup>
  <Accordion title="GitHub">
    **Available Components:**

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

    **Recommended for:**

    * Development teams
    * CI/CD pipelines
    * Deployment automation
  </Accordion>

  <Accordion title="GitLab">
    **Available Components:**

    * Git Operations
    * API
    * Pages
    * CI/CD Pipelines
    * Container Registry

    **Recommended for:**

    * Self-hosted Git
    * DevOps workflows
    * Enterprise development
  </Accordion>

  <Accordion title="Vercel">
    **Available Components:**

    * Edge Network
    * Build System
    * Serverless Functions
    * Analytics
    * Image Optimization

    **Recommended for:**

    * Frontend deployments
    * Next.js applications
    * Jamstack sites
  </Accordion>

  <Accordion title="Netlify">
    **Available Components:**

    * Build System
    * CDN
    * Functions
    * Forms
    * Identity

    **Recommended for:**

    * Static sites
    * Jamstack applications
    * CI/CD for frontend
  </Accordion>
</AccordionGroup>

### SaaS & Business Tools

<AccordionGroup>
  <Accordion title="Stripe">
    **Available Components:**

    * API
    * Checkout
    * Dashboard
    * Connect
    * Billing
    * Webhooks

    **Recommended for:**

    * Payment processing
    * Subscription billing
    * E-commerce platforms
  </Accordion>

  <Accordion title="Shopify">
    **Available Components:**

    * Storefront
    * Admin API
    * Checkout
    * Payments
    * Apps

    **Recommended for:**

    * E-commerce sites
    * Online stores
    * Retail operations
  </Accordion>

  <Accordion title="Salesforce">
    **Available Components:**

    * Sales Cloud
    * Service Cloud
    * Marketing Cloud
    * API
    * Community Cloud

    **Recommended for:**

    * CRM systems
    * Sales operations
    * Customer service
  </Accordion>
</AccordionGroup>

### Infrastructure & CDN

<AccordionGroup>
  <Accordion title="Cloudflare">
    **Available Components:**

    * DNS
    * CDN
    * SSL/TLS
    * Workers
    * Pages
    * Stream
    * R2 Storage

    **Recommended for:**

    * DNS management
    * DDoS protection
    * Edge computing
  </Accordion>

  <Accordion title="Fastly">
    **Available Components:**

    * CDN
    * Edge Cloud
    * Image Optimizer
    * Next-Gen WAF

    **Recommended for:**

    * High-performance CDN
    * Video streaming
    * Edge computing
  </Accordion>
</AccordionGroup>

### Databases & Data

<AccordionGroup>
  <Accordion title="MongoDB Atlas">
    **Available Components:**

    * Cluster Operations
    * Data API
    * Backup Service
    * Search
    * Charts

    **Recommended for:**

    * NoSQL databases
    * Document storage
    * Cloud databases
  </Accordion>

  <Accordion title="Redis Cloud">
    **Available Components:**

    * Database Operations
    * Pub/Sub
    * JSON
    * Search
    * TimeSeries

    **Recommended for:**

    * Caching layer
    * Session storage
    * Real-time applications
  </Accordion>

  <Accordion title="PlanetScale">
    **Available Components:**

    * Database Operations
    * Branching
    * Insights
    * Deploy Requests

    **Recommended for:**

    * MySQL databases
    * Serverless databases
    * Schema management
  </Accordion>
</AccordionGroup>

### Communication & Collaboration

<AccordionGroup>
  <Accordion title="Slack">
    **Available Components:**

    * Messaging
    * Calls
    * Workspace
    * Apps/Integrations
    * Enterprise Grid

    **Recommended for:**

    * Team communication
    * Integration dependencies
    * Notification delivery
  </Accordion>

  <Accordion title="Discord">
    **Available Components:**

    * API
    * Voice
    * Media Proxy
    * Third-party Networks

    **Recommended for:**

    * Community platforms
    * Gaming applications
    * Real-time chat
  </Accordion>

  <Accordion title="Microsoft Teams">
    **Available Components:**

    * Messaging
    * Calls & Meetings
    * Calendar
    * Apps
    * Admin Center

    **Recommended for:**

    * Enterprise communication
    * Microsoft 365 integration
    * Corporate collaboration
  </Accordion>
</AccordionGroup>

***

## Component Management

### Viewing Component Status

Each component in your Stack displays:

<CardGroup cols={2}>
  <Card title="Current Status" icon="circle-check">
    Real-time status indicator (Operational, Degraded, Critical)
  </Card>

  <Card title="Last Updated" icon="clock">
    Timestamp of the last status check
  </Card>

  <Card title="Uptime Percentage" icon="chart-line">
    Historical uptime over 7/30/90 days
  </Card>

  <Card title="Incident History" icon="history">
    Recent outages and status changes
  </Card>
</CardGroup>

### Removing Components

<Steps>
  <Step title="Open Stack">
    Navigate to your Stack in the dashboard
  </Step>

  <Step title="Find Component">
    Locate the component you want to remove
  </Step>

  <Step title="Click Remove">
    Click the **⋮** menu next to the component and select **"Remove from Stack"**
  </Step>

  <Step title="Confirm">
    Confirm the removal when prompted
  </Step>
</Steps>

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

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

<Steps>
  <Step title="Open Stack Settings">
    Click the **⚙️ Settings** icon in your Stack
  </Step>

  <Step title="Navigate to Groups">
    Go to **"Component Groups"** section
  </Step>

  <Step title="Create Group">
    Click **"Add Group"** and enter:

    * **Group Name** (e.g., "Core Services", "Infrastructure")
    * **Description** (optional)
    * **Collapse by Default** (show/hide components)
  </Step>

  <Step title="Assign Components">
    Drag components into the appropriate groups
  </Step>

  <Step title="Save Changes">
    Click **"Save Groups"**
  </Step>
</Steps>

### 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"**

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

***

## Auto-Adding Components

Automatically add new components when a Source adds them:

### Enabling Auto-Add

<Steps>
  <Step title="Open Stack Settings">
    Navigate to Stack → Settings
  </Step>

  <Step title="Find Auto-Add Section">
    Scroll to **"Auto-Add Components"**
  </Step>

  <Step title="Select Sources">
    Choose which Sources should auto-add new components:

    * ✅ Enable for stable Sources (AWS, GitHub)
    * ❌ Disable for noisy Sources (might add unwanted components)
  </Step>

  <Step title="Save Settings">
    Click **"Save Preferences"**
  </Step>
</Steps>

<Warning>
  **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.
</Warning>

***

## Monitoring Multiple Sources

### Scenario: Full-Stack Application

For a typical web application, you might monitor:

```yaml theme={null}
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

```yaml theme={null}
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

<AccordionGroup>
  <Accordion title="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:**

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

  <Accordion title="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
  </Accordion>

  <Accordion title="Use Descriptive Names">
    **Customize component display names**

    **Generic names:**

    * "API"
    * "Database"
    * "Storage"

    **Descriptive names:**

    * "Production API (us-east-1)"
    * "Customer Database (PostgreSQL)"
    * "User Uploads (S3)"
  </Accordion>

  <Accordion title="Group Related Components">
    **Organize for clarity**

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

      Infrastructure
        - AWS
        - Cloudflare

      Third-Party
        - Stripe
        - SendGrid

    ❌ Poor Grouping:
      Important Stuff
        - Everything
    ```
  </Accordion>

  <Accordion title="Regular Maintenance">
    **Keep your Stack clean**

    Monthly tasks:

    * Remove deprecated components
    * Add newly-integrated services
    * Update component display names
    * Verify grouping still makes sense
    * Check for unused Sources
  </Accordion>
</AccordionGroup>

***

## 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](https://status.statusstack.com)
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

<CardGroup cols={2}>
  <Card title="Custom Monitoring" icon="chart-line" href="/guides/custom-monitoring">
    Monitor your own websites and APIs
  </Card>

  <Card title="Notification Setup" icon="bell" href="/guides/notification-setup">
    Get alerted when services go down
  </Card>

  <Card title="Status Pages" icon="browser" href="/guides/status-pages">
    Customize your public status page
  </Card>

  <Card title="Source Concepts" icon="book" href="/concepts/sources">
    Deep dive into Sources and Components
  </Card>
</CardGroup>