summaryrefslogtreecommitdiff
path: root/requirements.txt
diff options
context:
space:
mode:
authorMehdi Abaakouk <sileht@redhat.com>2017-07-18 08:10:38 +0200
committerMehdi Abaakouk <sileht@redhat.com>2017-07-20 16:45:20 +0200
commit75e10b2a4808ee007a8e3d768ae90fa1037a3c11 (patch)
tree4ea79cf25cce535aa85a16846f4e5183bf475adf /requirements.txt
parent5a049260122bacf683d66985d5500826b903443f (diff)
downloadceilometer-75e10b2a4808ee007a8e3d768ae90fa1037a3c11.tar.gz
High precision rate of change timedelta
The current way to calculate rate of change is not precise at all and depends on the local host clock. So, we have good chance that the host clock derive a bit between each polling. Also the timestamp is polling cycle run and not the exact polled sample. This makes the rate of change transformer not accurate, and maybe wrong if the local clock have jumped to much or if a pollster make to much time to get the stats (libvirt reconnection, ...). A sample gets a new attribute monotonic_time, where we can store an accurate polling time using monotonic.monotonic(). In rate of change transformer, if the monotonic time is available we use to calculate the time delta between samples. For instance metrics, we set monotonic_time as soon as we poll it from libvirt, avoiding almost all precision issue. That makes the rate of change precise to the nanoseconds for polled samples, while keeping the timestamp identical for all samples polled during one cycle. Related-bug: #1527620 Change-Id: I40e14fb6aa595a86df9767be5758f52b7ceafc8f
Diffstat (limited to 'requirements.txt')
-rw-r--r--requirements.txt1
1 files changed, 1 insertions, 0 deletions
diff --git a/requirements.txt b/requirements.txt
index 51346d04..b714a918 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -12,6 +12,7 @@ jsonschema!=2.5.0,<3.0.0,>=2.0.0 # MIT
kafka-python>=1.3.2 # Apache-2.0
keystonemiddleware!=4.1.0,>=4.0.0 # Apache-2.0
lxml>=2.3 # BSD
+monotonic
msgpack-python>=0.4.0 # Apache-2.0
oslo.concurrency>=3.5.0 # Apache-2.0
oslo.config>=3.22.0 # Apache-2.0