Effort involved in monitoring http connection pools?

[kjorg50]

Hi there, I was looking into monitoring the connection pools for my akka-http application, because in the past we've had instances where we hit our akka.http.host-connection-pool.max-connections limit. While browsing around the source code a bit, I came across this comment:

Kamon/instrumentation/kamon-akka-http/src/main/scala/kamon/instrumentation/akka/http/AkkaHttpClientInstrumentation.scala

Lines 32 to 35 in acc3c12

	/**
	* Simply modifies the requests as they are submitted. This does not cover connection pooling, just requests sent
	* via the Http.singleRequest mechanism.
	*/

I was curious, why does it not cover connection pooling? What would it take to enhance the capabilities such that we could monitor these type of connections? I realize it is probably challenging, so I'm wondering if it's something that has been considered in the past.

Thanks!