Mashdun
AI GrowthWorkCapabilitiesIntegrationsProcessLabsMarketplaceBlogAbout
Get in Touch
Mashdun

Full-stack web developer, AI engineer & growth marketer. Building production-grade apps and intelligent solutions.

Navigation

  • Portfolio
  • Capabilities
  • Process
  • Labs
  • About

Resources

  • Blog / Notes
  • Marketplace
  • Contact
  • RSS Feed

Legal

  • Terms of Service
  • Privacy Policy
  • Cookie Policy
  • Do Not Sell or Share
  • Delete my data

© 2026 Mashdun. All rights reserved.

Built with Next.js, Tailwind CSS & Prisma

    All Labs
    Product
    Health Checks
    Uptime
    Alerting
    SRE

    System Health Board

    Recreated from a production system-health page: live dependency probes (DB, storage, cache) with latency, config-presence integration checks, an overall status only live failures can drop, and an incident log with a 60-minute per-source alert throttle so a flapping dependency can't spam on-call. Hit 'Simulate incident' to trip a fault.

    System Health Board

    Live Probes
    Degraded vs Down
    Alert Throttling
    Uptime Endpoint

    System operational

    3 live probes · 4 integrations

    Database (Postgres)

    Connected

    75msOK

    Object storage

    Connected

    249msOK

    Cache (Redis)

    Connected

    8msOK

    OpenAI (LLM + images)

    Key configured

    configOK

    ElevenLabs (voice)

    Key configured

    configOK

    OpenRouter (LLM + video)

    Key configured

    configOK

    Resend (email)

    Key configured

    configOK

    Incident log60-min per-source alert throttle

    No incidents. Hit "Simulate incident" a few times — every third one trips a live fault.

    How it works

    1. Live probes actually ping (DB, storage, cache) and report latency; integrations are config-presence checks
    2. Overall status only drops on a LIVE failure — an unconfigured integration reads 'off', not 'down'
    3. Incidents record per-source with a 60-min alert throttle so a flapping dependency can't spam on-call
    4. A public /api/health endpoint returns the same probes (200 ok / 503 down) for external monitors

    From real client work

    Recreated from the system-health page shipped in a production field-service platform. The key discipline: monitoring must never take down what it monitors, and config presence is not health — a missing API key is a feature toggle, not an outage. Hit 'Simulate incident' a few times to trip a live fault and watch the throttled alert log.

    More dashboard modules