On Sat, Jan 07, 2023 at 09:41:01AM -0700, Shawn Heisey wrote: > On 1/7/23 07:46, Willy Tarreau wrote: > > Indeed, you need "option socket-stats" in the frontend that has such > > listeners, so that the stats are collected per-listening socket (this > > is not the case by default). > > That's really cool. But I have an oddity I'd like to share and see if it > needs some work. > > https://www.dropbox.com/s/m54wp15wkmkrzcp/haproxy_option_socket-stats.png?dl=0 > > The bind config line I have for quic lists three host:port combos (the two > real server IPs and the VIP), which is why it's there three times. I know > you probably don't want to put info like the host:port on the stats page. > Because all three host:port combos are part of the same bind line, I think > it probably should have only listed the name once. Thoughts?
No, you just have one entry per "bind" line. If it's only a matter of listening on multiple host:port and you want them merged, you could probably put all the addresses on the same line separated by commas and see if it's better: bind quic4@1.1.1.1:443,quic4@2.2.2.2:443,quic4@3.3.3.3:443 ssl crt ... Also if you want you can show the IP:ports by adding "stats show-legends" in your stats section. However, be aware that it will also show server IP addresses, configured stickiness cookies etc. Thus only do this if access to your stats page is restricted to authorized users only. > I will be adjusting that to three bind lines with separate names and the > same options, because I do like the idea of having them separate ... but I > think by default it probably should have only showed one line, not three > with the same name, because it's currently one config line. No they are precisely 3 config lines, which is why you have 3 stats. Internally one such line creates what we call a "bind_conf" which groups a number of settings, and the name is given to this line. Regards, Willy
