NotifyBC
Home
Docs
Help
GitHub
Home
Docs
Help
GitHub
  • Getting Started

    • Welcome
    • Overview
    • Quick Start
    • Installation
    • Web Console
    • What's New
  • Configuration

    • Configuration Overview
    • Database
    • Admin IP List
    • Reverse Proxy IP Lists
    • HTTP Host
    • Internal HTTP Host
    • Email
    • SMS
    • Subscription
    • Notification
    • Node Roles
    • Cron Jobs
    • RSA Keys
    • Worker Process Count
    • Middleware
    • OIDC
    • TLS Certificates
    • Queue
    • Logging
  • API

    • API Overview
    • Subscription
    • Notification
    • Configuration
    • Administrator
    • Bounce
  • Miscellaneous

    • Health Check
    • Disaster Recovery
    • Memory Dump
    • Benchmarks
    • Bulk Import
    • Developer Notes
    • Upgrade Guide
  • Meta

    • Code of Conduct
    • Security Reporting
    • Acknowledgments

Health Check

Health status of NotifyBC can be obtained by querying /health API end point. For example

$ curl -s http://localhost:3000/api/health | jq
{
  "status": "ok",
  "info": {
    "MongoDB": {
      "status": "up"
    },
    "config": {
      "status": "up",
      "count": 2
    },
    "redis": {
      "status": "up"
    }
  },
  "error": {},
  "details": {
    "MongoDB": {
      "status": "up"
    },
    "config": {
      "status": "up",
      "count": 2
    },
    "redis": {
      "status": "up"
    }
  }
}

If overall health status is OK, the HTTP response code is 200, otherwise 503. The response payload shows status of following indicators and health criteria

  1. MongoDB - MongoDB must be reachable
  2. config - There must be at least 2 items in MongoDB configuration collection
  3. Redis - Redis must be reachable

/health API end point is also reachable in API Explorer of NotifyBC web console.

Prev
Bounce
Next
Disaster Recovery