Valery Piashchynski

> why is config there? It's just a placeholder for GitHub, which means, that value should be taken from the config.

@ohDaddyPlease Let me explain, it's my bad :) We extend the `http` section in the `.rr.yaml` (which is located in the root). You need to add, right after the `http`...

@ohDaddyPlease Do you have any plans to work on this ticket?

> 1. The metric for Situation 1 should show the current queue size (0 if no request queuing is happening). It's possible. I moved http metrics to the middleware, so,...

DDoS doesn't relate to this in any way. This is a task for the LB to filter requests, apply a circuit breaker to prevent application DDoS. > "too few free...

Important note - I'm not against your proposal, the general idea was proposed by other people as well and I agree to do that. But at the moment we have...

> What about autoscaling? This is also not a RR issue. RR can't autoscale and this is a DevOps task. > I never mentioned a DDoS. I said "DoS condition"...

> I agree, but to set up autoscaling, a DevOps needs feedback from the application server, preferably in the form of resource metrics (though indirect indicators like CPU load may...

> Is there a gauge somewhere internally in RR with a number of free workers? Or a number of free workers / num_workers? Or busy_workers/free_workers? There are no particular numbers,...

> +1 for exposing number of free/busy workers. It would allow to scale in advance, if there is some I/O blocking in workers, and they all become busy. No +1...