The server.health subscription is the preferred way to monitor blockd health — events are pushed at a configurable interval with no polling required.

For the complete health response schema, field reference, state tables, IBD fields, and ZMQ monitoring documentation, see Health & IBD Reference.

---

server.health

{
  "subscriptions": [
    {
      "subscribe": "server.health",
      "args": {
        "interval": 30,
        "tip": true,
        "detailed": true
      }
    }
  ]
}

Subscription args:

Arg	Type	Default	Description
interval	integer	30	Emit frequency in seconds
tip	bool	false	Include current block tip in events
detailed	bool	false	Include bitcoind and indexer status in events

---

server_health event

The server_health event carries the same data as GET /health/{level}. The event field identifies the message type:

{
  "event": "server_health",
  "time": 1771612931,
  "up_since": 1771612819,
  "state": "ready",
  "ready_at": 1771612824,
  "tracking_since": 1771612824
}

tip and ibd fields are added when present. core and indexer objects are added when detailed: true is set. See Health & IBD Reference for the complete response shape and all optional fields.

---

Recommended intervals

Use a short interval during IBD to drive smooth progress updates:

{
  "subscriptions": [
    {
      "subscribe": "server.health",
      "args": {
        "interval": 5,
        "tip": true,
        "detailed": true
      }
    }
  ]
}

Use a longer interval for ongoing node monitoring:

{
  "subscriptions": [
    {
      "subscribe": "server.health",
      "args": {
        "interval": 30,
        "tip": true,
        "detailed": true
      }
    }
  ]
}