Bug 1264172 - [RFE] Add time stamp to RESTAPI statistics data
[RFE] Add time stamp to RESTAPI statistics data
Product: ovirt-engine
Classification: oVirt
Component: RFEs (Show other bugs)
Unspecified Unspecified
unspecified Severity medium (vote)
: ---
: ---
Assigned To: Scott Herold
Gil Klein
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2015-09-17 13:36 EDT by Juan Hernández
Modified: 2016-02-10 14:25 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-11-23 04:01:55 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
juan.hernandez: ovirt‑future?
rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?

Attachments (Terms of Use)

  None (edit)
Description Juan Hernández 2015-09-17 13:36:25 EDT
Currently the RESTAPI doesn't include time stamps for the statistical data that it provides. For example, the CPU usage data is reported as follows:

  GET /hosts/{host:id}/statistics/{statistic:id}
  <statistic href="..." id="...">
    <description>User CPU usage</description>
    <values type="DECIMAL">

With this information it isn't possible to know exactly when the information was collected. For users of the RESTAPI that poll these statistics periodically this complicates calculation of accurate averages, or any other statistical measures.

The objective of this RFE is to add to the statistics a time stamp that reliably indicates when the data was collected:

  GET /hosts/{host:id}/statistics/{statistic:id}
  <statistic href="..." id="...">
    <values type="DECIMAL">

Note that even if the objective is to add the time stamp at the RESTAPI level, the rest of the components of the system (engine and VDSM) may need to be modified as well.
Comment 1 Yaniv Kaul 2015-11-22 15:27:27 EST
4.0 material?
Comment 2 Juan Hernández 2015-11-23 04:01:55 EST
When I opened this bug I thought that it was the solution for a specific user requirement. But it turned out that what they really need is what bug 1168022 requests. So this isn't needed any longer. I think that it would be nice to have, but no one actually needs it. I'm closing it.

Note You need to log in before you can comment on or make changes to this bug.