My present employer is just starting with Openstack and we aren't using Ceilometer yet, but when I was at eBay we had a whole team trying to make it work and it was still terrible. I was very happy when I heard that the shitty old ceilometer was going away and would never be heard from again. As an operator, I want to see a clear path forward; a path that does not include going back to something that never worked properly.
If there's a choice between doing it the "right" way, and doing something easier, we all know that doing it the "right" way will be easier in the long run.
From: Thierry Carrez <thierry at openstack.org>
Sent: Tuesday, December 17, 2019 3:14 AM
To: openstack-discuss at lists.openstack.org
Subject: Re: [Telemetry][TC]Telemetry status
I'd like to hear from more Ceilometer users. What are they using
Ceilometer for, and what long-term plans would be acceptable. There is a
trade-off between adopting short-term workarounds that reintroduce
performance issues vs. undergoing a complex migration to the "right" way
of fixing this. Like for example there is little point in pushing
Monasca/Ceilometer stack integration if most users say, like Catalyst
Cloud seems to say, that they would rather have a slow performing
Ceilometer API back.