Hello,
thank you very much for the feedback.
Ok, I have tried to go through the triggers an events.
Let me summarize, so we can confirm I understand it correctly:
==
The trigger:
--
- has a pattern - that is something like starting condition,
On 09/25/2013 01:51 AM, Gabriel Hurley wrote
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
On Tue, Sep 24 2013, Ladislav Smola wrote:
Well for example, if we find metrics, that can be used for measuring health
(this is probably more undercloud talking, or hardware metrics in general),
we could do something like I want this alarm on all resources of this
type,
if there will be e.g.
On Tue, Sep 24 2013, Ladislav Smola wrote:
Yes it would be good if something like this would be supported. -
relation of alarm to multiple entities, that
are result of sample-api query. Could it be worth creating a BP?
Probably indeed.
--
Julien Danjou
# Free Software hacker # independent
I think Dragon's BP for notification triggers would solve this problem.
Instead of looking at it as applying a single alarm to several resources,
you could instead leverage the similarities of the resources:
https://blueprints.launchpad.net/ceilometer/+spec/notifications-triggers.
Compound that
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
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
