Telemetry rate metrics are missing data

Solution In Progress - Updated -

Issue

  • When getting the measures for rate metric (cpu_util or any *.rate metric), there's some points missing in time
  • If controllerA treats sample cpu from instanceA, it will store the value in its local cache.
  • If controllerB treats the sample cpu from instanceA during the next polling, it's not aware of the predecessor, so it will drop the sample after storing it in its cache, thus creating a hole in the measures.

Environment

  • Red Hat OpenStack Platform 10
  • Red Hat OpenStack Platform 11
  • Red Hat OpenStack Platform 12
  • Red Hat OpenStack Platform 13

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content