Bitcoin Node Monitoring Tools Compared

Node Monitoring Tools Overview

Running a Bitcoin node without monitoring is like operating a server without logs: you only discover problems after they cause damage. Node monitoring tools provide real-time visibility into block sync status, peer connections, mempool state, and Lightning channel health. The six tools compared here range from turnkey dashboards to full observability stacks.

Each tool takes a different approach. Umbrel and mempool.space focus on Bitcoin layer-one visibility. Ride The Lightning (RTL) and ThunderHub are Lightning node management interfaces with built-in monitoring. LNDg adds automated channel management on top of monitoring. The RaspiBolt stack uses Prometheus and Grafana to build a fully customizable observability platform. The right choice depends on which node implementations you run, whether you need alerting, and how much you value customization over simplicity.

For a deeper comparison of the underlying node software, see our Bitcoin node software comparison and node hardware comparison.

Metrics and Monitoring Capabilities

The metrics each tool exposes determine what you can actually observe about your node. A Bitcoin full node operator primarily cares about block sync status, peer connectivity, and mempool depth. A routing node operator also needs channel balance visibility, forwarding statistics, and HTLC failure tracking.

Tool-by-Tool Breakdown

Umbrel Dashboard

Umbrel provides a polished, browser-based dashboard for Bitcoin Core and LND. It displays blockchain sync progress, active peer connections, mempool size, blockchain storage usage, and system resource consumption (CPU, RAM, disk, temperature). The dashboard is designed for simplicity: no configuration required beyond the initial node setup.

Umbrel does not include built-in alerting, but its app store offers third-party notification tools. WoofBot sends Telegram alerts for payments, confirmed transactions, and new blocks. Uptime Kuma provides self-hosted uptime monitoring with webhook and Telegram support. Minimum hardware is a dual-core CPU with 4 GB RAM (8 GB recommended) and a 1 TB SSD.

RaspiBolt Monitoring Stack

The RaspiBolt guide documents a full Prometheus and Grafana stack purpose-built for Bitcoin and Lightning monitoring. The data pipeline uses dedicated exporters: bitcoin-prometheus-exporter scrapes Bitcoin Core RPC for blockchain metrics, lndmon (from Lightning Labs) connects to LND via gRPC for channel and routing data, and Node Exporter collects system hardware metrics. Prometheus stores the time-series data, and Grafana renders customizable dashboards with pre-built templates.

The key advantage of this approach is Grafana's native alerting engine. You can configure threshold-based alerts for any metric: disk usage above 80%, peer count dropping below a minimum, channels going inactive, or block sync falling behind. Alert notifications support Telegram, email, Slack, Discord, and webhooks. The stack runs on a Raspberry Pi 4 (8 GB recommended) or any Linux x86 system. For Core Lightning users, the CLN Prometheus plugin provides equivalent channel metrics.

Ride The Lightning (RTL)

RTL (v0.15.9-beta, July 2025) is a web-based node management interface that supports all three major Lightning implementations: LND, Core Lightning (via CLNRest), and Eclair. This is the only tool in this comparison with Eclair support. RTL shows on-chain and Lightning balances, channel capacity with local and remote balance breakdowns, forwarding history, and routing peer summaries.

RTL focuses on management rather than monitoring: it excels at channel operations (open, close, rebalance) and payment workflows. It does not track Bitcoin Core metrics like block height or mempool state, and it has no built-in alerting. RTL runs as a lightweight Node.js application and is available as a pre-installed app on Umbrel, myNode, RaspiBlitz, and Start9.

ThunderHub

ThunderHub (v0.18.4, May 2026) is an LND-focused management dashboard with a polished UI. It provides liquidity reports showing total local and remote balances across all channels, forwarded payment graphs, UTXO management, and batch channel opens. Recent versions added Taproot Assets support (v0.16.0) and circular rebalancing (v0.18.0).

ThunderHub supports LND only: no CLN or Eclair. It does not monitor Bitcoin Core directly, and it has no built-in alerting. It offers both admin and view-only access modes, which is useful for operators who want to share read access without exposing management capabilities. Connection options include HEX/Base64 macaroons, LNDConnect URLs, and BTCPayServer integration.

mempool.space (Self-Hosted)

Self-hosting mempool.space (v3.3.1, April 2025) gives you a private block explorer with the same real-time mempool visualization available on the public site. It displays fee rate distributions, projected block confirmation times, mining pool statistics, and a full transaction and address explorer. Optional modules add Lightning Network topology views and Liquid Network support.

The backend requires Bitcoin Core with txindex=1 enabled, and optionally an Electrum server (mempool/electrs or Fulcrum) for address lookups. Resource requirements are heavier than the other tools: 16 GB RAM is recommended for full indexing, and fast SSD or NVMe storage is critical for performance. mempool.space has no built-in alerting, though third-party bots can query the API for fee threshold notifications. It is available as a one-click install on Umbrel, RaspiBlitz, Start9, and myNode.

LNDg

LNDg (v1.11.0, July 2026) is unique among these tools: it combines monitoring with automated channel management. The dashboard tracks channel performance, forwarding revenue, HTLC failure streams, and peer online/offline status. Its automation engine handles circular rebalancing, dynamic fee adjustment based on channel utilization, and automatic peer reconnection for inactive channels.

LNDg supports LND only. It does not monitor Bitcoin Core metrics, and it has no built-in alerting beyond a suggestions engine that recommends fee adjustments and rebalancing actions. It runs as a Python application with Docker support and is compatible with Umbrel, Start9, and RaspiBlitz. For operators running routing nodes on LND, LNDg's automation features save significant manual effort.

Prometheus and Grafana: Building a Custom Stack

For operators who want full control over their monitoring, the Prometheus and Grafana combination provides the most flexibility. The architecture is modular: each component of your node stack gets its own exporter, Prometheus scrapes metrics at configurable intervals, and Grafana provides dashboards and alerting.

Available exporters for the Bitcoin stack:

• Node Exporter: system metrics including CPU, RAM, disk I/O, network bandwidth, and temperature
• bitcoin-prometheus-exporter (jvstein): block height, chain difficulty, blockchain size, peer count, mempool depth, network hashrate
• lndmon (Lightning Labs): channel balances, routing fees, HTLC statistics, graph node and edge counts, wallet UTXOs
• CLN Prometheus plugin: channel fund allocations, spendable balances, unresolved HTLCs, on-chain output funds

This approach requires more setup than turnkey dashboards, but it scales to any number of nodes and metrics. Pre-built Grafana dashboard templates for Bitcoin and Lightning nodes are available on the Grafana community dashboards site.

Self-Hosted vs Third-Party Monitoring

The choice between self-hosted and third-party monitoring has direct implications for privacy. Every query you send to a public block explorer or API reveals information about which addresses, transactions, and UTXOs you care about. Over time, a third-party service can correlate your IP address with your on-chain activity and build a profile of your holdings.

Self-hosting mempool.space or running your own Electrum server ensures that address lookups, fee estimates, and transaction broadcasts stay local. Your full node validates everything independently, and no external service sees your queries. This matters especially for Lightning node operators, where channel opens and closes are visible on-chain and can be linked to your node's public key if observed by the same entity that serves your block explorer queries.

For operators who use a mix of self-hosted and external services, running node traffic over Tor adds IP-level anonymity. Compact block filters (BIP 157/158) provide another privacy layer when connecting to untrusted peers. The general principle: use self-hosted tools for anything involving your own addresses and transactions, and reserve public APIs for non-sensitive lookups like general fee estimates or block statistics.

How to Choose a Monitoring Setup

The right monitoring setup depends on your node type and operational goals:

Bitcoin-only full node with minimal overhead: Umbrel provides the easiest setup with block sync, peer, and system metrics out of the box. Add self-hosted mempool.space for detailed mempool visualization and fee estimation.

LND routing node focused on revenue: combine ThunderHub or RTL for channel management with LNDg for automated rebalancing and fee optimization. Add the RaspiBolt Prometheus stack if you need historical metrics and alerting.

Core Lightning node: RTL is the primary management interface with CLN support. For monitoring, the CLN Prometheus plugin feeds directly into a Grafana stack. ThunderHub and LNDg are not options for CLN operators.

Multi-node operator needing alerts: the Prometheus and Grafana stack is the only option with production-grade alerting. Configure Telegram or Slack notifications for disk usage thresholds, channel inactivity, peer drops, and sync failures. No other tool in this comparison offers equivalent alerting without third-party add-ons.

Privacy-focused operator: self-host mempool.space, run your own Electrum server, and route all traffic through Tor. Avoid any monitoring setup that queries external APIs with your addresses or transaction data.

Many operators run multiple tools simultaneously. A common setup pairs Umbrel (for system overview) with RTL or ThunderHub (for Lightning management), mempool.space (for mempool visibility), and LNDg (for automation). For hardware guidance on running these tools alongside your node, see our node hardware comparison.

Monitoring Lightning Nodes on Spark

Operators running Lightning infrastructure alongside Spark benefit from the same monitoring principles. Spark extends Bitcoin with off-chain capabilities, and tracking channel balances, routing fees, and peer connectivity remains essential regardless of which layer-two protocol carries the traffic. The Prometheus and Grafana stack is protocol-agnostic: any service that exposes metrics via an HTTP endpoint can be scraped and visualized alongside your Bitcoin Core and Lightning data. For a broader comparison of Lightning node options, see our Lightning node comparison tool.

Frequently Asked Questions

What is the best way to monitor a Bitcoin full node?

For most home node operators, Umbrel provides sufficient monitoring with zero configuration: it tracks block sync, peer count, mempool size, and system resources. For operators who need alerting or historical time-series data, the Prometheus and Grafana stack (as documented in the RaspiBolt guide) offers the most comprehensive approach. Adding a self-hosted mempool.space instance provides detailed mempool visualization and fee estimation powered by your own node.

Can I monitor both Bitcoin Core and a Lightning node from one dashboard?

Yes, but only the RaspiBolt Prometheus and Grafana stack supports this natively. It uses separate exporters for Bitcoin Core (bitcoin-prometheus-exporter), Lightning (lndmon for LND or the CLN Prometheus plugin), and system hardware (Node Exporter), all feeding into a single Grafana dashboard. The other tools in this comparison focus on either Bitcoin Core or Lightning, not both.

Which node monitoring tool supports Core Lightning?

Ride The Lightning (RTL) supports Core Lightning via CLNRest, alongside LND and Eclair. For dedicated monitoring metrics, the CLN Prometheus plugin exposes channel allocations, spendable funds, and HTLC data to Prometheus. ThunderHub, LNDg, and the Umbrel Lightning dashboard support LND only.

Do any Bitcoin node monitoring tools have built-in alerts?

Among the tools compared here, only the Grafana-based stack (used in the RaspiBolt setup) has native alerting. Grafana supports threshold-based alerts with notifications to Telegram, email, Slack, Discord, and webhooks. Umbrel can add alerting through third-party apps like WoofBot (Telegram) and Uptime Kuma. RTL, ThunderHub, LNDg, and mempool.space have no built-in alerting.

Is it safe to use public block explorers to monitor my node?

Public block explorers like mempool.space can reveal which addresses and transactions you are interested in. Over time, this metadata can be correlated with your IP address to build a profile of your on-chain activity. For privacy-sensitive monitoring, self-host mempool.space and run your own Electrum server. Use public APIs only for non-sensitive queries like general fee estimation or block statistics.

What hardware do I need to run a monitoring stack?

Umbrel, RTL, ThunderHub, and LNDg run comfortably on a Raspberry Pi 4 with 4 to 8 GB of RAM alongside your node software. The Prometheus and Grafana stack adds moderate overhead: plan for 8 GB RAM minimum on a Raspberry Pi. Self-hosted mempool.space with full indexing is the most resource-intensive option, recommending 16 GB RAM and fast NVMe storage. See our hardware comparison for detailed specs.

Can LNDg automatically manage my Lightning channel fees?

Yes. LNDg includes an auto-fee engine that dynamically adjusts routing fees based on channel utilization and performance. It prefers lower fees for larger channels to attract volume, matches high fees for channels connected to high-fee peers, and discounts channels with heavy local-side balances to encourage outbound flow. It also handles circular rebalancing automatically.

This tool is for informational purposes only and does not constitute financial advice. Software versions, features, and resource requirements change frequently. Always verify current capabilities on each project's official GitHub repository before making infrastructure decisions.