- Requests, 5xx/4xx, bandwidth, p50/p95 and top paths per service (1 h / 24 h / 7 d)
docker logs -fstreamed through the agent, ANSI colours rendered, filter and error highlightingdocker exec -it … shin the browser (xterm.js)- Deploy and job logs kept with their history
- Log views reconnect themselves after a network blip
- Connectivity test from the service's network position
Traffic
The Traffic tab reads Traefik’s access log on the server and shows, per service and per window (1 hour, 24 hours, 7 days): requests, 5xx and 4xx counts, bandwidth, p50 and p95 latency and the top paths. No agent in your app, no third-party analytics: it is the proxy’s own log, parsed on the server.
Logs
Container logs stream live through the agent tunnel. ANSI colours, bold and dim are rendered instead of raw escape codes; filtering and error highlighting work on the plain text. Deploy and job logs are kept with their history so you can read what happened last week. Views reconnect themselves after a network blip and have a Refresh button.
Terminal
The Terminal tab opens sh inside the running container with xterm.js. Inspect files, run a migration, tail a log — through the same outbound WebSocket the agent already holds, with no SSH and no open port.
Connectivity test
The Advanced tab can test a host and port from the service’s network position: is the database reachable by name, does the outbound request to a third-party API get through, is the port on the other server open to this one.