Hi all, we did some thinking about how to improve haproxy and which features we’d like to see in next versions.
We came up with the following list and would like to discuss if they can be done/should be done or not. - One global statssocket which can be switched through to see stats of every bind process. And also an overall overview summed up from all backends and frontends. - One global control socket to control every backend server and set them inactive or active on the fly. - In general better nbproc > 1 support - Include possibility in configfile to maintain one configfile for each backend / frontend pair - CPU pinning in haproxy without manually using taskset/cpuset - sflow output - latency metrics at stats interface (frontend and backend, avg, 95%, 90%, max, min) - accesslist for statssocket or ldap authentication for stats socket Are there any others things which would be cool? I hope we can have a nice discussion about a “fancy” feature set which could be provided by lovely haproxy. Best regards, Annika --- Systemadministration Travian Games GmbH Wilhelm-Wagenfeld-Str. 22 80807 München Germany a.wick...@traviangames.com<mailto:a.wick...@traviangames.com> www.traviangames.de<http://www.traviangames.de/> Sitz der Gesellschaft München AG München HRB: 173511 Geschäftsführer: Siegfried Müller USt-IdNr.: DE246258085 Diese Email einschließlich ihrer Anlagen ist vertraulich und nur für den Adressaten bestimmt. Wenn Sie nicht der vorgesehene Empfänger sind, bitten wir Sie, diese Email mit Anlagen unverzüglich und vollständig zu löschen und uns umgehend zu benachrichtigen. This email and its attachments are strictly confidential and are intended solely for the attention of the person to whom it is addressed. If you are not the intended recipient of this email, please delete it including its attachments immediately and inform us accordingly.
