Nitro

Node monitoring

Enable the Nitro metrics server, scrape Prometheus metrics, monitor key metrics, and run health checks

Request an update

Nitro exposes Prometheus-compatible metrics through a dedicated metrics server. Each Nitro binary reports its health through its own mechanism.

Metrics server

Enable the metrics server

Pass the --metrics flag when you start the node. Configure the server with these flags:

FlagDefaultDescription
--metrics-server.addr127.0.0.1Listen address for the metrics server
--metrics-server.port6070Listen port for the metrics server
--metrics-server.update-interval3sHow often Nitro refreshes internal metrics

Example:

nitro --metrics \
  --metrics-server.addr 0.0.0.0 \
  --metrics-server.port 6070

Prometheus scrape endpoint

After you enable metrics, Nitro exposes a Prometheus-compatible endpoint at:

http://<metrics-server.addr>:<metrics-server.port>/debug/metrics/prometheus

pprof runs as a separate server at /debug/pprof/ for CPU and memory profiling. Enable it with --pprof, and configure it with --pprof-cfg.addr and --pprof-cfg.port (default 127.0.0.1:6071). The metrics port does not serve pprof.

Key metrics to monitor

Group your alerts by concern. The metric names below are Nitro's Prometheus metric names.

ConcernMetricWhat it tells you
Memorycontainer_memory_rssActual container RSS (resident memory). Alert on this, not Go heap. Most Nitro memory is invisible to Go.
Sequencer feedarb_feed_backlog_messagesMessages in the feed backlog. A growing backlog means the is not posting message batches to the .
Sequencingarb_sequencer_backlogBacklog at the . Sustained growth means the sequencer can't keep up with load.
Batch postingarb_batchposter_wallet_ethBatch poster wallet balance. If the wallet runs dry, batches stop posting.
Batch postingarb_batchposter_suggestedtipcapSuggested tip cap the batch poster pays. It tracks parent chain fee pressure.
RPC protectionarb_rpc_limitcheck_failureIncrements when the memory free-limit throttle rejects an RPC call (HTTP 429).
Tip

Always alert on container_memory_rss, not Go heap metrics. Most of Nitro's memory is invisible to Go's runtime. To learn why, see Memory allocators in Nitro.

Health checks

Each Nitro component exposes health information through a mechanism specific to its binary.

Main Nitro node

The main nitro binary does not expose a dedicated /health endpoint. Infer node health from RPC availability. If the HTTP RPC port (default 8547) returns HTTP 200 for a valid JSON-RPC request, the node is healthy.

Example liveness check:

curl -sf -X POST http://localhost:8547 \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_chainId","params":[],"id":1}'

Auxiliary components

  • filterer: Exposes a /liveness endpoint for health checks.
  • DA server: Exposes a /health endpoint.

Kubernetes

If you run Nitro on Kubernetes, the community Helm chart sets up the ServiceMonitor, startup and liveness probes, and a Grafana dashboard for you. To enable metrics scraping and configure probes on Kubernetes, see Enable monitoring and Probes in the Helm guide.

How is this guide?

On this page