Open Stack

sorry, my email was blocking the list for a bit so i missed this.

the original reason this was implemented i believe was to track alarm 
state changes as an event in ceilometer events. i still see this as a 
valid use case but it does duplicate some of the functionality of alarm 
history.

i think the main items are to not flood the message bus with messages 
that no one is listening to. but if there is a use case for it, i'm 
happy to see it remain (and improved).

you can check the patch that Liusheng referenced, but the basic concept 
is as mentioned: send message when an alarm state is changed.

cheers,

-- 
gord