a37dda5013
Gnocchi fixed its `aggregates` API with PR https://github.com/gnocchixyz/gnocchi/pull/1059. Before that patch, the `aggregates` API would only return the latest metadata for the resource of the metric being handled. Therefore, for CloudKitty processing and reprocessing, we would always have the possibility of using the wrong attribute version to rate the computing resources. With this patch we propose to always use the correct metadata for the processing and reprocessing of CloudKitty. This means, we always use the metadata for the timestamp that we are collecting at Gnocchi. The patch was released under version 4.5.0 of Gnocchi. Change-Id: I31bc2cdf620fb5c0f561dc9de8c10d7882895cce
14 lines
708 B
YAML
14 lines
708 B
YAML
---
|
|
fixes:
|
|
- |
|
|
CloudKitty will always use the correct metadata for the
|
|
processing and reprocessing jobs. This means, we always use
|
|
the metadata for the timestamp that we are collecting at
|
|
Gnocchi backend.This is achieved with the use of
|
|
``use_history=true`` in Gnocchi, which was released under
|
|
`version 4.5.0 <https://github.com/gnocchixyz/gnocchi/releases/tag/4.5.0>`__.
|
|
Before that release, the ``aggregates`` API would only return
|
|
the latest metadata for the resource of the metric being handled.
|
|
Therefore, for CloudKitty processing and reprocessing, we would
|
|
always have the possibility of using the wrong attribute version
|
|
to rate the computing resources. |