CloudLens VM Sensor Sizing Calculator

Production resource planning · bare-metal / hypervisor VM tap agents · v1.0

VM Infrastructure PLATFORM

Hypervisor Affects install + mirror method

Guest OS Family

OS Version

VMs to Monitor

vCPU / VM

Memory / VM (GB)

Traffic & Mirror WORKLOAD

vNIC Throughput per VM Actual traffic, not vNIC capacity

Mirror Method How traffic reaches the sensor

Install Method

Kernel Headers Strategy For kernel module (Linux)

Debug Logging

CloudLens Connection CONFIG

Sensor Version / Package

vController Host / IP vController endpoint

Project Key From vController UI

Mirror Interface Which vNIC to tap

Package Repository URL Optional private repo

Custom Tags Optional, comma-separated k=v

Systemd Unit Name

Per-VM Sensor Footprint

CPU Request—

CPU Limit—

Memory Request—

Memory Limit—

% of VM vCPU—

% of VM Memory—

Fleet-Wide Totals

Total Sensor CPU—

Total Sensor Memory—

Total Mirrored Traffic—

Fleet Raw Resources—

Monitored VMs—

Install Command RPM

Run on each monitored VM. Copy-paste over SSH (Linux) or PowerShell remote (Windows).

Sensor Configuration File /etc/cloudlens/sensor.conf

Installed at /etc/cloudlens/sensor.conf (or C:\ProgramData\CloudLens\sensor.conf on Windows).

Ansible Playbook (fleet automation) ANSIBLE

Save as cloudlens-sensor.yml and run: ansible-playbook -i inventory cloudlens-sensor.yml. Ideal for deploying to hundreds of VMs.

Pre-Flight Checklist Script VALIDATE

Run before installing to verify kernel headers, promiscuous mode support, and firewall paths. Fails fast if anything's wrong.

Download Full Deployment Plan REPORT

One file with everything: scenario summary, sizing decision, all install commands, Ansible playbook, pre-flight script, and deployment checklist.

Tip: The markdown report renders in GitHub, GitLab, Slack, VS Code, Confluence, and Jira. For PDF, click Print / Save as PDF and choose "Save as PDF" in your browser's print dialog.

Reference: VM Sensor Sizing Tiers

Current selection highlighted. Values assume user-space capture + kernel tap module; DPDK variants use 20-30% less CPU at the high end.

vNIC Throughput	CPU Request	CPU Limit	Memory Request	Memory Limit	Typical Use Case
< 100 Mbps	100m	500m	128 MB	512 MB	Admin VMs, config servers
100 – 500 Mbps	250m	1 vCPU	256 MB	1 GB	Small web / API VMs
500 Mbps – 1 Gbps	500m	2 vCPU	512 MB	2 GB	Standard production VMs
1 – 3 Gbps	1 vCPU	3 vCPU	1 GB	3 GB	Database, app servers
3 – 5 Gbps	2 vCPU	4 vCPU	2 GB	4 GB	Streaming, Kafka brokers
5 – 10 Gbps	3 vCPU	6 vCPU	3 GB	6 GB	High-throughput, NFV
10 – 25 Gbps	4 vCPU	8 vCPU	6 GB	12 GB	Telco edge, DPDK VMs
25 – 40 Gbps	6 vCPU	12 vCPU	10 GB	20 GB	DPI, hyperscale

Architecture Diagram Click to view (PNG · SVG · Markdown export available)