Hi Ryota, > -----Original Message----- > From: Ryota Mibu [mailto:r-m...@cq.jp.nec.com] > Sent: Tuesday, December 08, 2015 11:17 AM > > In short, 'event' is generated in OpenStack, 'alarm' is defined by a > user. 'event' is a container of data passed from other OpenStack > services through OpenStack notification bus. 'event' and contained data > will be stored in ceilometer DB and exposed via event api [1]. 'alarm' > is pre-configured alerting rule defined by a user via alarm API [2]. > 'Alarm' also has state like 'ok' and 'alarm', and history as well. > > [1] > http://docs.openstack.org/developer/ceilometer/webapi/v2.html#events- > and-traits > [2] http://docs.openstack.org/developer/aodh/webapi/v2.html#alarms > > > The point is whether we should use 'event' or 'alarm' for all failure > representation. Maybe we can use 'event' for all raw error/fault > notification, and use 'alarm' for exposing deduced/wrapped failure. > This is my view, so might be wrong. >
I believe Vitrage should define alarms, as we want the alarm to have a state and history (that can be queried in horizon UI). Moreover, in the future I can imagine that some other OpenStack services might want to add their alarm actions to the alarms that Vitrage generated. I think this applies both for Vitrage deduced alarms, and for alarms that Vitrage generated as a result of Nagios test failures for example. Does that make sense? Best Regards, Ifat. __________________________________________________________________________ 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
