Logs not being forwarded to logstash after re-connect

[sheshum]

Prerequisites

• [ X] Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3AOutOfSyncStudios
  • Reproduced the behavior multiple times

Description

If connection to logstash service is lost and re-established, logs are not being
forwarded to logstash service anymore.

Also, "retries" property is not incremented while re-connecting so max connection retries is
never reached.

my logstash transport configuration:
{
mode: 'tcp',
host: 'myhostIP',
port: 5044,
maxConnectRetries: 500,
timeoutConnectRetries: 60000
}

Steps to Reproduce

1. Set Logstash transport to connect to you logstash service
2. Make sure that your app logs are being forwarded to logstash and are visible in kibana
3. Stop logstash service and start it again or reboot VM that is hosting the service.
4. Check if messages arrive to logstash/elasticsearch after restart of logstash service.

Expected behavior:
Logs should be forwarded to logstash after connection is broken and re-established.

Actual behavior:
Logs are not visible in kibana and after debugin the lib it seems that transport is not used by winston logger anymore.
Even though the logstash transport is connected to logstash service.

Reproduces how often:
Reproduces every time, 10/10.

Versions

npm: 6.13.4
nodejs: v12.14.1
"winston": "3.3.3",
"winston-daily-rotate-file": "4.5.0",
"winston3-logstash-transport": "1.0.1-c",

Additional Information

my logstash transport configuration:
{
mode: "tcp",
host: 'myhostIP',
port: 5044,
maxConnectRetries: 500,
timeoutConnectRetries: 60000,
}

[dhemiwc]

same issue here