Ask Your Question

Revision history [back]

I had the similar issue

aodh alarm show cpu-high
| evaluation_periods        | 1
| granularity               | 600
| query                     | {"and": [{"or": [{"=": {"created_by_project_id": "eaf4d8ec028c4027b02d8c67b7565d61"}}, {"and": [{"=": {"created_by_project_id": "c0580563e514461f906be948d99afe46"}}, {"=": {"project_id": "eaf4d8ec028c4027b02d8c67b7565d61"}}]}]}, {"=": {"display_name": "ub-node"}}]} |
| repeat_actions            | False

At the same time:

gnocchi measures aggregation -m cpu_util --query "project_id='eaf4d8ec028c4027b02d8c67b7565d61' and display_name='ub-node'" --resource-type instance --start 2019-02-19T18:30:00+03:00
+---------------------------+-------------+----------------+
| timestamp                 | granularity |          value |
+---------------------------+-------------+----------------+
| 2019-02-19T18:30:00+03:00 |       300.0 |  99.8654217781 |
| 2019-02-19T18:35:00+03:00 |       300.0 |  99.8822001703 |
| 2019-02-19T18:40:00+03:00 |       300.0 |  99.8669754688 |
| 2019-02-19T18:45:00+03:00 |       300.0 |  92.7373500072 |
| 2019-02-19T18:50:00+03:00 |       300.0 |  66.6870052248 |

I did not see any errors in Aodh logs

But during I was writing this post, I found out solution =)

The pretty important: The alarm granularity must match the granularities of the metric configured in Gnocchi.

As I see, you set granularity:60, check you granularity in gnocchi