Skip to main content
Migration Notice
We're migrating documentation from the old portal into this one. Some things may look a little different or out of place in the meantime — we know, and we're working to get it right. If something's unclear or doesn't look right, let us know.

Agent Dashboard — Egress (Tx Mbps)

What this chart shows​

Egress (Tx Mbps) — megabits per second of data leaving the agent host across all physical network interfaces, sampled from /proc/net/dev on every heartbeat (~30 s + 0–10 s jitter).

During an active copy job, Egress primarily reflects:

  • S3 PUT traffic — object data being uploaded to the vault target bucket
  • ClickHouse inserts — copy-log batches written to the ClickHouse metrics store
  • Console heartbeat — small periodic payloads sent to the console

S3 PUT traffic dominates when copy jobs are running; the other two are negligible by comparison.

Data collection — how bandwidth is sampled​

The agent reads raw byte counters from /proc/net/dev and sums across all physical interfaces. Virtual and container interfaces are excluded because they carry only internal traffic:

Excluded: lo, docker*, br-*, veth*, virbr*, tunl*, sit*, dummy*

Formula applied between two consecutive readings:

Tx Mbps = tx_bytes_delta × 8 / 1_000_000 / elapsed_seconds

Results are stored in ClickHouse and displayed here rounded to 3 decimal places.

This metric requires /proc/net/dev and is reported on Linux hosts.

First heartbeat after agent start​

The first sample after an agent starts (or restarts) always reports 0 Mbps. The sampler seeds a baseline on the first call and needs two readings to compute a delta. The second heartbeat (~30 seconds + 0–10 seconds jitter later) produces the first real value.

Fleet Total line​

When more than one agent has data in the selected time window, a Fleet Total dashed line is drawn over the per-agent lines. It shows the combined Egress of the entire agent fleet at each timestamp — a direct measure of total S3 PUT throughput across all agents.

The Fleet Total is computed client-side by summing all agent series per timestamp. It is not stored in ClickHouse.

Interpreting the chart​

  • Fleet Total ≈ total S3 PUT throughput — use this to measure overall vault protection write rate during active jobs.
  • Flat Egress during a running job — possible causes: network saturation, S3 throttling (429 responses), all objects are being Smart Skipped (already copied), or jobs are waiting for work rather than actively transferring.
  • Agent shows 0 — either the agent just started (first heartbeat), is running on a non-Linux OS, or has no active copy jobs.
  • One agent much higher than others — that agent is handling larger or more numerous objects. The Auto Distribution Plan spreads heavy buckets across agents the next time you start several syncs at once.

Polling interval​

~30 seconds + 0–10 seconds jitter per heartbeat. Historical data is retained for 90 days in ClickHouse.