Hi AFEK,
Sorry I was busy in other things and didn't pay much attention to Vitrage project(But I will do :) ), the notification message I metioned doesn't mean the notification based on "alarm_actions". currently, when a alarm's state changed, it will trigger the alarm actions specified in alarm definition, and also send a notification message about the alarm change to notification.info (default config value) meanwhile. thanks Liu sheng At 2015-12-03 00:31:05, "AFEK, Ifat (Ifat)" <ifat.a...@alcatel-lucent.com> wrote: >Hi, > >In Vitrage[3] project, we would like to be notified on every alarm that is >triggered, and respond immediately (e.g. by generating RCA insights, or by >triggering new alarms on other resources). We are now in the process of >designing our integration with AODH. > >If I understood you correctly, you want to remove the notifications to the >bus, but keep the alarm_actions in the alarm definition? >I'd be happy to get some more details about the difference between these two >approaches, and why do you think the notifications should be removed. > >[3] https://wiki.openstack.org/wiki/Vitrage > >Thanks, >Ifat. > > >> >> From: liusheng [mailto:liusheng1...@126.com] >> Sent: Tuesday, December 01, 2015 4:32 AM >> To: openstack-dev@lists.openstack.org >> Subject: [openstack-dev] [telemetry][aodh] The purpose of notification about >> alarm updating >> >> Hi folks, >> >> Currently, a notification message will be emitted when updating an alarm >> (state transition, attribute updating, creation), this > functionality was >> added by change[1], but the change didn't describe any purpose. So I wonder >> whether there is any usage of this >> type of notification, we can get the whole details about alarm change by >> alarm-history API. the notification is implicitly >> ignored by default, because the "notification_driver" config option won't be >> configured by default. if we enable this option in >> aodh.conf and enable the "store_events" in ceilometer.conf, this type of >> notifications will be stored as events. so maybe some >> users want to aggregate this with events ? what's your opinion ? >> >> I have made a change try to deprecate this notification, see [2]. >> >> [1] https://review.openstack.org/#/c/48949/ >> [2] https://review.openstack.org/#/c/246727/ >> >> BR >> Liu sheng > >__________________________________________________________________________ >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
