Gateway

reading the ingress…

ports

n/a

connections

n/a

live

n/a

warnings

n/a

No gateway configured

Set GATEWAY_HOST to the HOST_TARGETS name of the machine that routes this fleet, and run agent/host_agent.py 1.2.0 on it — that is the version that reads the proxy configs and the kernel's socket table.

Warnings to address

Connection map

nginx

Charts

haproxy

Charts

a line is drawn because the config says the route exists, and it animates only while at least one connection is open on it — a resting line is not a dead one, and nothing here is coloured by a verdict: a busy ingress is the job.

a dash means the endpoint is written in the config as a name; the page matches sockets by address and resolves nothing, so this route is drawn but not counted.

the switch shows what the config says; toggling a route needs a config write path and is not wired up yet.

the filter box hides the routes whose own labels do not contain what you typed — domain, server_name, map key, endpoint or port. It asks for nothing: the tallies, the warnings and the charts above it are still the whole ingress, not the filtered part of it.