<html><body>
<p><font size="2" face="sans-serif">In Kilo, with the bug fix from 1326721, I can create an alarm like the following with the "query" property. I use this alarm to monitor the health of a server instance in the pool. In juno/stable, without the query property, ceilometer alarms can only be created via heat with matching metadata. This limits the metrics I can create alarms for, as not every resource has metadata associated with it. </font><font size="2" face="sans-serif">Without this bug fix, I've been unable to find a way to monitor the health of my server in Juno via heat. </font><a href="https://review.openstack.org/#/c/146624/"><font size="2" face="sans-serif">I'd like thoughts on back porting 1326721 back to juno/stable, so this can be work the same as it does in Kilo</font><font size="2" color="#0000FF" face="sans-serif"> </font><font size="2" face="sans-serif">https://review.openstack.org/#/c/146624/</font></a><font size="2" face="sans-serif"> .Thanks</font><br>
<br>
<font size="2" face="Default San Serif">gone_alarm:<br>
type: OS::Ceilometer::Alarm<br>
properties:<br>
description: Detect server being unresponsive<br>
repeat_actions: False<br>
meter_name: network.services.lb.member<br>
statistic: avg<br>
period: 600<br>
evaluation_periods: 1<br>
threshold: 1<br>
alarm_actions: [ {get_attr: [restart, AlarmUrl]} ]<br>
query:<br>
- field: resource_id<br>
op: eq<br>
value: {get_resource: member}<br>
comparison_operator: lt</font><font size="3" face="serif"><br>
</font><font size="2" face="Default San Serif"><br>
member:<br>
type: OS::Neutron::PoolMember<br>
properties:<br>
pool_id: {get_param: pool_id}<br>
address: {get_attr: [server_node, first_address]}<br>
protocol_port: { get_param: loadbalance_port }</font><font size="3" face="serif"><br>
</font><br>
<br>
<font size="2" face="sans-serif">Karolyn Chambers</font></body></html>