It would be... more convenient for my use case to be able to encode the string in the config (we may have several backends for a different service to correspond to phased deployment rollouts, and I'd prefer to encode the logic for mapping backend name to service name in my existing haproxy config templating script rather than adding it to the agent script). If you think it's significantly better, I could make it a static string, though, and bite the bullet for complexity in the agent.
We could also do something where we defined it per-backend (like the way `option httpchk` works now; I could easily change this to a backend parameter set with `option agent-send` or whatever). On Thu, Oct 22, 2015 at 12:51 PM, Willy Tarreau <[email protected]> wrote: > On Thu, Oct 22, 2015 at 11:37:47AM +0200, Baptiste wrote: > > This is interesting. > > Yep, that's in line with the HTTP option to send some server info > with HTTP checks (name, weight and I don't remember what). > > > That said, I'm suggesting an improvement: use the log format varialble. > > No, please no! > > Log-format only works with a session. Here checks don't have any session > and are completely out of band. Most tags and fetches will either not work > or simply crash the system. Not to mention the added complexity in the > config parser to deal with these cases. > > In order to simplify the config, I'd suggest just to always send the > exact same string (eg: "backend=XXX; server=YYY\n") which is easy to > expand with new tags in the future if needed (such as the LB node for > example). > > Regards, > Willy > > -- James Brown Engineer
