[
https://issues.apache.org/jira/browse/FLUME-3133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686447#comment-16686447
]
ASF subversion and git services commented on FLUME-3133:
--------------------------------------------------------
Commit 671fc3f1b6d6b2239b171f582b189d0fbadedb6f in flume's branch
refs/heads/trunk from [~turcsanyip]
[ https://git-wip-us.apache.org/repos/asf?p=flume.git;h=671fc3f ]
FLUME-3133 Add client IP / hostname headers to Syslog sources.
In the newer version of the Syslog message format (RFC-5424) the hostname
is not a mandatory header anymore so the Syslog client might not send it.
On the Flume side it would be a useful information that could be used
in interceptors or for event routing.
To keep this information, two new properties have been added to the Syslog
sources: clientIPHeader and clientHostnameHeader.
Flume users can define custom event header names through these parameters
for storing the IP address / hostname of the Syslog client in the Flume
event as headers.
The IP address / hostname are retrieved from the underlying network sockets,
not from the Syslog message.
This change is based on the patch submitted by Jinjiang Ling which has been
rebased onto the current trunk and the review comments have been implemented.
This closes #234
Reviewers: Ferenc Szabo, Endre Major
(Peter Turcsanyi via Ferenc Szabo)
> Add a ipHeader config in Syslog Sources
> ---------------------------------------
>
> Key: FLUME-3133
> URL: https://issues.apache.org/jira/browse/FLUME-3133
> Project: Flume
> Issue Type: Bug
> Components: Sinks+Sources
> Affects Versions: 1.7.0
> Reporter: Jinjiang Ling
> Assignee: Peter Turcsanyi
> Priority: Major
> Fix For: 1.9.0
>
> Attachments: FLUME-3133.patch
>
>
> When I use the syslog source to collect log from other hosts, my config like
> this
> {quote}
> ...
> a1.sources.r1.host = 0.0.0.0
> a1.sources.r1.ports = 5140
> ...
> {quote}
> I'm using the "host" header to tell where the event come from.
> However, when the syslog format is changed, the "host" header will miss.
> In this sence, I couldn't tell where the event come from.
> So I add a new config "ipHeader", it's similar to "portHeader" in Multiport
> Syslog TCP Source.
> It can be used like this
> {quote}
> ...
> a1.sources.r1.host = 0.0.0.0
> a1.sources.r1.ports = 5140
> a1.sources.r1.ipHeader = test_ip_header
> ...
> {quote}
> Then I can get a header named "test_ip_header" in the event, the value is the
> ip of host which send this event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
