Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating
Hi Ifat, I am OK to abandon the change and keep notifications about alarm changes if you really need. the problem is if we enabled the notifications and if there are many alarms periodically evaluated and updated by aodh-evaluator, there will emit many these notification messages and will be stored as events in ceilometer, that may will disperse the events we really want. how about sending these notifications message on a different topic? that can avoid consuming by ceilometer-notification-agent. thanks Liu sheng At 2016-01-10 14:30:34, "AFEK, Ifat (Ifat)" <ifat.a...@alcatel-lucent.com> wrote: >Hi Julien, > >I'm a bit confused. This thread started by liusheng asking to remove the >notifications to the bus[1], and I replied saying that we do want to use this >capability in Vitrage. What is the notifier plugin that you suggested? Is it >the same notifier that liusheng referred to, or something else? > > >[1] https://review.openstack.org/#/c/246727/ > >Thanks, >Ifat. > >> -Original Message- >> From: Julien Danjou [mailto:jul...@danjou.info] >> Sent: Friday, January 08, 2016 11:42 AM >> >> On Thu, Jan 07 2016, AFEK, Ifat (Ifat) wrote: >> >> > We have two motivations: one is that we want to get notifications on >> > every change, but we don't want to register our webhook to each and >> > every alarm; and the other is that we already listen to the message >> > bus for other openstack components, so we would like to handle aodh >> the same way. >> > >> > If we disable aodh-notifier, won't it have other impacts on the >> > system? What if someone else used a webhook, and won't be notified >> > because we disabled the notifier? >> >> We could have a notifier plugin that would send a notification using >> oslo.messaging I guess. That shouldn't be a big deal. >> >> -- >> Julien Danjou >> ;; Free Software hacker >> ;; https://julien.danjou.info > >__ >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
[openstack-dev] [telemetry][ceilometer][aodh] Only support sql for alarm data
Hi operators and developers, We have support dedicated dabase for alarm data[1], that allow deployers to config ceilometer distributing alarm data to a separate database. And In liberty, we have splitted out the alarming service as a separate project Aodh from Ceilometer tree. Continue from Ceilometer implementation, we now support mongodb, Hbase, sqalchemy storage drivers for alarm data, but, we agree to deprecate the mongodb and Hbase support for alarm data and only keep sql. The reasons and advantages for this change have been described in the proposal[2]. we will deprecate them in this release cycle and try to provide data migration tool for migrating data from mongodb/Hbase to sql, and remove the mongodb and Hbase support in future O* cycle. For now, I want to confirm the effect about this change of your current deployment/products, appreciate your feedback. [1] https://blueprints.launchpad.net/ceilometer/+spec/dedicated-alarm-database [2] https://review.openstack.org/#/c/258283/2/specs/mitaka/only-support-sqlalchemy-in-aodh.rst Best regards 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
Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating
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
