Monitoring
Live interpreter health across every environment, polled continuously while the window is in front of you.
The board
One card per server: hostname, IP, uptime, and two gauges — latency and heap. Both run against fixed scales rather than each server’s own numbers, so you can compare machines at a glance instead of decoding four different axes.
| Gauge | Green | Amber | Red |
|---|---|---|---|
| Latency | under 100 ms | 100–200 ms | over 200 ms |
| Heap | under ~280 MB | ~280–420 MB | over ~420 MB |
An unreachable server shows a greyed dial and a dash rather than a needle at zero — a needle parked in the green would read as “healthy and fast”, which is the opposite of true.
Scoping
The control at the top filters to one environment. Everything follows it: the verdict chip, the online count, the averages and the grid. Cards name their environment only when you are looking at all of them.
Server detail
Click a card for the full health payload in a side panel — PID, Node or .NET version, platform and architecture, cores, heap used and total, RSS, external memory, uptime, and the domains that server is answering on.
It opens beside the grid rather than expanding in place, so the other servers do not move while you are comparing them.
Polling
Every ten seconds. Polling stops when the window is hidden or loses focus, and does one immediate refresh when you come back — so what you see on return is current rather than minutes stale.