add_remote_addr to http input like fluentd has

[knogbe]

Is your feature request related to a problem? Please describe.

add_remote_addr in fluentd http input allow you to add the source host ip to the event been forwarded. Fluent-bit does not seem to have it unless it is hidden which is the reason why I am asking first.

Describe the solution you'd like

Solution will be to add this option which is looking in the request header and retrieving the remote address and inject it in the event as REMOTE_ADDR.

Describe alternatives you've considered

Will have to put a proxy in front of fluent-bit.
Additional context

The event that I am trying to aggregate does not have any datapoint to identify the source of the event.

[soc-team-members]

I would vote for this feature, too. There plenty are of inputs where remote_addr would add real valuable information to map a computername to an IP, like in_http, in_splunk, in_syslog, in_elasticsearch, in_tcp, in_upd and so on. Since some logs contain the IP, while other logs contain the computername, a remote_addr-feature would massively ease up correlations between those logs. In case of syslog for example, we are currently using syslog-ng in front of fluent-bit just to add this tiny piece of information. With a remote_addr-feature in fluent-bit, we could completely get rid of syslog-ng.