Add the function of deleting alarm history¶
Currently the ceilometer-expirer doesn’t delete expired AlarmChanges. Remained AlarmChanges would be cause of wasted disk-space and slow response. This blueprint adds the function of deleting alarm history.
Currently the ceilometer-expirer doesn’t delete expired AlarmChanges. So we need to add the function of deleting alarm history.
For doing so, a time-to-live (TTL) value needs to be specified. Currently the metering_time_to_live (aka time_to_live) value is used for deleting metering data. However, alarm history expirations shouldn’t be the same frequency as sample expiration.
Therefore, separate TTL value needs to be introduced for alarm history.
Add the function of deleting alarm history. This functionality will be put into the ceilometer-expirer.
New TTL, alarm_history_time_to_live, is added as a config option to database section.
It is possible to use the same time_to_live value for both sample and alarm history.
However their scale might be completely different, so the expiration frequency shouldn’t be the same.
Therefore, we will have separate TTL.
Data model impact¶
REST API impact¶
Other end user impact¶
Other deployer impact¶
A new option should be set if deployer wants to enable this feature.
- Primary assignee:
- Other contributors:
- Ongoing maintainer:
“alarm_history_time_to_live” is added as a config option.
support mongodb back end
support sqlalchemy back end
This code will be tested in unit tests for expire.
 bug report that addresse this issue https://bugs.launchpad.net/ceilometer/+bug/1289141
 ongoing patch for  https://review.openstack.org/#/c/87869/