Re: ceph-mgr perf throttle-msgr - what is caused fails?
As I said before, currently Prometheus module performance degradation is only one _visible_ issues. I named things like is as indicator (of feature problem's) k Sent from my iPhone
On 12 Sep 2024, at 23:18, Eugen Block <eblock@nde.ag> wrote:
But did you notice any actual issues or did you just see that value being that high without any connection to an incident?
I remember having a prometheus issue quite some time ago, it couldn't handle 30 nodes or something, not really a big cluster. But we needed to increase the polling time. Have you tried increasing mgr/prometheus/scrape_interval to 30 seconds or so? Zitat von Konstantin Shalygin <k0ste@k0ste.ru>:
As I said before, currently Prometheus module performance degradation is only one _visible_ issues. I named things like is as indicator (of feature problem's)
k Sent from my iPhone
On 12 Sep 2024, at 23:18, Eugen Block <eblock@nde.ag> wrote:
But did you notice any actual issues or did you just see that value being that high without any connection to an incident?
Hi, Increasing this value to 30 is the only thing I could do at the moment k Sent from my iPhone
On 13 Sep 2024, at 16:49, Eugen Block <eblock@nde.ag> wrote:
I remember having a prometheus issue quite some time ago, it couldn't handle 30 nodes or something, not really a big cluster. But we needed to increase the polling time. Have you tried increasing mgr/prometheus/scrape_interval to 30 seconds or so?
participants (2)
-
Eugen Block
-
Konstantin Shalygin