Does not send successfully unless I wait 30 seconds about winston-logsene HOT 5 CLOSED

Did you set options.flushOnExit=true in the winston constructor?

from winston-logsene.

I tried setting flushOnExit: true in the add call and have now tried it on the Winston constructor as well. No change. It defaults to true, and in fact I don't think it can be set to false:

if (!options.flushOnExit) {
    options.flushOnExit = true
}

from winston-logsene.

Please let me know, how to reproduce it. How is your program terminated? Calling process.exit (which means no async code can be executed)?

Could you please post the output of npm ls - so we can check dependencies?

Here is what I did:

1. Run the example https://github.com/sematext/winston-logsene/blob/master/example/index.js
   `node exaple/index.js``
   Output:

node example/index.js 
2016-09-25T17:58:36.327Z winston-logsene: start flushing 1 logs before exit ...
2016-09-25T17:58:36.788Z winston-logssene: flush before exit: 1 logs send.
2016-09-25T17:58:36.989Z winston-logsene: flush: no logs in buffer

Check logs in Logsene:

and Kibana

from winston-logsene.

Should be fixed, something changed in logsene-js log counts, and winston-logsene should watch own logCounts. 3a967ab

Even with latest logsene-js, it works again:

node example/index.js 
2016-09-25T19:04:08.075Z winston-logsene: start flushing 1 logs before exit ...
2016-09-25T19:04:08.568Z winston-logssene: flush before exit: 1 logs send.
2016-09-25T19:04:08.771Z winston-logsene: flush: no logs in buffer

from winston-logsene.

I tried with 1.2.1 and it works for me now. Thanks.

from winston-logsene.