actions / actions/actions-runner-controller
`metrics-server`: maxScrapeSize and increasing BodySize
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
A way to configure maxBodySize for /metrics endpoint in metrics-server.
Why is this needed?
We faced an issue when body with metrics became > 70mb. Old data is not deleted, so with each new action run size is growing. it would be nice to have ability to set maxBodySize and rotate body if it exceeds the limit.
the response from "http://xx.xx.xx.xx:8080/metrics" exceeds -
promscrape.maxScrapeSize=33554432 (the actual response size is
73898063 bytes); either reduce the response size for the target or increase - promscrape.maxScrapeSize
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 tracing the metrics-server /metrics endpoint in actions-runner-controller and reviewing how metric data is retained across action runs. Determine where a configurable max body size and rotation would belong; done means the endpoint honors the configured limit without unbounded growth and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, go, kubernetes
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100