Difference between revisions of "Ceilometer/blueprints/alarm-audit-api-group-by"
(Support of aggregate queries ove multiple alamrs for Alarm Audit API) |
(→The user stories) |
||
| Line 2: | Line 2: | ||
* User wants health chart of nova instances (health is represented by number of alerts) | * User wants health chart of nova instances (health is represented by number of alerts) | ||
| − | Each instance is represented by number of alerts in given time period. | + | - Each instance is represented by number of alerts in given time period. |
| − | Instances can be grouped by metadate resouce_id, meter_names and other alarm attributes (all needs to be saved in Alarm event, so the change of Alarm won't affect it). | + | - Instances can be grouped by metadate resouce_id, meter_names and other alarm attributes (all needs to be saved in Alarm event, so the change of Alarm won't affect it). |
| − | Instanced can be queried by regular ceilometer query, also by a state transition (user is interested only in transitions to 'alarm' states) | + | - Instanced can be queried by regular ceilometer query, also by a state transition (user is interested only in transitions to 'alarm' states) |
Result will be something like | Result will be something like | ||
| Line 53: | Line 53: | ||
Instead of resource ID in the query, there will be a project ID. | Instead of resource ID in the query, there will be a project ID. | ||
For making this work also for Alarms defined for resource ID. Alarm for resource would have to always contain also a Project. | For making this work also for Alarms defined for resource ID. Alarm for resource would have to always contain also a Project. | ||
| − | |||
== API definition == | == API definition == | ||
Revision as of 15:44, 12 September 2013
The user stories
- User wants health chart of nova instances (health is represented by number of alerts)
- Each instance is represented by number of alerts in given time period.
- Instances can be grouped by metadate resouce_id, meter_names and other alarm attributes (all needs to be saved in Alarm event, so the change of Alarm won't affect it).
- Instanced can be queried by regular ceilometer query, also by a state transition (user is interested only in transitions to 'alarm' states)
Result will be something like
[ {
'resource_id': 'x',
'meter_name':' y',
'count' => 'z',
'timestamp'...
}
, ... ]
- it was grouped by resource_id an meter_name, but I could group by only by resource_id
- User wants to display a health of multiple instances in time line
Same as 1. but it would be grouped by time ( limit )
Result would be something like this
[[ {
'resource_id': 'x',
'meter_name':' y',
'count' => 1,
'timestamp'...
},
{'resource_id': 'x',
'meter_name':' y',
'count' => 2,
'timestamp'...
}]
,
[{
'resource_id': 'x2',
'meter_name':' y',
'count' => 3,
'timestamp'...
},
{'resource_id': 'x2',
'meter_name':' y',
'count' => 4,
'timestamp'...
}], ...]
- User wants to see health map of projects
Instead of resource ID in the query, there will be a project ID. For making this work also for Alarms defined for resource ID. Alarm for resource would have to always contain also a Project.
