Files
zeekay 7cf87b230b node-unified is the node
The module already called itself github.com/luxfi/node while containing no node
in Go: cmd/luxd was twenty-one lines that printed the size of a few types, and
the Go column of the matrix measured a VM plugin. A repo that fetches the thing
it claims to be has not replaced it, so the Go sources move in — 1515 files,
the daemon and everything under it — and the build reaches outside this module
for nothing.

Rust and C++ sit beside it unchanged and are still measured against it by the
differential. That is the point of one repo: the reference implementation and
the two ports are the same checkout, so parity is a thing you can run rather
than a thing you assert.

Verified: builds, and the closure carries no lux-private — checked at build time
rather than believed. The daemon starts twelve chains on a local network
(P X C Q Z A B G K M F, plus D through its plugin) and reports healthy.
2026-09-07 16:15:25 -07:00

717 B

The Metrics API allows clients to get statistics about a node's health and performance.

This API set is for a specific node, it is unavailable on the [public server](https://docs.lux.network/docs/tooling/rpc-providers).

Endpoint

/v1/metrics

Usage

To get the node metrics:

curl -X POST 127.0.0.1:9630/v1/metrics

Format

This API produces Prometheus compatible metrics. See here for information on Prometheus' formatting.

Here is a tutorial that shows how to set up Prometheus and Grafana to monitor Lux Node using the Metrics API.