Problem with Limit - http_max_conns_per_client
- Dominant language
- Go
- Stars
- 30.1k
- Forks
- 4.6k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 39
Description
Hi guys. This is not a Bug, I wanted to make an issue because I need some help!
For my BA research project I'm doing some testing with an application running in consul with mTLS configured.
I'm running gattling tests with 200 concurrent users. But in the graphs I can see that there is a limit on open connections per client.
I'm installing consul with helm and I also use Grafana and Prometheus, they are also installed with Helm charts.
How can I change the http_max_conns_per_client value?
Contributor guide
Research direction
Start by tracing how the Consul Helm deployment exposes the http_max_conns_per_client setting, then check the existing Consul and Helm documentation for the relevant configuration entry point. Done should be a clear, verified explanation of how to change the value in this deployment context.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana, helm, kubernetes, prometheus
- Domain
- cloud, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100