[openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating
gord at live.ca
Mon Jan 11 12:53:49 UTC 2016
so one point i should mention is that the notification we propose on
removing was originally attended for Ceilometer events. much in same way
as disabling the aodh-notifier to allow Vitrage to consume alarm
triggers, it isn't exactly safe for Vitrage to consume the existing
messages as Ceilometer may also consume it.
the idea with moving it to a discrete notifier (whether zaqar or plain
oslo.messaging) is so the consumer of message is explicit.
On 10/01/2016 1:30 AM, AFEK, Ifat (Ifat) wrote:
> Hi Julien,
> I'm a bit confused. This thread started by liusheng asking to remove the notifications to the bus, 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?
>  https://review.openstack.org/#/c/246727/
>> -----Original Message-----
>> From: Julien Danjou [mailto:julien at 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-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev