1
Baseline captured
Store the active server before the public fallback demo recycles its pod.
Public demo route
ClubCRM failover monitor
This page is intended for the networking demo iframe. It stays public, polls the live app every two seconds, and shows the current browser entry pod plus the API upstream pod and node.
No login required
Audience screen
Follow ClubCRM traffic as it fails over to a healthy replacement server
This public page turns live routing snapshots into a presentation-first failover story. The presenter console is the canonical place to run the server restart demo; this button remains available as a faster pod-recycle rehearsal path.
API connectedLive snapshots
ReadyClient-side run state
0.0.0.0
The audience screen is ready for a guided failover story.
Use this route to rehearse the public narrative. For the real networking presentation, start the canonical server failover from the monitor dashboard and leave this screen projected for the audience.
Current route
0.0.0.0
Pod 0.0.0.0
- Baseline server
- Waiting
- Current server
- 0.0.0.0
- API status
- Connected
- Failover timer
- Standing by
Will lock when the rehearsal starts.
Pod 0.0.0.0
http://api:8000/health
Starts when you trigger the pod recycle run.
2
Failover triggered
This audience route can run a fallback pod recycle demo. Use the monitor dashboard for the full server failover presentation path.
3
Disruption observed
The screen will call out any reconnect or API disruption during the run.
4
Recovery confirmed
The run finishes once the browser route lands on a different server.
Browser entry server
0.0.0.0
Pod 0.0.0.0
This is the server and pod the public route is currently reaching. The server label is the primary audience signal; pod details stay here as supporting evidence.
- Service
- clubcrm-web
- Instance
- 0.0.0.0
- Namespace
- Unavailable
- Node / VM
- Unavailable
API upstream server
677ae244ef28
Pod 677ae244ef28
Reference signal only. This shows the API runtime behind the health endpoint. Status: ok • http://api:8000/health
- Service
- clubcrm-api
- Instance
- 677ae244ef28
- Namespace
- Unavailable
- Node / VM
- Unavailable
Run status
Ready to start
Nothing is running yet. Starting this fallback path captures the current server, recycles the active pod, and watches for the route to recover.
Observed changes
0 logged
Start the fallback pod recycle demo to capture a baseline and begin watching the route.