Visualizing Network Health: An Introduction to Bandwidth Graphs

Designing Clear Bandwidth Graphs: Best Practices and Common Pitfalls

Purpose & audience

• Purpose: Show what the graph should communicate (capacity, trends, spikes, utilization vs. threshold).
• Audience: Network operators, managers, or non-technical stakeholders — tailor detail and labels accordingly.

Data to include

• Primary metric: Throughput (bps) — plot both inbound and outbound if relevant.
• Supporting metrics: Packet loss, latency, error rates, and interface utilization (%) when they help explain anomalies.
• Time window: Choose a window that matches the troubleshooting need (real-time 1–15 min for live monitoring; 24–72 hours for trend analysis; 30–90 days for capacity planning).

Axis, scale, and units

• Y-axis units: Use bits per second (bps) or appropriate SI prefixes (kbps, Mbps, Gbps). Label units clearly.
• Scale choice: Use linear scale for utilization and absolute throughput; use logarithmic only if showing many orders of magnitude.
• Dual axes: Avoid dual Y-axes unless absolutely necessary; they can mislead. If used, clearly label and color-code each axis.

Visual encoding & layout

• Lines vs. areas: Use lines for precise time series, stacked areas for aggregated categories (e.g., per-app contributions).
• Colors: Use distinct, colorblind-safe palette; reserve bright/alert colors (red/orange) only for thresholds or alarms.
• Line weight & style: Keep lines thin for multiple series; use dashed lines for projected values or baselines.
• Legends & labels: Place legend near the chart; label key series inline when possible to reduce eye travel.
• Gridlines: Light, subtle gridlines help reading without dominating the view.

Annotations & context

• Thresholds: Draw capacity and SLA thresholds as horizontal lines with labels.
• Events: Annotate deployments, configuration changes, or outages to correlate causes.
• Aggregates & summaries: Show max, min, average, and 95th percentile values in a small stats panel.

Interactivity (for dashboards)

• Hover details: Show exact timestamped values and tooltip summaries.
• Zoom & pan: Allow zoom to inspect short-term spikes and pan for trend comparison.
• Series toggles: Let users hide/show series to reduce clutter.
• Time presets: Quick buttons for common windows (15m, 1h, 24h, 7d, 30d).

Best practices checklist

• Clear unit labels on axes.
• Appropriate time window for the task.
• Avoid dual axes unless labeled and justified.
• Use color deliberately and accessibly.
• Annotate known events and thresholds.
• Provide summary stats (avg, max, p95).
• Keep chart uncluttered—merge or hide low-value series.

Common pitfalls

• Misleading scales: Truncating Y-axis or using inconsistent units.
• Overplotting: Too many series without grouping or stacking.
• Unlabeled thresholds: Users can’t interpret alert lines without labels.
• Color misuse: Relying on red/green contrasts or indistinguishable hues.
• Ignoring context: Showing spikes without correlating events or other metrics.
• Using area charts for many series: Stacked areas can hide individual patterns and inflate perceived totals.

Quick example layout

• Title: concise + time window (e.g., “Interface eth0 Bandwidth — Last 24h”)
• Chart: line for in/out, capacity threshold (dashed), light gridlines
• Right-side panel: current, avg, max, p95 values; legend; event list
• Controls: time presets, series toggles, export button

Closing tip

Design first for the most common user task (troubleshooting vs. planning), then add extras (annotations, interactivity) that directly support that task.