management of VNF life cycles. ONAP orchestration addresses various VNF lifecycle aspects such as instantiation, elastic scaling, service assurance, automatic recovery from resource Building the Network of the Future failures, resource allocation, etc. To facilitate this, VNFs need to be equipped with capabilities that comply with standards to enable automated measurements. VNFs must provide a compat- ible interface to ONAP for data collection and event notification. The current options are JSON schema and REST APIs. AT&T excludes the use of SNMP, CLIs, and EMS, SO as to ensure ven- dor independence. The end-to-end service reliability and availability in a virtualized network will greatly depend on the ability to monitor and manage the behavior of VNFs in near real-time rather than relying on reliability and availability of network elements. The ONAP platform will monitor performance of VNFs using the capabilities provided by these resources to proactively predict potential issues and resolve them automatically by taking appropriate actions such as restart of the resources or provid- ing additional capacity. This means that the VNF developers are required to provide a rich set of monitoring and alerting capabilities to facilitate near real-time monitoring and proactive problem resolution. VNFs are required to provide the following network data in real time and near real-time streaming: Consistent fault alarm and event format in a defined standard Events (i.e., host/customer configurations changes, etc.) Performance management data (i.e., application KPIs) Usage data (i.e., call detail records) On-demand access to additional detailed tracing and trouble-shooting data 16.8.2 PASSIVE VPROBE MEASUREMENT DATA MODEL Passive probe monitoring in legacy networks required an appliance that would tap or port mir- ror a specific service network interface to capture network packets for service-specific analysis. Passive network monitoring can collect and correlate packets into enriched transactional records. Virtualization ha