© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
There are two contributing factors here. First, this is just the nature of a distributed asynchronous system. We can't be sure what order the data is generated or received, so the precision we have for "latest" is vague.
The second cause of many samples with the same timestamp is the fact that a single notification event is converted into several different samples. It is almost always necessary to restrict queries by meter name to get meaningful results.