You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are logging the connectionpool_inPool metric every minute to track open connections. Unfortunately, this metric appears to increase with each new connection created and does not decrease when the connection is closed as the metric only increases over time. We can use netstat to see that there are nowhere near as many open connections as reported by connectionpool_inPool.
The connectionpool_inUse metric seems to be accurate.
Here is the code we use to register the metric colleciton in our Bootstrap.java:
We are using Zuul 2.4.0. We saw the same behavior in 2.3.0. I attempted to look at the code that tracks these metrics but the increment/decrement logic for the connection tracking was hard for me to follow as it appeared to be sprinkled across many methods.
The text was updated successfully, but these errors were encountered:
I'm still interested in whether anyone has ideas about how to fix the connectionpool_inPool metrics. We are starting to implement connection limits and having better insight into connection use is important in being able to tweak and monitor connection behavior.
I don't see the same issue in our internal inUse metrics. The counter should be decremented by DefaultClientChannelManager.release() which will be called when a pooled connection is no longer in use
Sorry, @jguerra. I had a typo in my coment yesterday. It should have said inPool and not inUse. I edited the comment to fix that. The inUse metrics are working well. It is the inPool ones (as mentioned in the issue title) that are not reporting properly.
We are logging the connectionpool_inPool metric every minute to track open connections. Unfortunately, this metric appears to increase with each new connection created and does not decrease when the connection is closed as the metric only increases over time. We can use netstat to see that there are nowhere near as many open connections as reported by connectionpool_inPool.
The connectionpool_inUse metric seems to be accurate.
Here is the code we use to register the metric colleciton in our Bootstrap.java:
We are using Zuul 2.4.0. We saw the same behavior in 2.3.0. I attempted to look at the code that tracks these metrics but the increment/decrement logic for the connection tracking was hard for me to follow as it appeared to be sprinkled across many methods.
The text was updated successfully, but these errors were encountered: