Buffering the logs being send to fluentd when fluentd is not available

Hey,
We are using your library to send logs from our lambda functions to fluentd via Bunyan Logger.

```
// Instance style fluent-logger creation
const sender = require('fluent-logger').createFluentSender('tag-prefix', {
enableReconnect: false,
host: 'localhost',
port: 24224,
reconnectInterval: 3000,
requireAckResponse: true,
timeout: 3.0
});

// Listener for detecting error events
sender.on('error', (error) => {
console.log('Error found on stream here. ' + error);
// Printing the logs on stdout using the buffer.
});

// bunyan logger instance for sending logs to fluentd.
logger = bunyan.createLogger({
name: 'FluentdLogger',
streams: [{ stream: sender.toStream('fluentd') }]
});

logger.info('this log record is sent to fluent daemon');

```
1. Using the above mentioned approach, the logs are successfully being sent to fluentd from lambda.
2. However, in the case fluentd is _not available_ (not listening at the specified host and port) , then the expected behavior is to send these logs to the **stdout** for displaying.

For point number 2, is there a way to buffer the logs being sent to fluentd and then sending them to stdout instead (inside the error listener)?

It would be great if anyone could advise me on it.

Beginnen Sie mit createFluentSender, seinen Optionen enableReconnect und timeout sowie den Einstiegspunkten des error-Ereignisses des Senders und toStream('fluentd'). Klären Sie das beabsichtigte Buffering- und Fallback-Verhalten für nicht verfügbares Fluentd und bestimmen Sie anschließend den erforderlichen Umfang, damit Logs stdout erreichen, ohne Datensätze zu verlieren.

Vom Indexierungsmodell aus dem Issue-Text verfasst.