Network Stat Visualizer
Turn firewall, proxy, load balancer and network-device statistics into friendly interactive graphs. Files are parsed in your browser and are not uploaded by this tool.
Raw Data Lab — Paste Vendor CLI / Monitoring Output
Tip: separate repeated snapshots with a blank line or a line beginning with ---. If a timestamp exists in the text it will be used; otherwise the parser creates Sample 1, Sample 2, etc.
Comparison Mode — Before vs After / Device A vs Device B
Dataset A
Dataset B
Hover/tap a point for values. Drag across the graph to zoom into a time range. Double-click the graph to reset zoom.
User Guide — How to Prepare and Plot Device Statistics
SanchitGurukul — Technology • Education • Innovation
Select a vendor below for practical guidance. Export operational statistics from your device or management platform, keep a timestamp/date column where possible, and save the data as CSV, TSV, TXT or JSON. The visualizer processes the selected file in your browser.
Palo Alto Networks PAN-OS
Useful statistics: dataplane/management CPU, memory, active sessions, session utilization, new sessions/CPS, throughput, packet drops, threat events, GlobalProtect users and interface counters.
Where data commonly comes from: PAN-OS operational monitoring, ACC/report exports, Panorama reports, SNMP/telemetry collectors, or your monitoring platform. Export a time-series report where available.
Recommended columns: timestamp, cpu_percent, memory_percent, sessions, session_utilization, cps, throughput_mbps, drops, threat_events
Visualizer tip: use CPU & Memory for resource trends, Sessions for capacity behavior, Traffic for throughput, and Security Events for threat spikes. Treat generic threshold lines as references rather than PAN-OS model limits.
How to gather data
PAN-OS CLI: collect repeated snapshots with show system resources, show running resource-monitor and show session info; use Panorama/report or monitoring exports for historical data.
Sample CSV
timestamp,cpu_percent,memory_percent,sessions,session_utilization,cps,throughput_mbps,drops,threat_events 10:00,31,57,18420,28,340,620,3,4 10:05,38,59,22110,34,470,790,7,6 10:10,74,64,39750,61,890,1260,26,19
Example: upload the CSV, open the automatically generated dashboards, then correlate traffic/session demand with resource, error, latency or security-event changes.
Fortinet FortiGate / FortiOS
Useful statistics: CPU, memory, session count, session setup rate, bandwidth, interface packets/errors, drops, VPN users, IPS/AV events and blocked traffic.
Where data commonly comes from: FortiGate/FortiManager/FortiAnalyzer reports, performance monitoring, SNMP, telemetry or external monitoring systems. CSV exports from reporting systems are easiest to graph.
Recommended columns: timestamp, cpu_percent, memory_percent, sessions, cps, rx_mbps, tx_mbps, drops, ips_events
Visualizer tip: compare RX/TX together in Traffic and correlate session/CPS peaks with CPU or memory changes.
How to gather data
FortiOS CLI: get system performance status provides CPU/memory and session/network performance information; diagnose sys top helps inspect processes. FortiAnalyzer/FortiManager or monitoring exports are better for history.
Sample CSV
timestamp,cpu_percent,memory_percent,sessions,cps,rx_mbps,tx_mbps,drops,ips_events 10:00,22,51,12600,210,410,365,1,2 10:05,35,54,15840,390,590,510,4,5 10:10,69,62,24750,720,910,840,18,14
Example: upload the CSV, open the automatically generated dashboards, then correlate traffic/session demand with resource, error, latency or security-event changes.
Check Point Security Gateway
Useful statistics: CPU, memory, connections, connection rate, throughput, SecureXL/CoreXL-related performance counters, drops, VPN activity and threat-prevention events.
Where data commonly comes from: Gaia/SmartConsole monitoring and reports, management reporting, SNMP, CPView-derived exports or an external monitoring platform.
Recommended columns: timestamp, cpu_percent, memory_percent, connections, cps, throughput_mbps, drops, threat_events
Visualizer tip: graph connection load and throughput beside CPU trends when investigating performance pressure. Avoid assuming counters from different gateway models have identical capacity limits.
How to gather data
Use CPView on the Security Gateway for continuously refreshed CPU, memory and Software Blade statistics. Save/capture supported CPView data or use SmartConsole, SNMP or monitoring exports for a time series.
Sample CSV
timestamp,cpu_percent,memory_percent,connections,cps,throughput_mbps,drops,threat_events 10:00,27,55,14320,250,480,2,3 10:05,44,58,19760,440,710,8,7 10:10,71,63,28610,690,1040,21,16
Example: upload the CSV, open the automatically generated dashboards, then correlate traffic/session demand with resource, error, latency or security-event changes.
Cisco ASA / Secure Firewall Threat Defense
Useful statistics: CPU, memory, connections, connection rate, interface throughput, drops/errors, VPN sessions, inspection events, intrusion events and blocked traffic.
Where data commonly comes from: ASA operational output converted to tabular data, Secure Firewall Management Center reports, SNMP/telemetry or external monitoring tools.
Recommended columns: timestamp, cpu_percent, memory_percent, connections, cps, inside_mbps, outside_mbps, drops, intrusion_events
Visualizer tip: use Sessions for concurrent connections and CPS, Errors & Drops for interface/inspection problems, and Security Events for intrusion activity.
How to gather data
Gather read-only ASA/FTD CPU, memory, connection and interface statistics. For FTD, use Secure Firewall Management Center reports or monitoring integrations for historical data; take consistent periodic snapshots.
Sample CSV
timestamp,cpu_percent,memory_percent,connections,cps,inside_mbps,outside_mbps,drops,intrusion_events 10:00,25,49,11200,180,320,305,1,2 10:05,37,52,14900,330,505,480,5,4 10:10,66,59,23500,610,810,775,17,13
Example: upload the CSV, open the automatically generated dashboards, then correlate traffic/session demand with resource, error, latency or security-event changes.
Juniper SRX / Junos
Useful statistics: routing-engine/SPU resource statistics, sessions, session setup, interface traffic, packet errors/drops, flow statistics, VPN activity and security events.
Where data commonly comes from: Junos operational monitoring, Junos Space/Security Director reporting, SNMP, streaming telemetry or an external collector.
Recommended columns: timestamp, cpu_percent, memory_percent, sessions, cps, input_mbps, output_mbps, drops, security_events
Visualizer tip: preserve separate SPU/RE columns when your export provides them; graphing them separately can make resource bottlenecks easier to identify.
How to gather data
Junos operational mode: show security monitoring can provide sessions/CPU/memory on supported SRX; show security monitoring performance session gives recent sessions; show interfaces statistics or monitor interface gives interface counters/rates.
Sample CSV
timestamp,cpu_percent,memory_percent,sessions,cps,input_mbps,output_mbps,drops,screen_events 10:00,20,46,9700,160,270,245,0,1 10:05,33,49,13200,310,455,420,3,4 10:10,62,57,21900,590,760,715,15,12
Example: upload the CSV, open the automatically generated dashboards, then correlate traffic/session demand with resource, error, latency or security-event changes.
Zscaler Internet Access / Private Access
Useful statistics: requests, bandwidth, response/transaction time, blocked transactions, web/security events, authentication activity, application usage and connector/tunnel health statistics where available.
Where data commonly comes from: Zscaler analytics/report exports, log streaming/NSS/SIEM data, API-derived reports or monitoring exports. Convert event-heavy logs into time buckets before plotting large datasets.
Recommended columns: timestamp, requests, bandwidth_mbps, latency_ms, blocked_requests, security_events, errors
Visualizer tip: aggregate high-volume logs into 1-, 5- or 15-minute buckets and use Average/Maximum depending on whether you are studying baseline behavior or spikes.
How to gather data
Use ZIA Insights/Logs CSV downloads for historical transactions or NSS feeds for continuous log streaming. Aggregate raw transactions into 1/5/15-minute buckets before graphing and omit unnecessary sensitive fields.
Sample CSV
timestamp,requests,bandwidth_mbps,latency_ms,blocked_requests,security_events,errors 10:00,18400,210,84,320,14,9 10:05,23100,285,96,510,21,13 10:10,34700,390,172,1280,66,31
Example: upload the CSV, open the automatically generated dashboards, then correlate traffic/session demand with resource, error, latency or security-event changes.
Broadcom / Symantec Blue Coat ProxySG
Useful statistics: client requests, connections, bandwidth, response time, cache hit ratio, CPU, memory, denied requests and errors.
Where data commonly comes from: ProxySG statistics/reporting, access-log analysis, Management Center/report exports, SNMP or an external monitoring platform.
Recommended columns: timestamp, requests, connections, bandwidth_mbps, latency_ms, cache_hit_percent, cpu_percent, denied, errors
Visualizer tip: correlate cache hit ratio with bandwidth and latency. For access logs, aggregate individual transactions into time buckets before upload.
How to gather data
Collect ProxySG statistics through your management/reporting platform, SNMP or access-log analytics. Aggregate access logs into fixed time buckets and calculate requests, bandwidth, latency, cache hit, denied and errors.
Sample CSV
timestamp,requests,connections,bandwidth_mbps,latency_ms,cache_hit_percent,cpu_percent,denied,errors 10:00,12100,3200,165,72,64,24,180,5 10:05,16900,4100,230,89,61,36,270,9 10:10,25100,5900,345,148,53,61,640,22
Example: upload the CSV, open the automatically generated dashboards, then correlate traffic/session demand with resource, error, latency or security-event changes.
F5 BIG-IP
Useful statistics: TMM CPU, memory, active connections, connection rate, virtual-server traffic, requests/sec, SSL TPS, pool/member availability, server-side latency, drops and WAF/security events.
Where data commonly comes from: BIG-IP statistics, BIG-IQ reports, telemetry streaming, SNMP or monitoring-platform exports.
Recommended columns: timestamp, cpu_percent, memory_percent, active_connections, cps, throughput_mbps, rps, ssl_tps, server_latency_ms
Visualizer tip: keep client-side and server-side metrics as separate columns. This helps distinguish incoming demand from backend performance problems.
How to gather data
Use BIG-IP Statistics/Analytics, monitoring integrations or TMSH performance views. System/connection/throughput statistics and Analytics CSV exports can provide time-series data where the required BIG-IP analytics capability is provisioned.
Sample CSV
timestamp,cpu_percent,memory_percent,active_connections,cps,throughput_mbps,rps,ssl_tps,server_latency_ms 10:00,29,52,8400,240,530,3100,1200,38 10:05,42,55,11900,410,760,4700,1840,51 10:10,68,61,18700,680,1110,7200,2960,94
Example: upload the CSV, open the automatically generated dashboards, then correlate traffic/session demand with resource, error, latency or security-event changes.
A10 Thunder ADC / CGN / TPS
Useful statistics: CPU, memory, connections, CPS, throughput, packets/sec, HTTP requests, SSL TPS, server latency, CGN session/NAT statistics, attack traffic and mitigated/dropped traffic for TPS deployments.
Where data commonly comes from: ACOS operational statistics, aGalaxy/management reporting, SNMP, API/telemetry collectors or monitoring exports.
Recommended columns: timestamp, cpu_percent, memory_percent, connections, cps, throughput_mbps, pps, ssl_tps, attack_pps, mitigated_pps
Visualizer tip: for DDoS/TPS analysis, plot attack and mitigated traffic together. For ADC analysis, compare connections/CPS with server latency and resource utilization.
How to gather data
ACOS: useful checks include show slb virtual-server, show slb service-group, show slb server, show slb resource-usage and show session. GUI statistics and aXAPI /stats resources can provide structured data for collection.
Sample CSV
timestamp,cpu_percent,memory_percent,connections,cps,throughput_mbps,pps,ssl_tps,backend_latency_ms 10:00,23,48,7600,210,440,62000,980,31 10:05,39,52,10800,390,680,91000,1540,43 10:10,65,59,17100,640,1020,141000,2480,82
Example: upload the CSV, open the automatically generated dashboards, then correlate traffic/session demand with resource, error, latency or security-event changes.
Generic Firewall / Proxy / Router / Switch / ADC
Minimum requirement: one row per observation and at least one numeric metric. A timestamp/date/time column is strongly recommended.
Common columns: timestamp, cpu_percent, memory_percent, sessions, connections, cps, throughput_mbps, pps, errors, drops, latency_ms
Example:
timestamp,cpu_percent,memory_percent,sessions,throughput_mbps,drops 09:00,34,58,4200,285,2 09:05,36,59,4380,301,1 09:10,41,60,4720,337,8
Visualizer tip: clear column names improve automatic classification. If auto detection is not suitable, choose Generic and use the Custom dashboard to select metrics manually.
How to gather data
Use a safe read-only source such as CLI statistics, SNMP, telemetry, controller/report export or a monitoring platform. Collect at regular intervals and never include passwords, API tokens or unnecessary identity fields.
Sample CSV
timestamp,cpu_percent,memory_percent,sessions,throughput_mbps,pps,errors,drops,latency_ms 10:00,18,43,6500,310,44000,1,0,22 10:05,26,46,8100,430,61000,2,3,27 10:10,57,54,14300,760,103000,8,14,61
Example: upload the CSV, open the automatically generated dashboards, then correlate traffic/session demand with resource, error, latency or security-event changes.
Your feedback matters