HAProxy Stats, sessions and stick tables

Last updated: · Applies to Roxy-WI 10.0 and later.

Use Roxy-WI 10.0 HAProxy Runtime API statistics, transient server controls, persistent backend edits, connection limits, sessions and stick tables.

Open the current Stats workspace

Open Services → HAProxy → Stats and select a server. The 10.0 workspace reads HAProxy Runtime API snapshots, rather than embedding its HTTP statistics page. Configure the service's Runtime API access and the group's haproxy_sock_port; the running socket needs permission for the commands you intend to use.

Use Refresh or the auto-refresh interval. The Overview tab groups frontends, backends, servers and listeners and exposes traffic, connection, queue and health counters. Read-only users can inspect data; mutations require operator access to HAProxy and the selected server.

HAProxy Stats overview with filters, Sessions and Stick tables tabs
HAProxy Stats overview with filters, Sessions and Stick tables tabs. Captured on the public Roxy-WI demo.

Find the relevant row

Use text search, state and type filters, the backup-only or problems-only switches, and the column selector. A missing counter is not assumed to be zero. Refresh after a reload or restart before acting on an older row; actions verify the process and target identity.

Temporary server state and weight

Use the server row's controls to select ready, drain or maintenance state, or adjust its absolute weight (0–256; 0 removes it from balancing). These are Runtime changes on the selected HAProxy instance. They do not edit configuration files or automatically propagate to linked replicas.

Refresh to verify the resulting state. Runtime-only changes may disappear after reload/restart according to HAProxy's state-restoration configuration. Do not confuse this with the persistent configuration operations below.

Persistent server changes and connection limits

Use Add server, Edit address and port or Delete server on the relevant backend/server row. The address must be IPv4 or IPv6; review the health-check options when adding a server. Review the displayed targets: these operations include the selected server and directly linked replicas. Configuration is validated for every target and checked for drift before changes begin.

Adding/editing a supported server updates runtime and the configuration; deleting a server saves the configuration and reloads HAProxy. Matching form-managed settings are updated as well. Unsupported or ambiguous sections and changed targets are rejected; use the configuration workflow for changes outside the form's scope.

Connection-limit controls support global, frontend and individual server limits. They update runtime and persist the setting in configuration. Global/frontend values must be positive integers; a server value of 0 removes its individual limit. A global runtime value cannot exceed the running process's hard limit. Maxconn currently locates its target in the main configuration file; use the configuration editor for a target in another file. These operations require direct deployment to be allowed on every target; a Change Center-only policy is not bypassed.

Inspect per-target results on failure: files, runtime or saved form state may need reconciliation. Recovery is not a guarantee of an atomic update across all hosts. Refresh actual state and history before repeating an uncertain operation. Use Change Center for reviewed configuration deployment.

Sessions

Open Sessions to search active connections and inspect their details. A server-scoped view narrows the list to a selected backend server. Authorized users can terminate a session after confirmation.

The action is immediate and affects the selected running instance. Session identities are rechecked, because a connection may finish or the process may restart between viewing and acting. If the snapshot is stale, refresh instead of reusing an old session reference.

Stick tables

Open Stick tables, choose a table and search its entries. Inspect an entry's counters, remove an individual entry or clear the selected table after confirmation.

These operations change in-memory state on the selected instance; any HAProxy peer replication is governed by HAProxy's configuration. Removing entries can affect rate limits or affinity. Entries in use may remain, and traffic or peers can recreate them. Unsupported key types remain read-only. A table/process change requires a refreshed view before another action.

Troubleshooting

For an unavailable snapshot, check service state, Runtime socket access and configured port. For denied commands, check operator permissions and the socket's administrative level. For stale targets, refresh and reopen the action. For a persistence failure, inspect all reported nodes and their configuration/runtime state.

Adopted Docker/Podman services use their saved engine, owner and network context; see container requirements. Request routing problems can be investigated with request diagnostics. The separate Runtime API command interface remains available for supported manual commands.

All documentation · Roxy-WI 10.0 release notes