Just to confirm, are you testing a l4xnat farm or an HTTP farm? I would recommend you test some load balancer service that keeps a TCP connection opened like SSH, if you test HTTP then you should use some stress tool like wrk or ab, HTTP requests are super fast and it is quite difficult to capture some metrics if there isn't dedicated traffic. 

Please can you give more information about your test and try to run the tests as proposed?

Thanks!

Hi @rgonzaleza, did you check my previous comment, just to understand better the issue you share here, we need to understand if the TCP connections are always established (i.e ssh) or are established and closed in each simple request, as HTTP(S) works. 

Hi @emiliocm, thanks for your replies, we are testing a http farm, it is working seamlessly, and suddenly graphs are working but not in the right way, for example, right now we have 130 established connections but in the graph just show us 4 connections, I'm attaching some evidence hoping could help you understand the problem

Hi @rgonzaleza, I understand now what you are trying to share here. 

The session table (130) is not the same as the connection table (4) 

The session table shows the information saved in memory related to the session identifier, this identifier is used to connect the same client against the same backend during a period. It is information in layer 7 - Application layer. 

The connection table shows the TCP established connections, information in layer 4, transport layer. 

Weirdly, your farm is always in 4 TCP connections, but it can be normal in cases where the number of clients is always the same, for example, a group of API consumers. 

So I see a normal behaviour, if you want to know more about Established connections and sessions you can read our administration guide: 

https://www.skudonet.com/knowledge-base/enterprise-edition-v10-administration-guide/lslb-farms-update-http-profile-v10/#Persistence

Persistence: This setting controls how the HTTP service manages client sessions and which HTTP connections are used to maintain secure client sessions. When you select a persistence session type, you will be shown its Time To Live (TTL) in seconds.
No persistence: The farm service will not control client sessions. HTTP or HTTPS requests will be delivered to real servers in a round-robin fashion.

https://www.skudonet.com/knowledge-base/enterprise-edition-v10-administration-guide/monitoring-stats-farms-v10/

"Established Conns: The number of active connections to the farm. This does not necessarily mean one connection per connected client."