[openstack-dev] 答复: Re: [vitrage][aodh] about aodh notifier to create a event alarm
dong.wenjuan at zte.com.cn
dong.wenjuan at zte.com.cn
Wed Oct 19 06:21:25 UTC 2016
Hi All,
The BP of aodh-message-bus-notifications[1] was blocked as Aodh message
bus notification.
As the discuession of Vitrage and Aodh in etherpad[2], only the Aodh
alarm_deletion notification is missing.
I proposed a patch to add the Aodh alarm_deletion notification.[3]
Please help me to review this patch.
Do the alarm.creation, alarm.state_transition and alarm.deletion satisfy
the Vitrage requirement?
I'd like to help to implement the aodh-message-bus-notifications BP if
there is nobody interest in it.
About the Aodh custon alarm:
What about the alarm type as `prompt` or something else like this, which
means the alarm
is fired with no evaluation. And the metedata include the `source_id`
means which source
the alarm is on?
Let me know if you have some good ideas.
Thanks,
[1]https://blueprints.launchpad.net/vitrage/+spec/aodh-message-bus-notifications
[2]https://etherpad.openstack.org/p/newton-telemetry-vitrage
[3]https://review.openstack.org/#/c/387754/
BR,
dwj
"Afek, Ifat (Nokia - IL)" <ifat.afek at nokia.com>
2016-10-13 17:31
请答复 给
"OpenStack Development Mailing List \(not for usage questions\)"
<openstack-dev at lists.openstack.org>
收件人
"OpenStack Development Mailing List (not for usage questions)"
<openstack-dev at lists.openstack.org>
抄送
主题
Re: [openstack-dev] [vitrage][aodh] about aodh notifier to create a event
alarm
Hi dwj,
Thanks for bringing this up.
Aodh notifier plugin inside Vitrage is defined as a POC, and is disabled
by default. We are aware that this integration is not working well, and
its purpose was to demonstrate how it could work and start a discussion
about other possible implementations. I know that in Austin there were
discussions between Aodh and Vitrage teams, and a general agreement that
Vitrage would suggest a design for Aodh custom alarm. Such an alarm could
then be used by Vitrage instead of the event-alarm in a more natural way.
Unfortunately, due to time limitations, we did not get to write the custom
alarm blueprint in Aodh. It is still defined as a high priority in Vitrage
roadmap, and I hope it will happen in Ocata. If you have some free time
you are more than welcome to give a hand :-)
Best Regards,
Ifat.
From: "dong.wenjuan at zte.com.cn"
Date: Thursday, 13 October 2016 at 04:20
Hi vitrages,
In aodh notifier plugin, we receive a ACTIVATE_DEDUCED_ALARM_EVENT and
then create a aodh event alarm.
The event alarm with a `event_rule`, it should be include `event_type` and
`query` which Aodh used to evaluator
a alarm when it receives a specify event to filter with the query to fire
a alarm. see [1]
But we create a event alarm only with `query` in `event_rule`.
The deduced alarm create with the `alarm` state so Aodh will skip to
evaluator the fired alarm.
The `event_rule` seems no necessary in the request body, am I right?
Let me know if i miss something. :)
[1]
https://github.com/openstack/aodh/blob/master/doc/source/event-alarm.rst
BR,
dwj
董文娟 Wenjuan Dong
控制器四部 / 无线产品 Controller Dept Ⅳ. / Wireless Product Operation
上海市浦东新区碧波路889号中兴通讯D3
D3, ZTE, No. 889, Bibo Rd.
T: +86 021 85922 M: +86 13661996389
E: dong.wenjuan at zte.com.cn
www.ztedevice.com
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161019/427d04b9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 6015 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161019/427d04b9/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 900 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161019/427d04b9/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ATT00001.gif
Type: image/gif
Size: 6015 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161019/427d04b9/attachment-0002.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ATT00002.gif
Type: image/gif
Size: 900 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20161019/427d04b9/attachment-0003.gif>
More information about the OpenStack-dev
mailing list