Skip to content

Node.js stream for logging to s3 with rotated object names. Usable as a wiston-file stream.

License

Notifications You must be signed in to change notification settings

yumenohosi/s3-streamlogger

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

30 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

s3-streamlogger

NPM version

A Writable Stream object that uploads to s3 objects, periodically rotating to a new object name.

See also tails3 for a script to tail the log files produced by s3-streamlogger.

Installation

npm install --save s3-streamlogger

Basic Usage

var S3StreamLogger = require('s3-streamlogger').S3StreamLogger;

var s3stream = new S3StreamLogger({
               bucket: "mys3bucket",
        access_key_id: "...",
    secret_access_key: "..."
});

s3stream.write("hello S3");

Use with Winston: Log to S3

npm install --save winston
npm install --save s3-streamlogger
var winston        = require('winston');
var S3StreamLogger = require('s3-streamlogger').S3StreamLogger;

var s3_stream = new S3StreamLogger({
             bucket: "mys3bucket",
      access_key_id: "...",
  secret_access_key: "..."
});

var logger = new (winston.Logger)({
  transports: [
    new (winston.transports.File)({
      stream: s3_stream
    })
  ]
});

logger.info('Hello Winston!');

Add hostname information for tails3

tails3 expects messages to be logged as json (the default for the file transport), with hostname and (for critical errors), stack properties to each log object, in addition to the standard timestamp, level and message properties. You can provide these using the third "metadata" option to winston's log method:

logger.log(level, message, {hostname: ... , stack: ...});

Handling logging errors

When there is an error writing to s3, the stream emits an 'error' event with details. You should take care not to log these errors back to the same stream (as that is likely to cause infinite recursion). Instead log them to the console, to a file, or to SNS using winston-sns.

Options

bucket (required)

Name of the S3 bucket to upload data to. Must exist. Can also be provided as the environment variable BUCKET_NAME.

access_key_id (required)

AWS access key ID, must have putObject permission on the specified bucket. Can also be provided as the environment variable AWS_SECRET_ACCESS_KEY.

secret_access_key (required)

AWS secret key for the access_key_id specified. Can also be provided as the environment variable AWS_SECRET_KEY_ID.

name_format

Format of file names to create, accepts strftime specifiers. Defaults to "%Y-%m-%d-%H-%M-unknown-unknown.log". The Date() used to fill the format specifiers is created with the current UTC time, but still has the current timezone, so any specifiers that perform timezone conversion will return incorrect dates.

If you use a format of the form %Y-%m-%d-%H-%M-<stage>-<hostname>.log, then you can use tails3 to tail the log files being generated by S3StreamLogger.

rotate_every

Files will be rotated every rotate_every milliseconds. Defaults to 3600000 (60 minutes).

max_file_size

Files will be rotated when they reach max_file_size bytes. Defaults to 200 KB.

upload_every

Files will be uploaded every upload_every milliseconds. Defaults to 20 seconds.

buffer_size

Files will be uploaded if the un-uploaded data exceeds buffer_size bytes. Defaults to 10 KB.

server_side_encryption

The server side encryption AES256 algorithm used when storing objects in S3. Defaults to false.

License

ISC: equivalent to 2-clause BSD.

About

Node.js stream for logging to s3 with rotated object names. Usable as a wiston-file stream.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 100.0%