"Starting tcp input listener" is no longer logged as of Logstash 5.6.x

[PhaedrusTheGreek]

Prior to Logstash 5.6.x, we could see TCP listener start in the Log:

├ $ ~jay/workspace/logstash-5.5.2/bin/logstash -f test.conf
ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console.
Sending Logstash's logs to /Users/jay/workspace/logstash-5.5.2/logs which is now configured via log4j2.properties
[2017-11-03T10:12:33,741][INFO ][logstash.pipeline        ] Starting pipeline {"id"=>"main", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>500}
[2017-11-03T10:12:33,756][INFO ][logstash.inputs.tcp      ] Starting tcp input listener {:address=>"192.168.0.17:5052"}
[2017-11-03T10:12:33,771][INFO ][logstash.pipeline        ] Pipeline main started
[2017-11-03T10:12:33,806][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600}

Now it seems we have no such luxury:

Sending Logstash's logs to /Users/jay/workspace/logstash-5.6.1/logs which is now configured via log4j2.properties
[2017-11-03T10:10:57,299][INFO ][logstash.modules.scaffold] Initializing module {:module_name=>"fb_apache", :directory=>"/Users/jay/workspace/logstash-5.6.1/modules/fb_apache/configuration"}
[2017-11-03T10:10:57,323][INFO ][logstash.modules.scaffold] Initializing module {:module_name=>"netflow", :directory=>"/Users/jay/workspace/logstash-5.6.1/modules/netflow/configuration"}
[2017-11-03T10:10:57,627][INFO ][logstash.pipeline        ] Starting pipeline {"id"=>"main", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>500}
[2017-11-03T10:10:57,865][INFO ][logstash.pipeline        ] Pipeline main started
[2017-11-03T10:10:57,903][INFO ][logstash.agent           ] Successfully started Logstash API endpoint {:port=>9600}

tcp4       0      0  192.168.0.17.5052      *.*                    LISTEN

[jordansissel]

I don’t think we consider the logs emitted by programs to be part of any compatibility contract. I would prefer in this case to avoid burdening a human with having to stare at the logstash logs waiting to read “starting tcp input” — So. What is the problem created by this log message being missing? What does it inform that is not already informed by some other signal such as “pipeline started”?

…

On Fri, Nov 3, 2017 at 7:15 AM Jay Greenberg ***@***.***> wrote: Prior to Logstash 5.6.x, we could see TCP listener start in the Log: ├ $ ~jay/workspace/logstash-5.5.2/bin/logstash -f test.conf ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Sending Logstash's logs to /Users/jay/workspace/logstash-5.5.2/logs which is now configured via log4j2.properties [2017-11-03T10:12:33,741][INFO ][logstash.pipeline ] Starting pipeline {"id"=>"main", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>500} [2017-11-03T10:12:33,756][INFO ][logstash.inputs.tcp ] Starting tcp input listener {:address=>"192.168.0.17:5052"} [2017-11-03T10:12:33,771][INFO ][logstash.pipeline ] Pipeline main started [2017-11-03T10:12:33,806][INFO ][logstash.agent ] Successfully started Logstash API endpoint {:port=>9600} Now it seems we have no such luxury: Sending Logstash's logs to /Users/jay/workspace/logstash-5.6.1/logs which is now configured via log4j2.properties [2017-11-03T10:10:57,299][INFO ][logstash.modules.scaffold] Initializing module {:module_name=>"fb_apache", :directory=>"/Users/jay/workspace/logstash-5.6.1/modules/fb_apache/configuration"} [2017-11-03T10:10:57,323][INFO ][logstash.modules.scaffold] Initializing module {:module_name=>"netflow", :directory=>"/Users/jay/workspace/logstash-5.6.1/modules/netflow/configuration"} [2017-11-03T10:10:57,627][INFO ][logstash.pipeline ] Starting pipeline {"id"=>"main", "pipeline.workers"=>4, "pipeline.batch.size"=>125, "pipeline.batch.delay"=>5, "pipeline.max_inflight"=>500} [2017-11-03T10:10:57,865][INFO ][logstash.pipeline ] Pipeline main started [2017-11-03T10:10:57,903][INFO ][logstash.agent ] Successfully started Logstash API endpoint {:port=>9600} tcp4 0 0 192.168.0.17.5052 *.* LISTEN — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#92>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAIC6iCe7h6OkDrzvUEojVcOCsD1pcL7ks5syx_rgaJpZM4QRJjN> .

[PhaedrusTheGreek]

I don't suppose there's any reason to keep the log message, just documenting the unexpected change in behaviour, as it's been raised to me more than once.

[jsvd]

It does seem like a useful log message, we tend to log such information about opening files, sockets, etc. I'm tagging this as adoptme, as it should be a super low hanging fruit.