FEED OPERATIONS
Keep the feed under control.
Watch resource use and choose when background updates run.
Admin sign in
Use your separate admin password. The client API key does not grant admin access.
Checking feed status
KAFKA
—
Compressed payload processed after initial load
- Payload received
- —
- Subscription demand
- —
- Records behind
- —
- On-demand HTTPS snapshots
- —
- Listed fixtures
- —
- Awaiting metadata
- —
Kafka counters exclude initialization and network overhead. HTTPS count excludes initial SDK snapshots.
BRIDGE CONTAINER
—
Memory used / container limit
- CPU · 100% = one core
- —
- Network incoming
- —
- Received since container start
- —
- Java heap
- —
Network includes Kafka, HTTPS and client traffic. It is not a billing counter.
HETZNER HOST
Unavailable
Waiting for host monitoring
- CPU usage
- —
- Network incoming
- —
- Network outgoing
- —
- Last sample
- —
Host totals include other applications on the server.
Refresh and throttling
What these controls do
- Last completed refresh
- —
- Next scheduled refresh
- —
- Current settings
- —
Periodic refreshes catch up on messages received since the last cycle. They batch traffic rather than remove the accumulated Kafka data.
During idle periods, fixtures are cached and may be out of date. Match detail requests can fetch a current HTTPS snapshot without keeping Kafka active.
No daily quota shutdown is enabled. If processing falls behind, the API keeps its freshness checks rather than presenting delayed active-match data as live.
Dashboard updates every five seconds. Viewing this page does not subscribe to matches.