prometheus / prometheus/client_ruby
slow response on metrics http endpoint
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 558
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
Hi people,
I use The Foreman in version 2.0.0. That version bundles the prometheus-client gem in version 1.0.0. A simple call to the /metrics endpoint takes 60 to 75 seconds. I raised in issue for that already at the foreman project: https://projects.theforeman.org/issues/30029
They advised me to create an issue here as well. I'm not really sure how I should debug this. The whole stack runs on a dedicated server with CentOS 7. I don't see any CPU/IO peaks.
I'm aware of the fact that those information aren't really useful to debug the issue. Can you please tell me which infos you need / how I should debug this? I'm happy to debug this for you or discuss it in any chat.
Cheers, Tim
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the linked Foreman issue 30029 and reproducing a request to the /metrics endpoint with Foreman 2.0.0 and prometheus-client 1.0.0 on CentOS 7. Collect the debugging information needed to explain the 60–75 second response, then document the cause and a reproducible result or next debugging step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- prometheus, ruby
- Domain
- observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100