ygk12345
Cadet
Cadet
  • 316 Views

How to interpret the openstack metric measures

Hi,

How to correctly interpret the measures of a metric in telemetry in openstack. I am finding it hard to corelate the figures returned by the measures command and the archive policy it denotes. 

Labels (1)
0 Kudos
2 Replies
philip_sweany
Flight Engineer Flight Engineer
Flight Engineer
  • 300 Views

Re: How to interpret the openstack metric measures

The archive policy defines how the incoming data metrics are aggregated.  All incoming metrics that occur with the "granularity"  amount of time are store in a single value in the database, which could be an avergae, minimum., maximum, sum. etc, based on your configuration, and also how long to store the data before it is automatically deleted.  The default archive policies are listed in the table attached as an image.Screen Shot 2020-07-08 at 11.56.47 AM.png

These are just default policies for aggregation.  You could make new policies, but you could also moidify those defaults to do somethig different.  Better to make your own and leave the defaults.

0 Kudos
Reply
Loading...
ygk12345
Cadet
Cadet
  • 292 Views

Re: How to interpret the openstack metric measures

Thanks for the response. My observation doesn't seem to corelate to the granularity definition of 'high' archive policy. For example, consider the following snippet from the doc.

--------

[student@workstation ~(developer1-finance)]$ openstack metric measures show \
--resource-id 8e8ca3d6-6b1c-4a97-a242-ec8549f6628e \
disk.read.requests.rate
+---------------------------+-------------+---------------+
| timestamp | granularity | value |
+---------------------------+-------------+---------------+
| 2018-07-04T10:30:00+05:30 | 3600.0 | 0.00166716985 |
| 2018-07-04T10:42:00+05:30 | 60.0 | 0.0016675937 |
| 2018-07-04T10:52:00+05:30 | 60.0 | 0.001666746 |
| 2018-07-04T10:42:50+05:30 | 1.0 | 0.0016675937 |
| 2018-07-04T10:52:50+05:30 | 1.0 | 0.001666746 |
+---------------------------+-------------+---------------+
Observe the value column, which displays the aggregated values based on archive
policy associated with the metric. The 3600, 60, and 1 in the granularity column
values represent the aggregation periods of 1 day, 1 hour, and 1 minute, respectively

----------------------- 

In the above output, what exactly does '3600' . '60, '1.0' represent. If I assume , 60 as one minute interval for collecting data, why is the timestamp showing 10 minute gap between the two '60.0'  timestamps ? (10:42:00+05:30,  10:52:00+05:30)  ? So my bigger questoin is how to interpret the above measures according to the following 'high'  archive policy definition ?

---------------

| high | - points: 3600, granularity: 0:00:01, timespan: 1:00:00 |
| | - points: 10080, granularity: 0:01:00, timespan: 7 days, 0:00:00 |
| | - points: 8760, granularity: 1:00:00, timespan: 365 days, 0:00:00 |

------------------

Hope this makes my question clear to you.

0 Kudos
Reply
Loading...
Join the discussion
You must log in to join this conversation.