Skip to content

feat(app): wire the monitoring API into pluto run#539

Open
iamquang95 wants to merge 2 commits into
emlautarom1/app-wiringfrom
feat/monitoring-api
Open

feat(app): wire the monitoring API into pluto run#539
iamquang95 wants to merge 2 commits into
emlautarom1/app-wiringfrom
feat/monitoring-api

Conversation

@iamquang95

Copy link
Copy Markdown
Collaborator

Stack on #536

Wires the (already-ported) monitoringapi and health modules into the running node, so pluto run serves the monitoring API on --monitoring-address (default 127.0.0.1:3620):

  • GET /metrics — Prometheus/OpenMetrics scrape of the global vise registry
  • GET /livez — liveness
  • GET /readyz — readiness, backed by a background checker (beacon-node sync/peers/version, quorum peer connectivity, validator-client activity)

It also starts the health checker (app_health_checks). The CLI run bridge now honors --monitoring-address (previously accepted but ignored).

Readiness's "validators seen" signal is fed from the validator API: validatorapi::Component gains a pubkey observer invoked at the share↔root translation points, collected into a bounded, deduped set that the checker drains each slot.

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