Watching blockchain nodes from the outside in

Custom exporters, Prometheus and Grafana over a node management platform, covering endpoint health and resource use on every node.

Talk to an engineer DevOps

Blockchain infrastructure Client

DevOps Practice

July 2024 Published

01 — The challenge

Where it started.

The platform’s whole service is the condition of its customers’ blockchain nodes: endpoint health, status visible in real time, and CPU, memory and disk read early enough to act on.

Off-the-shelf monitoring does not know what a healthy node looks like, so the signals that matter were the ones not being collected.

02 — What we built

The work itself.

Decide the metrics first. The key metrics identified and a collection and visualisation strategy agreed before anything was built.

Custom exporters. Exporters written for the signals that general-purpose monitoring does not expose, feeding Prometheus.

Across every node. The exporters deployed fleet-wide with the Prometheus and Grafana infrastructure behind them.

Tuned on what it showed. Performance watched after rollout and the solution revised against observed behaviour rather than left at version one.

03 — Results

What the client has now.

Node status and performance visible in real time, to the platform’s team and to its customers. Downtime reduced by alerting on conditions early rather than on failure. Resource use measured well enough to manage capacity against it. Support answered with evidence, which is what the customers were paying for.

The rest of this study

What we built, what it produced, and the stack behind it.

We share the whole write-up — we would just like to know who is reading. One form opens every case study on the site for the next 30 days.

If this is your problem too

Start with a fixed-price pilot.

Two weeks on a real piece of your backlog, priced before we begin. You keep the output whether or not you continue.

Related work

Health insurance · CI/CD

From a three-hour deployment to ten minutes

Identity management · Observability