Goal: Support the ability to modify the default syslog maximum message size of HAProxy.

Problem: The default setting of HAProxy's syslog maximum message size is 1024 bytes, but some customers define a custom syslog message format that captures many additional attributes of the traffic for the purposes of auditing, retrospection, analysis, etc resulting in messages larger than 1024 bytes. The large messages are truncated to 1024 bytes (because of the current fixed value) and there is important information loss.

Dependencies (internal and external):

Prioritized epics + deliverables (in scope / not in scope):

Not in scope:

• Performance tuning or analysis as a result of using larger message sizes.

Estimate (XS, S, M, L, XL, XXL):

Previous Work:

Open questions:

Acceptance criteria:

Epic Done Checklist:

• CI - CI Job & Automated tests: <link to CI Job & automated tests>
• Release Enablement: <link to Feature Enablement Presentation> 
• DEV - Upstream code and tests merged: <link to meaningful PR orf GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>
• Notes for Done Checklist: 
  • Adding links to the above checklist with multiple teams contributing; select a meaningful reference for this Epic.
  • Checklist added to each Epic in the description, to be filled out as phases are completed - tracking progress towards “Done” for the Epic.