2 ms·
Well, my GitLab instance at some point started to have its Prometheus eat 100% CPU all the time until I disabled the Prometheus component altogether, so there’s
by oefrha 5y ago
Well, my GitLab instance at some point started to have its Prometheus eat 100% CPU all the time until I disabled the Prometheus component altogether, so there’s that. A cursory glance at the tracker just now says the issue is still open. That’s the kind of problems you get for self-hosting, it’s not all rainbows and unicorns.
- dnsmichi 5y agoHi, Developer Evangelist at GitLab here. Can you link the issue please? :) For context, Prometheus and observability will be handled with Opstrace in the future [0]. I'd like to learn about your use-case and see which troubles you have been running into. Thanks! [0] https://opstrace.com/blog/gitlab https://opstrace.com/blog/gitlab
- oefrha 5y agoThis one I guess? https://gitlab.com/gitlab-org/gitlab/-/issues/210365 https://gitlab.com/gitlab-org/gitlab/-/issues/210365 To be clear, I don't care about Prometheus on my instance, I only care when it's causing trouble (e.g. by eating 100% CPU all the time).
- dnsmichi 5y agoThanks for the URL, and the additional context. Appreciate it. :)