Sebastian Osorio

any update about Prometheus?

Thanks @padiazg it works!

Prometheus operator

Same here! I checked the metrics and panel is link to *node_cpu* metric which is not available in my Prometheus, 

I would say it depends on your Prometheus configuration. Definitely the metrics had change and now you must use the new names, however, depends on your configuration you will get...

we are having the same issue and nothing helps. Any idea?

@crenshaw-dev at this point the entire cluster is stuck, most of the apps keep on "refreshing" mode so, I haven't been able to pin point exactly which is the application...

Thanks for your answer . it's nowhere in the yaml, I'm using **Argo v2.5.5** Do you know if it might be enforced somehow via code ? @crenshaw-dev

@crenshaw-dev It's seems that it's not CPU related issue . Additionally I found out that this is the api call that is taking "forever" to respond **https://argocdxxxx/api/v1/stream/applications/my-app-name/resource-tree?appNamespace=argocd** and in some...

hey I found my issue. In the end was nothing related to Argocd , the Kubeapi was overfload with thousands of requests generated by certmanager and ofc Argocd was trying...