Hello We recently transitioned from ‘legacy’ Ceilometer to Ceilometer+AODH+Gnocchi in our Mitaka cloud. One thing I noticed is that the alarm-action HTTP POSTs don’t seem to contain data about the alarm. In our old config, we used to receive information like this from the POST from Ceilometer’s alarm notifier:
<QueryDict: {"severity": "low”, "alarm_name": "cpu_high”, "current": "alarm”, "alarm_id": "70d5faff-2062-4bb1-bcbc-3f389fb9c6dc”, "reason": "Transition to alarm due to 2 samples outside threshold, most recent: 116.628333333", "reason_data": {"count": 2, "most_recent": 116.62833333333332, "type": "threshold", "disposition": "outside"}, "previous": "ok"} }> The POSTs that come from the AODH notifier look like this: <QueryDict: {}> The AODH notifier log about the alarm shows: 2017-04-04 08:22:15.151 64223 INFO aodh.notifier.rest [-] Notifying alarm clubo:cpu_low c97e05ad-d85c-464f-8026-765c372fdce5 with severity low from alarm to alarm with action SplitResult(scheme=u'https', netloc=u'XXX', path=u'/api/scaling/remove/XXX/', query='', fragment='') because Remaining as alarm due to 1 samples outside threshold, most recent: 9.59306036578. request-id: req-e676dab8-664a-4891-af69-2a2753e1a65d Is this expected? Is there a way to configure AODH to include this type of information in it’s POST payload for the alarm-actions? Thanks, Mike Smith Lead Cloud Systems Architect Overstock.com<http://overstock.com>
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack