http://localhost:4000/dashboard for the public profile, or /dashboard/{profile} for another configured file profile. Protect the dashboard with a private network boundary or reverse-proxy authentication when reachable by untrusted clients; RPC Core has no built-in client authentication.
The dashboard shows provider connectivity, circuit state, block freshness, recent routing activity, and a browser request tester. The tester makes real upstream requests. Its counters describe that browser’s run, while provider measurements describe observed upstream attempts. A single client request may produce multiple attempts during failover. Missing observations should be read as unavailable, not zero.
In a cluster, the dashboard can aggregate observations from responding nodes and display coverage. Each node still makes its own routing decisions using its local measurements. A partial or stale aggregate is not proof that every node has the same provider view. See clustering for discovery requirements and metrics and telemetry for measurement units.
System metrics are disabled by default; set LASSO_VM_METRICS_ENABLED=true to collect and display VM metrics. For programmatic node-local measurements use the metrics API. For implementation details see the released observability reference.