[openstack-dev] [Horizon] [UX] Design for Alarming and Alarm Management
eglynn at redhat.com
Wed Jun 4 16:06:30 UTC 2014
Some thoughts on the wireframe doc:
* The description of form:
"If CPU Utilization exceeds 80%, send alarm."
misses the time-window aspect of the alarm definition.
Whereas the boilerplate default descriptions generated by
"cpu_util > 70.0 during 3 x 600s"
captures this important info.
* The metric names, e.g. "CPU Utilization", are not an exact
match for the meter names used by ceilometer, e.g. "cpu_util".
* Non-admin users can create alarms in ceilometer:
"This is where admins can come in and
define and edit any alarms they want
the environment to use."
(though these alarms will only have visibility onto the stats
that would be accessible to the user on behalf of whom the
alarm is being evaluated)
* There's no concept currently of alarm severity.
* "Should users be able to enable/dis-able alarms."
Yes, the API allows for disabled (i.e. non-evaluated) alarms.
* "Should users be able to own/assign alarms?"
Only admin users can create an alarm on behalf of another
* "Should users be able to acknowledge, close alarms?"
No, we have no concept of ACKing an alarm.
* "Admins can also see a full list of all Alarms that have
taken place in the past."
In ceilometer terminology, we refer to this as alarm history
or alarm change events.
* "CPU Utilization exceeded 80%."
Again good to capture the duration in that description of the
* "Within the Overview section, there should be a new tab that allows the
user to click and view all Alarms that have occurred in their environment."
Not sure really what "environment" means here. Non-admin tenants only
have visibility to their own alarm, whereas admins have visibility to
* "This list would keep the latest alarms."
Presumably this would be based on querying the alarm-history API,
as opposed to an assumption that Horizon is consuming the actual
----- Original Message -----
> Hi All,
> I’ve recently put together a set of wireframes around Alarm Management
> that would support the following blueprint:
> If you have a chance it would be great to hear any feedback that folks have
> on this direction moving forward with Alarms.
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
More information about the OpenStack-dev