Skip to main content

Dependency Monitors

Dependency monitors track third-party services and APIs that your application relies on. Know when Stripe, Shopify, AWS, or any external service experiences issues.

Identify root causes: Know whether an issue is your fault or a third-party problem
  • Communicate proactively: Alert customers before they report issues
  • Track reliability: Build a history of third-party uptime for vendor discussions
  • 39 Supported Integrations

    FlareWarden auto-detects and integrates with 39 status page providers and cloud infrastructure dashboards including Atlassian StatusPage, AWS, Azure, GCP, and more. Just paste a URL and we handle the rest.

    Browse all integrations

    Common Dependencies to Monitor

    Popular third-party services worth tracking

    Payment Processors

    • Stripe
    • PayPal
    • Square

    E-commerce

    • Shopify
    • WooCommerce
    • BigCommerce

    Email Services

    • SendGrid
    • Mailchimp
    • Resend

    Cloud Providers

    • AWS
    • Google Cloud
    • Azure

    CDN & Performance

    • Cloudflare
    • Fastly
    • Akamai

    APIs & Integrations

    • Twilio
    • Auth0
    • Algolia

    Configuration Options

    Settings for dependency monitoring

    Endpoint URL

    The URL to monitor. Many services offer status or health check endpoints:

    https://status.stripe.com
    https://api.example.com/health
    https://status.aws.amazon.com/rss/ec2-us-east-1.rss

    Expected Content (Optional)

    Optionally verify the response contains specific text. Uses the same matching options as content monitors:

    • None: Only check if the endpoint responds
    • Contains: Verify specific text is present
    • Not Contains: Alert if specific text appears

    Severity Level

    How dependency failures affect your parent monitor:

    Critical: Dependency failure marks the parent monitor as DOWN
    Degraded: Dependency failure marks the parent monitor as DEGRADED

    Ownership

    Mark whether you own/control this dependency or if it's a third-party service. This helps with reporting and root cause analysis.

    How Dependency Monitoring Works

    Understanding the dependency check workflow

    1

    Attach to Parent Monitor

    Dependencies are linked to an uptime monitor (the "parent")

    2

    Independent Checks

    Dependencies are checked on the same schedule as their parent

    3

    Status Aggregation

    Dependency failures can affect the parent's status based on severity

    4

    Separate Incidents

    Dependency failures create their own incidents for clear tracking

    Best Practices

    Tips for effective dependency monitoring

    • Use official status endpoints

      Most services offer status pages or health endpoints. Check their documentation.

    • Set appropriate severity

      Use Critical for payment processors, Degraded for non-essential services.

    • Group related dependencies

      Attach all related dependencies to the appropriate parent monitor for a complete view.