we dropped Ceilometer as the core tool to gather metrics for our rating and
billing system. I must admit it has improved, but I think it's broken by
design: a metering and monitoring system is not the same thing.
We have built a component that directly listens from rabbit notification
tools (a-la-Stacktach). This tool stores the all events in a database (but
anything could work, it's just a logging system) and then we process these
events and store them in a datamart style database every hour. The rating
and billing system reads this database and process it every hour too. We
decided to implement this pipeline processing of data because we knew in
advance that processing such an amount of data was a challenge.
I think Ceilometer should be used just to trigger alarms for heat for
example, and something else should be used for rating and billing.
*www.stackops.com | * firstname.lastname@example.org |
+34 91 005-2164 | skype:diegoparrilla
On Wed, Feb 11, 2015 at 8:37 PM, Maish Saidel-Keesing email@example.com
Is Ceilometer ready for prime time?
I would be interested in hearing from people who have deployed OpenStack
clouds with Ceilometer, and their experience. Some of the topics I am
looking for feedback on are:
- Database Size
- MongoDB management, Sharding, replica sets etc.
- Replication strategies
- Database backup/restore
- Overall useability
- Gripes, pains and problems (things to look out for)
- Possible replacements for Ceilometer that you have used instead
If you are willing to share - I am sure it will be beneficial to the whole
Thanks in Advance
With best regards,
OpenStack-operators mailing list
OpenStack Development Mailing List (not for usage questions)