Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cherry-pick #9958 to 6.6: Support haproxy log lines without captured headers #9969

Merged
merged 1 commit into from
Jan 10, 2019

Conversation

jsoriano
Copy link
Member

@jsoriano jsoriano commented Jan 9, 2019

Cherry-pick of PR #9958 to 6.6 branch. Original message:

Haproxy can capture headers from http requests and responses and log
them. This is not done by default but current filebeat module expects
it.

Make captured headers optional, and collect them only if both request
and response headers are configured. If only one is configured, the log
is parsed but headers not collected as we cannot know if they are
request or response headers.

Fix #9463

Haproxy can capture headers from http requests and responses and log
them. This is not done by default but current filebeat module expects
it.

Make captured headers optional, and collect them only if both request
and response headers are configured. If only one is configured, the log
is parsed but headers not collected as we cannot know if they are
request or response headers.

(cherry picked from commit b39d780)
@jsoriano jsoriano merged commit 00a905c into elastic:6.6 Jan 10, 2019
@jsoriano jsoriano deleted the backport_9958_6.6 branch January 10, 2019 20:51
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
…astic#9969)

Haproxy can capture headers from http requests and responses and log
them. This is not done by default but current filebeat module expects
it.

Make captured headers optional, and collect them only if both request
and response headers are configured. If only one is configured, the log
is parsed but headers not collected as we cannot know if they are
request or response headers.

(cherry picked from commit 8e21bd2)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants