One of the telecom requirement of fault management for NFV is high scalability monitoring and advanced analytics. Distributed Monitoring and Analytics is the framework for fault management (FM), the architecture of DMA is to integrate each function of FM into each computing node. These functions are collecting, storing, evaluating, analysing, etc. Current centralized monitoring framework is strong and stable, but not high scalability. Distribution approach for FM is one of the solution for NFV. Using DMA, you can get the high scalability monitoring and advanced analytics.
Both use cases, you can watch the demo at OpenStack Summit Sydney's video (https://www.openstack.org/videos/summits/sydney-2017/dmadistributed-monitoring-and-analysis-monitoring-practice-and-lifecycle-management-for-telecom)
You can use the local agent function as a DMA function that is changing collectd config static and annotation that is combining libvirt information and OpenStack information into the alert. That code is included Gambia release. Manual is below link:
https://opnfv-barometer.readthedocs.io/en/stable-gambia/release/userguide/docker.userguide.html#build-and-run-localagent-and-redis-docker-images
Components
TBA
TBA
OpenStack Summit Berlin
https://www.openstack.org/videos/summits/berlin-2018/the-opnfv-barometer-with-telecom-operator-new-perspective-for-monitoring
OpenStack Summit Sydney
https://www.openstack.org/videos/summits/sydney-2017/dmadistributed-monitoring-and-analysis-monitoring-practice-and-lifecycle-management-for-telecom
OpenStack Summit Boston
https://www.openstack.org/videos/summits/boston-2017/distributed-monitoring-and-analysis-for-telecom-requirements
OpenStack Summit Barcelona
https://www.openstack.org/videos/summits/barcelona-2016/nec-the-telecom-requirements-for-openstack-how-to-reduce-operation-cost-after-day-2
TBA