New configuration option to make adding host and port fields optional

[GrahamHannington]

Currently, the Logstash TCP input plugin adds host and port fields. I'd like a new configuration option to make that behavior optional.

I'm using Logstash to input JSON Lines over TCP, and then output to Elasticsearch.

The resulting indexed documents in Elasticsearch contain host and port fields that are not in the original JSON Lines forwarded to Logstash. These fields are added by the Logstash TCP input plugin.

For my use case, these added fields are undesirable.

Some of the original incoming JSON Lines might contain host and port fields. So, in the Logstash configuration, I can't simply insert unconditional mutate remove_field settings for host and port, because that would risk removing those original fields.

Related reference

• Elastic discussion forum topics:
  • TCP input plugin generate additional port field
  • Safely remove tcp input plugin’s “host” and “port” fields

[GrahamHannington]

the Logstash TCP input plugin adds host and port fields

The current docs don't mention this behavior. This feature request involves updating the docs to mention this behavior.

I hope this feature request is accepted; however, if it's rejected, then it would be nice to have the docs updated so users aren't surprised by the presence of the added fields.