You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Prometheus is selected to be monitoring system for ONAP.  Prometheus service, alert manager and Grafana is instantiated by MSB for monitoring various ONAP projects.

OOF is one of the first projects to provide metrics to Prometheus.  OOF exports some of the metrics to Prometheus service.

As part of that, OOF integrated Python based exporter client software.

HPA matching logic is the first one in OOF to export its metric.

OOF-HPA metrics

OOF-HPA metrics provide information for the user to visualize following:

  • Number of times there is successful flavor match :   flavor_match_successful
  • Number of times there is unsuccessful flavor match:  flavor_match_unsuccessful
  • Number of times cloud region is selected successfully :  cloud_region_successful_selection
  • Number of times no cloud region is selected:  cloud_region_unsuccessful_selection

Metrics alone does not provide much information. Labels for each metric quality the metric.

Current thinking is that we have following labels for each metric

Labels for flavor_match_successful and flavor match_unsuccessful

  • vnf_name
  • vnfc_name
  • service_name (if available in R3.  Make it available in R4)
  • customer_name (if available in R3. Make it available in R4)
  • cloud_region
  • policy_name

In case of flavor_match_unsuccessful, few additional labels help

  • mandatory_match_failed
  • ???

Labels for cloud_region_successful_selection and cloud_region_unsuccessful_selection

  • cloud_region
  • service_name
  • customer_name

In case of cloud_region_unsuccessful_selection

  • no_selection_due_to_flavors
  • no_selection_due_to_distance
  • no_selection_due_to_cost


  • No labels