Enable set syslog host for Filebeat HAProxy module #9366
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The syslog input for the Filebeat HAProxy module binds by default to localhost:9001. It is possible to configure the port through the variable var.syslog_port, but it is not possible for the syslog_host. This can be useful when running Filebeat inside a Docker container. Since it is not easy to forward a port from the host to localhost inside the Docker container, it restricts the ability to use Filebeat in a Docker container to log HAProxy running on a remote instance. With this commit, we make it possible to configure the host that the syslog input for the HAProxy binds to through a variable var.syslog_host. This makes it possible to have HAProxy running on a remote instance (e.g., a FreeBSD 11.2 host), and configure that instance to remote log to a Filebeat instance running inside a Docker container.
ruflin
added
module
review
Filebeat
|
Pinging @elastic/infrastructure |
|
jenkins, test this |
jsoriano
reviewed
Dec 4, 2018
…yslog_host * elastic/master: Metricbeat can call Jolokia with GET requests. (elastic#8566) (elastic#9226) Add some missing references to PRs in changelog (elastic#9358)
jsoriano
approved these changes
Dec 4, 2018
jsoriano
approved these changes
Dec 4, 2018
|
@jsoriano I don't think the build failure had anything to do with my change. How do I trigger a new build? |
|
jenkins, retest this please |
jsoriano
added
the
needs_backport
jsoriano
pushed a commit
to jsoriano/beats
that referenced
this pull request
Dec 5, 2018
The syslog input for the Filebeat HAProxy module binds by default to localhost:9001. It is possible to configure the port through the variable var.syslog_port, but it is not possible for the syslog_host. This can be useful when running Filebeat inside a Docker container. Since it is not easy to forward a port from the host to localhost inside the Docker container, it restricts the ability to use Filebeat in a Docker container to log HAProxy running on a remote instance. With this commit, we make it possible to configure the host that the syslog input for the HAProxy binds to through a variable var.syslog_host. This makes it possible to have HAProxy running on a remote instance (e.g., a FreeBSD 11.2 host), and configure that instance to remote log to a Filebeat instance running inside a Docker container. (cherry picked from commit bc7640f)
jsoriano
added
v6.6.0
and removed
needs_backport
jsoriano
added a commit
that referenced
this pull request
Dec 6, 2018
The syslog input for the Filebeat HAProxy module binds by default to localhost:9001. It is possible to configure the port through the variable var.syslog_port, but it is not possible for the syslog_host. This can be useful when running Filebeat inside a Docker container. Since it is not easy to forward a port from the host to localhost inside the Docker container, it restricts the ability to use Filebeat in a Docker container to log HAProxy running on a remote instance. With this commit, we make it possible to configure the host that the syslog input for the HAProxy binds to through a variable var.syslog_host. This makes it possible to have HAProxy running on a remote instance (e.g., a FreeBSD 11.2 host), and configure that instance to remote log to a Filebeat instance running inside a Docker container. (cherry picked from commit bc7640f) Co-authored-by: Jason Tedor <jason@tedor.me>
|
Thanks @jasontedor! this will be available on 6.6.0. |
|
Thanks @jsoriano! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The syslog input for the Filebeat HAProxy module binds by default to localhost:9001. It is possible to configure the port through the variable var.syslog_port, but it is not possible for the syslog_host. This can be useful when running Filebeat inside a Docker container. Since it is not easy to forward a port from the host to localhost inside the Docker container, it restricts the ability to use Filebeat in a Docker container to log HAProxy running on a remote instance. With this commit, we make it possible to configure the host that the syslog input for the HAProxy binds to through a variable var.syslog_host. This makes it possible to have HAProxy running on a remote instance (e.g., a FreeBSD 11.2 host), and configure that instance to remote log to a Filebeat instance running inside a Docker container.