There seem to be two different notions of cpu_util. One is the thing computed by the rate_of_change transformer in the cpu_sink sink defined in pipeline.yaml, and the other is a direct measurement by the CPUUtilPollster. The latter is masked by the former, as far as I can tell, though changing the name in pipeline.yaml to something clever like cpu_util2 then seems to allow both to be presented.
The telemetry-measurements page in the admin guide talk about cpu_util as being introduced in various releases for different hypervisors as a pollster-originated measurement), but then talking about cpu_util as being something generated by a transformer, too. Is this an oversight, or simply something left to operators to discover and choose between? Thanks, Danek _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
