Ussuri separation of nova-cloud-controller and placement needs to be reflected in dashboard and metrics collected

Bug #1910442 reported by Drew Freiberger
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
prometheus-grok-exporter-charm
Won't Fix
Undecided
Unassigned

Bug Description

On bionic-ussuri clouds, the placement engine is moved out of the nova-cloud-controller application and into it's own charmed application space. Also, the nova-api logs moved to be apache WSGI logs.

Both the prometheus-grok-exporter and the grafana dashboard need to be updated to reflect these differences.

One can get some of the data in the Grok Exporter graphs by adding a relation between prometheus-grok-exporter and the placement application, but the dashboard needs to split the source hosts of the nova api logs from the source hosts of the placement api logs.

Nova-cloud-controller variable on the dashboard needs to change to be a query of nova_conductor_errors.

nova-placement variable needs to be added with the equivalent query of the current nova-cloud-controller variable.

Panels using $nova-cloud-controller need their queries to be updated to use $placement for data provided by the placement units.

Revision history for this message
Eric Chen (eric-chen) wrote :

This charm is no longer being actively maintained

Changed in charm-prometheus-grok-exporter:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.