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

Filebeat HAproxy Default log format added #8428

Conversation

sayden
Copy link
Contributor

@sayden sayden commented Sep 25, 2018

Refer to this Issue for more details elastic/integrations#3250

Integration tests are passing and I'm uploading after a make update and a make filebeat.test but removing whatever is written in the HAProxy http expected json that makes the tests fail

@sayden sayden added the Filebeat Filebeat label Sep 25, 2018
@sayden sayden requested a review from jsoriano September 25, 2018 09:27
@@ -40,5 +40,23 @@
description: raw_request_line is the complete HTTP request line, including the method, request and HTTP version string.
type: text


- name: default
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't namespace fields depending on the matching pattern, some fields can be common between them, like probably frontend_name.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TCP format PR is also open and waiting and I think I did a better naming there. Let's move on to finish and close this two and then I'll quickly open a new one to write proper naming?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After opening a new PR with both PRs, what prevents us on using a proper naming? I'd do it before merging.

"@timestamp": "2018-09-20T15:42:59.000Z",
"fileset.module": "haproxy",
"fileset.name": "log",
"haproxy.client_ip": "127.0.0.1",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Using local IPs can be a good trick to mitigate #8400 🙂 but also will avoid the presence of geoip fields, and I think that we want at least to test that they are present 🤔

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To clarify this point, we may want to use a public IP here, what would be more similar to a real event. Using a public IP will fill the geoip data (using a local IP won't, and this is why I said that it wouldn't be then affected by #8400).

@sayden sayden force-pushed the feature/haproxy-filebeat-default-log-format branch from e50caaf to b02c8ca Compare October 1, 2018 19:41
@sayden sayden added enhancement needs_backport PR is waiting to be backported to other branches. labels Oct 1, 2018
@sayden sayden added in progress Pull request is currently in progress. v6.5.0 module labels Oct 1, 2018
@jsoriano
Copy link
Member

This branch will need an update.

@sayden sayden force-pushed the feature/haproxy-filebeat-default-log-format branch from b02c8ca to fd9e9d2 Compare October 17, 2018 17:59
@sayden
Copy link
Contributor Author

sayden commented Oct 17, 2018

Continues here #8637

@sayden sayden closed this Oct 17, 2018
@sayden sayden deleted the feature/haproxy-filebeat-default-log-format branch October 18, 2018 11:28
@urso urso removed the needs_backport PR is waiting to be backported to other branches. label Oct 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Filebeat Filebeat in progress Pull request is currently in progress. module v6.5.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants