Open Stack

On Thu, Sep 19 2013, Ladislav Smola wrote:

Hi Ladislav,

Sorry for the late reply,

> 1. The points 1-4 from are some sort simple version of the page, that uses
> all basic alarm-api features. Do you think we need them all? Any feedback
> for them? Enhancements?

That looks like a really good start if we can have all of this!

> 2. There is a thought, that we should maybe divide Alarms into (System,
> User-defined). The only system alarms now, are set up with Heat and used for
> auto-scaling.

I don't think there is any formal way to distinguish alarms. Though it's
likely you can retrieve the alarm list Heat created for the user to
distinguish them.
On the other hand, I am not sure the user can see the alarms created by
Heat since they might not directly belong to the user, but to Heat.

> 3. There is a thought about watching correlation of multiple alarm histories
> in one Chart (either Alarm Histories, or the real statistics the Alarm is
> defined by). Do you think it will be needed? Any real life examples you have
> in mind?

I think the first use case is to debug combined alarms.
There's also a lot of potential to debug an entire platform activity by
superimposing several alarm graphs.

> 4. There is a thought about tagging the alarms by user defined tag, so user
> can easily group alarms together and then watch them together based on their
> tag.

The alarm API don't provide that directly, but you can imagine some sort
of filter based on description matching some texts.

> 5. There is a thought about generating a default alarms, that could observe
> the most important things (verifying good behaviour, showing bad behaviour).
> Does anybody have an idea which alarms could be the most important and
> usable for everybody?

I'm not sure you want to create alarm by default; alarm are resources, I
don't think we should create resources without the user asking for it.

Maybe you were talking about generating alarm template? You could start
with things like CPU usage staying at >90% for more than 1 hour, and
having an action that alerts the user via mail.
Same for disk usage.

> 6. There is a thought about making overview pages customizable by the users,
> so they can really observe, what they need. (includes Ceilometer statistics
> and alarms)

I think that could be as easy as picking the alarms you want in
overviews with a very small and narrowed graph.

-- 
Julien Danjou
/* Free Software hacker * independent consultant
   http://julien.danjou.info */
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130923/60060cfc/attachment.pgp>