Summary
I built a standalone community tool for Arc node operators:
- local CLI health monitor
- public remote node checker by IP/hostname
- JSON and Discord-friendly output
- Prometheus textfile export
- Grafana dashboard starter
- conservative Prometheus alert rules
- Telegram alerting examples
- self-hostable Telegram checker bot
- operator docs for local monitoring and optional public endpoint checks
Live checker:
https://arc-health.everstead.site
Repository:
https://github.com/Bela1401/arc-node-health-monitor
Why this may help
It turns common Arc node support checks into repeatable tooling:
- RPC reachability and latency
- Arc Testnet chain ID check
- latest block height
- block progression tracking
- EL and CL metrics endpoint reachability
- public port checks for intentionally exposed endpoints
- suggested fixes for common operator issues
Security model
- blocks private, loopback, link-local, and reserved targets by default
- disables redirect following
- enforces request timeouts
- reads bounded metrics response prefixes
- does not require or probe Engine API port
8551
- documents public metrics as optional
- explains that private/local endpoints may appear unreachable from the public checker even when the node is healthy locally
Current positioning
This is an independent community tool, not an official Arc component.
It is designed to complement the existing Arc node docs and operator workflows. It does not change Arc protocol behavior.
Request for maintainer feedback
Would the Arc team prefer this to remain a standalone community tool, or would a small docs reference PR be useful after review?
If a docs reference would be useful, I can open a minimal PR that links to the tool and explains the security model without duplicating the existing monitoring documentation.
Summary
I built a standalone community tool for Arc node operators:
Live checker:
https://arc-health.everstead.site
Repository:
https://github.com/Bela1401/arc-node-health-monitor
Why this may help
It turns common Arc node support checks into repeatable tooling:
Security model
8551Current positioning
This is an independent community tool, not an official Arc component.
It is designed to complement the existing Arc node docs and operator workflows. It does not change Arc protocol behavior.
Request for maintainer feedback
Would the Arc team prefer this to remain a standalone community tool, or would a small docs reference PR be useful after review?
If a docs reference would be useful, I can open a minimal PR that links to the tool and explains the security model without duplicating the existing monitoring documentation.