Public Dashboards
Public dashboards expose selected performance and reliability metrics without authentication.
What a dashboard includes
Section titled “What a dashboard includes”Per configured chain/dashboard:
- selected suites
- selected endpoints
- uptime and latency trend views
- incident-relevant status history
Shared URLs are in the form /p/:shareToken.
What stays private
Section titled “What stays private”Public dashboards do not expose:
- endpoint secret/auth credentials
- full internal endpoint URLs
- tenant settings or private metadata
Typical use cases
Section titled “Typical use cases”Public dashboards serve several purposes:
- infrastructure provider status transparency
- chain team external reliability page
- partner-facing SLO reporting
Setup flow
Section titled “Setup flow”- Open Public Status Pages (
/chains/:chainId/status-pages). - Click Create Dashboard .
- Select endpoint and suite scope.
- Review preview.
- Publish and share token URL.
Operational guidance
Section titled “Operational guidance”Keep published dashboards clean and secure:
- include only production-relevant suites
- document dashboard intent for external viewers
- rotate/revoke share token if accidentally over-shared
Suggested layout policy
Section titled “Suggested layout policy”Structure dashboards for quick readability:
- top section: current status summary
- middle section: latency trends (p50/p95/p99)
- bottom section: recent incidents and recoveries
Keep dashboard scope narrow enough that readers can answer “Is RPC healthy right now?” quickly.
Audience-specific dashboards
Section titled “Audience-specific dashboards”Create separate dashboards tailored to different audiences:
- Partners: selected endpoints used by partner traffic
- Public status page: highest-level service health only
- Internal mirror: broader endpoint set for non-public sharing
Incident communication workflow
Section titled “Incident communication workflow”- detect degradation from suite runs
- validate issue in authenticated run detail pages
- post incident note in external communication channel
- keep dashboard updated with current status
- send recovery note after metrics normalize
Privacy review checklist
Section titled “Privacy review checklist”Before publishing, confirm the following:
- verify endpoint identifiers are non-sensitive
- verify no authentication headers are exposed
- verify dashboard title/description avoid internal-only details
- verify selected suite names are safe for external visibility
Common mistakes
Section titled “Common mistakes”Avoid these pitfalls:
- sharing dashboards that include staging endpoints
- publishing before validating suite quality and schedule stability
- not rotating share tokens after broad distribution