Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

This list should be developed in conjunction with the  Doctor and VES Projects in OPNFV.

 

Monitoring Process information:

A Unique Process identifier.

NFVI Events

What about entire node and switch failures?  In terms of service affecting priority, host and switch failures are at the top as they can affect the most VMs / Containers / VNFs...

While the status of switches and hosts might be the domain of services that have a system-wide view, a host-resident component might be part of the monitoring functionality.

Compute

At a minimum the following events should be monitored:

  • Machine check exceptions (System, Processor, Memory...) [TODO: Break this down further]

Networking

At a minimum the following events should be monitored for a Networking interface:

  • Link Status
  • Dropped Receive Packets – An increasing count could indicate the failure or service interruption of an upstream processes.  

Storage

NFVI Other Information

Compute

BIOS information

Networking

Storage

NFVI Metrics

Compute

At a minimum the following metrics should be collected:

  • CPU Utilization
  • Memory Utilization
  • vMemory Utilization [TODO]
  • Cache Utililzation
  • Platform Metrics (thermals, fan-speed) [TODO: Break this down further]

 

Networking

[TODO] Add a note on the vSwitch and add vSwitch specific metrics

...

  • Average bitrate
  • Average latency

 

Storage