Created attachment 1685927 [details] ocp 4.4 Description of problem: From Prometheus, we can see haproxy exporter. haproxy_frontend_current_session or haproxy_server_current_session should show active sessions but it does not show like that. It seems that the number of sessions keeps increasing. From my test environment, there is no load that's why I can see session decresement after load testing. However, for customer production cluster, it goes to 15 million with ocp 3.11 and 8k with ocp 4.4 With 4.4, there is not much data because the customer just upgraded and ingress pod restarted and lost the data. However, when I see the graph, it seems to have the same issues with ocp 3.x Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Open Prometheus UI 2. query "haproxy_frontend_current_seesions" 3. The value should be under 20000 * ingress nodes Actual results: The value keeps increasing Expected results: The value should show only active sessions so the session counts would be around 15k per router. Additional info:
Created attachment 1685928 [details] ocp 3.11 (15 million)
The impact is that almost all router metrics are wrong after a sustained interval.
Created attachment 1685986 [details] Current sessions metric is now correct Uploaded an query from the PR that shows sessions being correct
The PR was merged and made available in "4.5.0-0.nightly-2020-05-11-084820". It is verified that in this version the Prometheus UI now shows the correct metric data for "haproxy_frontend_current_session".
Created attachment 1688909 [details] Promethrus UI data for patched v4.5 cluster
Created attachment 1688910 [details] Prometheus UI data for v4.4 cluster
Created attachment 1688912 [details] Promethrus UI data for unpatched v4.5 cluster
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409