benediktarnold commented on issue #282:
URL: https://github.com/apache/solr-operator/issues/282#issuecomment-880044518
> Maybe one solution is to add an actual health-check handler to the
PrometheusExporter itself (in Solr), that just checks that the metrics cache is
healthy, and the jetty server responds.
That seems to be a good idea. I'll look into the code and will come up with
a PR or at least an issue in the solr repo.
> A second question, what version of the prometheus exporter are you using?
It seems weird to me that additional calls to `/metrics` would be that
expensive, given that all the metrics _should_ be cached in the first place.
Maybe it's very expensive to generate the long response?
I thought so as well. I'm using the exporter that comes with the solr 8.7.0
Images. I'm about to upgrade to 8.9.0 and I'll let you know if that brings any
advantages. I made a snapshot of a metric response once and it was about 24MB
(~100 small collections on 3 solr nodes). The peak CPU usage of the exporter is
far bigger than the CPU usage of my whole solr cluster.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
