Network Function Virtualization (NFV) Performance Metrics
This dataset provides granular, time-stamped performance metrics for virtual and cloud-native network functions, including resource utilization, orchestration details, scaling events, and infrastructure allocation. It enables in-depth analysis of NFV operations, resource efficiency, and orchestration effectiveness across platforms such as Kubernetes and OpenStack. Ideal for network performance monitoring, optimization, and benchmarking in telecom and cloud environments.
Sample rows
preview · 8 of 250 rows · all 20 columns| record_idstring | mano_statusstring | network_throughput_mbpsfloat | nf_namestring | nf_typestring | nf_instance_idstring | orchestration_platformstring | vim_namestring | mano_instance_idstring | timestampdatetime | cpu_utilization_percentfloat | memory_utilization_mbfloat | storage_utilization_gbfloat | scaling_event_typestring | scaling_event_reasonstring | container_countinteger | vim_cpu_allocatedfloat | vim_memory_allocated_mbfloat | vim_storage_allocated_gbfloat | notesstring |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| rec-00001 | running | 1985.6 | firewall | CNF | cnf-ny-001 | Kubernetes | vim-nyc-k8s-1 | mano001 | 2024-05-01T10:22:31Z | 92.3 | 24256.7 | 158.2 | scale_up | Traffic spike during quarterly reporting | 12 | 24 | 32768 | 256 | Scaling triggered by heavy reporting load. |
| rec-00002 | running | 225.3 | load balancer | VNF | vnf-sfo-003 | OpenStack | vim-sfo-os-1 | mano002 | 2024-05-01T11:46:15Z | 33.2 | 3128.2 | 24.1 | none | blank | blank | 4 | 4096 | 32 | Routine operation, normal load observed. |
| rec-00003 | running | 44.2 | database proxy | CNF | cnf-lon-007 | Kubernetes | vim-lon-k8s-2 | mano003 | 2024-05-01T13:28:09Z | 8.7 | 321.8 | 8.2 | scale_down | Low off-peak usage detected. | 2 | 2 | 1024 | 12 | Off-hours, resources scaled down to save cost. |
| rec-00004 | error | 1324.8 | deep packet inspection | VNF | vnf-ny-004 | OpenStack | vim-nyc-os-2 | mano004 | 2024-05-01T13:47:45Z | 90.1 | 8950.2 | 36.8 | scale_up | Security event: DDoS mitigation. | blank | 16 | 12288 | 70 | High CPU; DDoS mitigation in progress. |
| rec-00005 | running | 1344.3 | service endpoint | CNF | cnf-bos-002 | Kubernetes | vim-bos-k8s-1 | mano005 | 2024-05-01T15:08:27Z | 61.7 | 17451.4 | 204.5 | scale_up | API request burst from mobile clients. | 10 | 12 | 24576 | 256 | API endpoint scaled up for demand. |
| rec-00006 | pending | 4.1 | network address translation | CNF | cnf-sfo-004 | Kubernetes | vim-sfo-k8s-1 | mano006 | 2024-05-02T09:14:01Z | 2.1 | 61.3 | 1.2 | none | blank | 0 | 0.5 | 128 | 2 | Test deployment; not in production. |
| rec-00007 | running | 329.9 | gateway | VNF | vnf-ny-002 | OpenStack | vim-nyc-os-3 | mano007 | 2024-05-02T10:45:23Z | 48.8 | 4096.5 | 30.6 | none | blank | blank | 8 | 8192 | 40 | Routine gateway operation, stable performance. |
| rec-00008 | running | 375.6 | caching service | CNF | cnf-ny-005 | Kubernetes | vim-nyc-k8s-2 | mano008 | 2024-05-02T12:18:50Z | 77.4 | 7112.6 | 60.3 | scale_up | Cache miss ratio exceeded threshold. | 8 | 8 | 16384 | 80 | Cache scaled up for increased hit rates. |
| rec-00009 | stopped | 8.6 | firewall | VNF | vnf-bos-005 | OpenStack | vim-bos-os-1 | mano009 | 2024-05-02T14:21:32Z | 4.3 | 132.1 | 2.7 | none | blank | blank | 1 | 256 | 5 | Firewall shutdown after maintenance window. |
| rec-00010 | running | 70.7 | load balancer | CNF | cnf-lon-003 | Kubernetes | vim-lon-k8s-1 | mano010 | 2024-05-02T16:44:19Z | 15.6 | 984.5 | 12.5 | scale_down | Off-peak hours, reduced demand. | 1 | 2 | 2048 | 16 | Load balancer scaled down for off-peak. |
| rec-00011 | running | 166.2 | database proxy | VNF | vnf-sfo-002 | OpenStack | vim-sfo-os-2 | mano011 | 2024-05-03T09:37:10Z | 21.9 | 1453.6 | 13.2 | none | blank | blank | 4 | 4096 | 20 | Routine DB proxy activity, regular updates. |
| rec-00012 | error | 4120.5 | firewall | CNF | cnf-ny-012 | Kubernetes | vim-nyc-k8s-3 | mano012 | 2024-05-03T11:00:55Z | 98.2 | 52312.2 | 812 | scale_up | Critical security incident/attack. | 20 | 32 | 131072 | 1024 | Firewall under heavy attack, resources maxed. |
| rec-00013 | pending | 3.2 | service endpoint | VNF | vnf-lon-010 | OpenStack | blank | mano013 | 2024-05-03T11:18:33Z | 2.7 | 90.6 | 0.8 | none | blank | blank | 0.5 | 128 | 3 | New deployment, pending activation. |
| rec-00014 | running | 321.9 | network address translation | CNF | cnf-bos-009 | Kubernetes | vim-bos-k8s-2 | mano014 | 2024-05-03T12:35:27Z | 49.4 | 7923.5 | 59 | scale_up | Increased NAT session count. | 7 | 8 | 12288 | 64 | NAT scaled for new connections. |
| rec-00015 | error | 1780.7 | load balancer | VNF | vnf-ny-008 | OpenStack | vim-nyc-os-4 | blank | 2024-05-03T13:12:03Z | 88.6 | 16288.5 | 88.4 | scale_up | Sudden traffic spike due to campaign. | blank | 16 | 20480 | 120 | Load balancer error, VIM/MANO unavailable. |
| rec-00016 | running | 1100.3 | caching service | CNF | cnf-sfo-011 | Kubernetes | vim-sfo-k8s-2 | mano015 | 2024-05-03T14:42:42Z | 66.2 | 10984.2 | 205.7 | scale_up | Frequent cache misses, increased demand. | 6 | 10 | 16384 | 256 | Scaling cache for higher hit rate. |
| rec-00017 | stopped | 0 | deep packet inspection | VNF | vnf-bos-001 | OpenStack | vim-bos-os-2 | mano016 | 2024-05-03T15:13:51Z | 0.9 | 8.5 | 0.2 | none | blank | blank | 0.1 | 12 | 1 | VNF stopped after test run. |
| rec-00018 | pending | 9.9 | service endpoint | CNF | cnf-ny-010 | Kubernetes | blank | mano017 | 2024-05-03T16:37:19Z | 3.5 | 120.7 | 2.4 | none | blank | 0 | 0.3 | 64 | 2 | CNF deployed, waiting for traffic. |
| rec-00019 | running | 192.7 | firewall | VNF | vnf-lon-011 | OpenStack | vim-lon-os-1 | mano018 | 2024-05-04T09:17:03Z | 37.6 | 3012.3 | 21.9 | none | blank | blank | 4 | 4096 | 24 | Firewall routine traffic filtering. |
| rec-00020 | running | 2200.9 | load balancer | CNF | cnf-sfo-015 | Kubernetes | vim-sfo-k8s-3 | mano019 | 2024-05-04T10:57:41Z | 83.2 | 36012.1 | 310.4 | scale_up | High demand during online event. | 15 | 28 | 65536 | 512 | Load balancer scaled for event traffic. |
What the 250 rows show
from the 250-row sampleError (mano status) stands out: mean network_
- 179.6median network_
throughput_ mbps - 2nf types
- 3orchestration platforms
- 3scaling event types
- 35.8median cpu_
utilization_ percent - 2,449median memory_
utilization_ mb
Median 179.6, from 0.0 to 5,000.
- string 11
- integer 1
- float 7
- datetime 1
Columns
20 columns in three groups| column | type | description | example |
|---|---|---|---|
| Text 11 columns | |||
record_id | string | Unique identifier for each performance metric recordunique | rec-00001 |
nf_type | string | Type of network function (VNF or CNF)VNF · CNF | CNF |
nf_instance_id | string | Unique identifier for the network function instance | cnf-ny-001 |
nf_name | string | Name of the network function (e.g., firewall, load balancer)8 names | firewall |
orchestration_platform | string | Name of the orchestration platform (e.g., Kubernetes, OpenStack)Kubernetes · OpenStack · Other | Kubernetes |
vim_name | string | Name of the Virtual Infrastructure Manager (VIM) allocating resourcesoptional | vim-nyc-k8s-1 |
mano_instance_id | string | Identifier for the MANO (Management and Orchestration) instance managing the NFoptional | mano001 |
scaling_event_type | string | Type of scaling event (e.g., scale_up, scale_down, none)scale_up · scale_down · none · optional | scale_up |
scaling_event_reason | string | Reason for the scaling event, if applicableoptional | Data migration completed |
mano_status | string | Current status reported by the MANO instance (e.g., running, stopped, error)running · stopped · error · pending · optional | running |
notes | string | Additional notes or comments about the metric recordoptional | Scaling triggered by heav… |
| Numbers 8 columns | |||
cpu_utilization_percent | float | CPU utilization percentage for the network function instance0 to 100 | 92.3 |
memory_utilization_mb | float | Memory utilization in megabytes for the network function instance0 or more | 24256.7 |
storage_utilization_gb | float | Storage utilization in gigabytes for the network function instance0 or more | 158.2 |
network_throughput_mbps | float | Network throughput in Mbps for the network function instance0 or more · optional | 1985.6 |
container_count | integer | Number of containers/pods running for the CNF/VNF instance0 or more · optional | 12 |
vim_cpu_allocated | float | CPU resources allocated by the VIM (in vCPUs)0 or more · optional | 24 |
vim_memory_allocated_mb | float | Memory resources allocated by the VIM (in MB)0 or more · optional | 32768 |
vim_storage_allocated_gb | float | Storage resources allocated by the VIM (in GB)0 or more · optional | 256 |
| Dates and times 1 column | |||
timestamp | datetime | Date and time when the metric was collected | 2024-05-01T10:22:31Z |
Use it for
A telecommunications dashboard
Network_
throughput_ mbps by mano_ status and a breakdown of nf_ name. Excel, Power BI or Tableau. Why do the 28 error rows have a mean network_
throughput_ mbps of 3,699? A root-cause class exercise
Hand out the rows and one question. The answer is in the data, not in the brief.
- Records250rec-000011985.6runningrec-00002225.3runningrec-0000344.2running
A software demo
Believable records with nf_
type, nf_ instance_ id and nf_ name to fill a screen in front of a buyer.
This dataset250 rows20 columns
Yours1,000 rows20 columns
blueprint · network-function-virtualization-nfv-performance-metrics
Behind this dataset
Same schema. As many rows as you need.
These 250 rows came out of a blueprint — 20 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.
Rules it was built with
- VNF/CNF instance ID and network service (vEPC, vIMS, vCDN, etc.)
- Deployment type: VM-based VNF or container-based CNF (Kubernetes pods)
- CPU utilization percentage and CPU pinning/NUMA optimization
- Memory utilization and huge pages allocation for performance
- Storage IOPS (input/output operations per second) for databases
- Network throughput and SR-IOV/DPDK acceleration enablement
- VNF scaling events: scale-out (add instances), scale-in (remove instances)
- MANO (Management and Orchestration): NFVO, VNFM lifecycle operations
Open the blueprint in Data Factory
1 credit per row. Preview 20 rows free. Buy rows for the full run.
- Exports
- CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
- Licence
- yours to use, including commercially
- API slug
- network-function-virtualization-nfv-performance-metrics