] [Ceilometer][AODH] Timeout Event Alarms
Hi,
Maybe the event transformer is needed in some use cases to generate new
events or do transformations like the samples
handling. but for this timeout event alarming requirement, the
'timeout' of alarms will be various, it not a good idea
Gordon thanks for quick answer.
I'll add a patch with new dir for mitaka specs and move my specs there.
cheers,
Igor Degtiarov
Software Engineer
Mirantis Inc.
www.mirantis.com
On Mon, Aug 17, 2015 at 7:02 PM, gord chung g...@live.ca wrote:
good questions...
On 17/08/2015 10:19 AM, Igor
good questions...
On 17/08/2015 10:19 AM, Igor Degtiarov wrote:
Gordon probably that question to you:
Are we going to create a new folder in spec's dir for next cycle, or
we continue discussing new specs as part of liberty?
we can create a new dir for M* cycle specs. as mentioned in last
-dev] [Ceilometer][AODH] Timeout Event Alarms
Hi,
Maybe the event transformer is needed in some use cases to generate new
events or do transformations like the samples
handling. but for this timeout event alarming requirement, the 'timeout' of
alarms will be various, it not a good idea
Hi folks,
On our meatup we agreed to add timeout event alarms [1](Event-Base Alarming
part).
In ToDo task Сhoose the optimal way for timeout alerting implementation
Now we have two proposition for implementation:
- first is to add timeout param in event pipeline (transformer part)
[2]
--
Hi,
Maybe the event transformer is needed in some use cases to generate new
events or do transformations like the samples handling. but for this
timeout event alarming requirement, the 'timeout' of alarms will be
various, it not a good idea of changing event_pipeline.yaml to generate
new
hi Igor,
i would suggest you go with second option as i believe your
implementation will overlap and reuse some of the functionality Ryota
would code for his alarm spec [1]. also, since Aodh is working on an
independent release cycle, it'll give you some more time as i don't
think we'd be
