npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

s3-log-fetcher

v1.0.0

Published

Fetch logs from S3

Downloads

1

Readme

s3-log-fetcher stability

npm version build status test coverage downloads js-standard-style

Fetch logs from S3.

Features:

  • incredibly fast
  • log lines are pumped out as they come in
  • incredibly fast
  • uses {node,unix} streams
  • incredibly fast

Installation

$ npm install s3-log-fetcher

Usage

const logFetcher = require('s3-log-fetcher')

const rs = logFetcher({
  from: '2015-10-03',
  until: '2015-11-04',
  bucket: 'sydney-my-app-test',
  key: '<S3 key>',
  secret: '<S3 secret>'
})

rs.pipe(stdout)

cli:

Usage: s3-log-fetcher [options]

Options:
  -h, --help      Output usage information
  -v, --version   Output version number
  -f, --from      Start date (required)
  -u, --until     End date (required)
  -k, --key       S3 access key, defaults to env.S3_ACCESS_KEY (required)
  -s, --secret    S3 secret key, defaults to env.S3_SECRET_KEY (required)
  -b, --bucket    S3 bucket name (required)

Examples:
  $ s3-log-fetcher -f 2015-10-03 -u 2015-10-03 \
    -b testbucket  # Fetch logs from S3 for 2015-10-03
  $ s3-log-fetcher -f 2015-10-03 -u 2015-10-13 \
    -b testbucket  # Fetch logs from S3 for 2015-10-03 until 2015-10-13

Docs: https://github.com/TabDigital/node-s3-log-fetcher
Bugs: https://github.com/TabDigital/node-s3-log-fetcher/issues

S3 directory structure

S3-log-fetcher expects the S3 bucket to follow a format. All files should either be prefixed by a date, or live in a directory that is prefixed with the date, this package don't care. For example:

. [ bucket: sydney-my-app-test ]
  - 2015-10-11-sydney-ec2-01.log
  - 2015-10-11-sydney-ec2-04.log
  - 2015-10-11
    - sydney-ec2-02.log
    - sydney-ec2-03.log
  - 2015-10-12
    - sydney-ec2-01.log
    - sydney-ec2-02.log
  - 2015-10-12-sydney-ec2-03.log
  - 2015-10-12-sydney-ec2-04.log

API

readStream = logFetcher.createReadStream(opts)

Create a readable stream for a start and end date. Takes the following opts:

  • from (required): Start date.
  • until (required): End date.
  • key (required): S3 access key. Defaults to process.env.S3_ACCESS_KEY.
  • secret (required): S3 secret key. Defaults to process.env.S3_SECRET_KEY.
  • bucket (required): S3 bucket name.

License

MIT