Skip to content

feat(deploy): collect metrics from linode chain and miner machines#4

Open
kacper-wolkiewicz-reef wants to merge 1 commit into
masterfrom
add-linode-chain-miner-metrics
Open

feat(deploy): collect metrics from linode chain and miner machines#4
kacper-wolkiewicz-reef wants to merge 1 commit into
masterfrom
add-linode-chain-miner-metrics

Conversation

@kacper-wolkiewicz-reef

Copy link
Copy Markdown
Collaborator

Add cadvisor and node-exporter to the Linode chain and miner compose files, bound to each machine's VLAN IP (never the public interface), and wire the validator's Prometheus to scrape them over the VLAN via new, gated CHAIN_METRICS_HOST / MINER_METRICS_HOST env vars. When unset (generic prod), the scrape config is byte-identical to before, so only Linode validators pick up the extra chain/miner jobs. Metrics from all three machines then flow through the validator's existing remote-write.

Document the new exporters, the validator .env additions, and the firewall ports (8080 + 9100 inbound on chain/miner from the validator IP).

Add cadvisor and node-exporter to the Linode chain and miner compose files,
exposed publicly on :8080 / :9100 so a separate, external Prometheus (run
elsewhere) can scrape them. The validator keeps its own Prometheus from the
standard prod stack and is left completely unchanged - it does not scrape the
chain or miner.

Document the public endpoints and the Cloud Firewall rules that must restrict
:8080 + :9100 to the external Prometheus's IP, since cadvisor and
node-exporter are unauthenticated.
@kacper-wolkiewicz-reef kacper-wolkiewicz-reef force-pushed the add-linode-chain-miner-metrics branch from 9ace0f3 to 255c2d2 Compare July 3, 2026 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant