On Sun, Nov 13, 2016 at 05:43:27PM +0530, Raghu Udiyar wrote: > > I'm having a few questions : did you miss anything from haproxy when > > doing this ? For example, did you have to workaround the impossibility > > to do something via the agent just because of the agent protocol or > > because of some validity checks performed by haproxy ? I'm asking > > because if we have to perform very minor tweaks, better do them before > > the release. Do you think you could benefit from "agent-send" so that > > the same agent is used for multiple servers, when haproxy would then > > indicate with the connection for what server it is connecting ? If so, > > would an automatic string such as "agent-send-name" sending the backend > > and the server name be an useful improvement for this ? > > > > Yes actually. When we started, herald was multi service, which is when we > realised its not possible to distinguish which backend agent request was > for. An "agent-send" feature that sends something like > "<backend_name>/<server_name>\n" would be useful. Herald would require > minor modifications to support this.
Right now haproxy already supports "agent-send" but you have to pass the string yourself in the configuration. So you can already update Herald to make use of this when configs support it. And later we may add a new directive so that users don't even have to configure the string anymore. > > Do you want me to add a link to the main haproxy page, and if so to > > what location ? > > > > Yes, I think the external link sections here is appropriate : > http://www.haproxy.org/#link Sure, that's what I intented, but I meant what should be the target of the link ? The github page, your article, anything else ? Willy
