Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upSupport haproxy logs without captured headers #9463
Comments
This comment has been minimized.
This comment has been minimized.
Pinging @elastic/infrastructure |
This comment has been minimized.
This comment has been minimized.
Would it not just be simpler to document in the haproxy module the log-format you are expecting |
This comment has been minimized.
This comment has been minimized.
@sentient actually it is also in our plans to document supported formats (see #8311) The idea is to support the default haproxy formats (no log options, The issue addressed here is that the log format used by If you are having this issue, an option to workaround it is to add captured headers, even if they don't exist, something like:
|
haproxy logs don't contain captured headers by default, but current grok patterns expect them, make them optional and add test cases for them.
Some examples:
Without captured headers:
With request captured headers:
With request and response captured headers:
Headers capture is configured in haproxy config with options like:
Notice that when only one type of headers is being captured it is not possible to know on default log formats if they are request or response headers. Maybe we should ignore them by default.