Skip to content

Access dashboards and isolate listeners

Access the dashboard from a workstation

Keep Grafana and Prometheus on router-side listeners and reach them through the deployment SSH path.

Run the tunnel command from the management checkout with the workstation .env loaded.

Reuse the Gate G tunnel when it is running with the monitoring forwards. For monitoring access by itself, open:

python3 tools/deployment/deploy_hosts.py tunnel --role router \
  --forward 13000:3000 --forward 19090:9090

Keep that terminal running while using the monitoring interfaces.

Open:

  • Grafana: http://127.0.0.1:13000/d/narwhal-router/narwhal-orchestrator
  • Prometheus: http://127.0.0.1:19090

Grafana permits anonymous Viewer access through the local tunnel.

If a deployment exposes Prometheus or Grafana through another route, apply that deployment's existing ingress, authentication, and TLS policy.

The dashboard reference documents router and engine scope selection.

Isolate a second monitoring deployment

When another monitoring deployment shares the router host, assign distinct loopback listeners:

NARWHAL_GRAFANA_BIND_ADDRESS=127.0.0.2 \
NARWHAL_PROMETHEUS_LISTEN_ADDRESS=127.0.0.2:19090 \
make observe

Grafana derives its Prometheus datasource URL from the selected listener. With a wildcard Prometheus bind, Narwhal points Grafana and readiness probes at loopback while the Prometheus socket keeps its configured wildcard address.

For the isolated listeners on 127.0.0.2, open the workstation tunnel with:

python3 tools/deployment/deploy_hosts.py tunnel --role router \
  --remote-address 127.0.0.2 \
  --forward 13000:3000 --forward 19090:19090

Review GPU telemetry, alerts, and recovery after confirming dashboard access.