Closed gabrielcocenza closed 2 months ago
Once merged, please be sure to update the charmhub docs ( https://charmhub.io/openstack-exporter ):
@samuelallan72 I've created a new issue #78 to track that.
Should we change the documentation after reaching the stable release?
@jneo8
question(non-blocking): I kind of lose why we want to enable cache as default, the upstream exporter default is false.
The motivation behind it it's because the scrape was failing, at least on serverstack (I didn't try on partner cloud or other environment that is more realistic with production) and it's not a good user experience to try to figure out why it's not working. Having it set to True we kind guarantee that will start working out of the box
The motivation behind it it's because the scrape was failing, at least on serverstack (I didn't try on partner cloud or other environment that is more realistic with production) and it's not a good user experience to try to figure out why it's not working. Having it set to True we kind guarantee that will start working out of the box
My concern is about the meaning of the metrics become a little bit different after you open the cache. This is also a major concern from others so we decide to not enable it as default and provide the same experience as upstream.
I am ok to enable cache as default, if there are more concern from others then we can discuss if we want to set it back.
Having the cache option set to True will make the exporter work out of the box. Right now if not changed, the time to scrape is bigger than 10 seconds and it fails.