Smarter by Design.Simpler for Business
TR7Enterprise Application Delivery & Security Platform
What does the Live Stats screen show?
Short answer
Live Stats is the tab that shows the current state of a vService with live counters refreshed every second by default; the data is not stored and no time range is selected. The screen consists of the Frontend, Source IP Statistics, Traffic Mirroring, Backend Services, Action Hits and Live Traffic sections; which of them appear depends on the vService type and the features that are on. The Frontend cards give the uptime, CPU, memory, sessions, request and connection rates, response time and throughput; the Backend Services table gives the status, sessions, rate and error rates of each Backend Service; and Live Traffic gives the country map and the busiest source IPs. The refresh interval is selected as 1s, 5s, 10s or 30s (at least 5s in a Network vService), and a live stream lasts about 30 minutes (screen controls).
How Does It Work?
Live Stats is the Live Stats tab of the screen that opens when the vService is clicked in the Left Monitor Panel's Load Balancer vServices category; when the tab is opened, the live stream starts, the counters are refreshed at the selected interval and the data is not stored (accessing Live Stats).
- Refresh interval: 1s (default), 5s, 10s, 30s; at least 5s in a Network vService (screen controls).
- LIVE indicator: Pulses while the live stream is running. The stream stops by itself after about 30 minutes; it is restarted by turning LIVE off and on, or by refreshing the page.
Live Stats and Dashboard
| Live Stats | Dashboard | |
|---|---|---|
| Time | Now | Selected past range |
| Refresh | 1–30 seconds | Auto-refresh or manual |
| Storage | None | Read from the archive |
| Use | Real-time problem tracking | Trend and comparison |
Live Stats Sections in TR7
| Section | What it shows |
|---|---|
| Frontend | Uptime, CPU, Memory usage, Current sessions, Queued requests, HTTP Request/s (Rate max in L7 TCP), New connection/s, Avg. Response Time, Throughput, Incoming, Outgoing; SSL, compression and cache cards if there is a profile |
| Source IP Statistics | Active IPs; per-client peak and p95 request and connection, peak error and peak incoming/outgoing traffic values in the measurement window (default 10 seconds) (request and error cards only in HTTP; no section in Network) |
| Traffic Mirroring | Copy traffic if Traffic Mirroring is defined on the vService |
| Backend Services | The health status, current session count, request or new connection rate, average response time, traffic and, in HTTP, the 4xx/5xx rates of each Backend Service |
| Action Hits | Per-second count of the actions with Hit Counter on |
| Live Traffic | Country map and the busiest source IPs of the last 10 seconds (not in Network) |
If Bot/DDoS protection is on, badges showing the ratio to the protection limit appear on the related cards. In a cluster, each device is shown in a separate column; the values are not summed.
Common Misconceptions
- "Live Stats flows continuously." The stream stops after about 30 minutes; if the values have frozen, LIVE is restarted.
- "Live Stats data is reviewed later." The data is not stored; the Dashboard is used for history.
- "A zero value means no traffic." A read error and the absence of traffic are not distinguished on the screen; for a section that reads zero continuously, whether there is traffic is verified on the Logs & Tracking screen.
How it is done in the documentation
