Re: [openstack-dev] [Ceilometer][Aodh] event-alarm fire policy
Just a personal thought, can we add an ACK to alarm notifier? when an event-alarm fired, the alarm state transformed to "alarm", if 'alarm_action' has been set, the 'alarm_action' will be triggered and notify. for event-alarm, a timout can be set to wait the ACK from alarm notifier, if the ACK recieved, reset the alarm state to OK, if timeout occured, set the alarm state to 'UNKNOWN'. If 'alarm_action' has not been set, we just need to recored the alarm state transition history. 在 2015/9/8 7:26, Zhai, Edwin 写道: All, Currently, event-alarm is one-shot style: don't fire again for same event. But threshold-alarm is limited periodic style: 1. only get 1 fire for continuous valid datapoints. 2. Would get a new fire if insufficient data followed by valid ones, as we reset alarm state upon insufficient data. So maybe event-alarm should be periodic also. But I'm not sure when to reset the alarm state to 'UNKNOWN': after each fire, or when receive different event. Fire a bug @ https://bugs.launchpad.net/aodh/+bug/1493171 Best Rgds, Edwin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Ceilometer][Aodh] event-alarm fire policy
Liusheng, Thanks for your idea. I think it guarantees alarm action got called. But I just want it fired upon each matching event. E.g. for each instance crash event. Have talked with MIBU, repeat-actions can be used for this purpose. Best, Edwin On Tue, 8 Sep 2015, liusheng wrote: Just a personal thought, can we add an ACK to alarm notifier? when an event-alarm fired, the alarm state transformed to "alarm", if 'alarm_action' has been set, the 'alarm_action' will be triggered and notify. for event-alarm, a timout can be set to wait the ACK from alarm notifier, if the ACK recieved, reset the alarm state to OK, if timeout occured, set the alarm state to 'UNKNOWN'. If 'alarm_action' has not been set, we just need to recored the alarm state transition history. 在 2015/9/8 7:26, Zhai, Edwin 写道: All, Currently, event-alarm is one-shot style: don't fire again for same event. But threshold-alarm is limited periodic style: 1. only get 1 fire for continuous valid datapoints. 2. Would get a new fire if insufficient data followed by valid ones, as we reset alarm state upon insufficient data. So maybe event-alarm should be periodic also. But I'm not sure when to reset the alarm state to 'UNKNOWN': after each fire, or when receive different event. Fire a bug @ https://bugs.launchpad.net/aodh/+bug/1493171 Best Rgds, Edwin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev Best Rgds, Edwin__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Ceilometer][Aodh] event-alarm fire policy
All, Currently, event-alarm is one-shot style: don't fire again for same event. But threshold-alarm is limited periodic style: 1. only get 1 fire for continuous valid datapoints. 2. Would get a new fire if insufficient data followed by valid ones, as we reset alarm state upon insufficient data. So maybe event-alarm should be periodic also. But I'm not sure when to reset the alarm state to 'UNKNOWN': after each fire, or when receive different event. Fire a bug @ https://bugs.launchpad.net/aodh/+bug/1493171 Best Rgds, Edwin __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
