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

@dtails/logger-backend

v1.3.0

Published

A logging library for Node.js, with optional support for storing logs in DB and S3

Downloads

255

Readme

Log Server

Logging solution for node.js

Features

  • During local development the logs written to the console
  • Auto written to Amazon S3 by day
  • Life time config for Amazon S3
  • Able to config to turn on/off by log level
  • Sentry included

Installation

  npm install @dtails/logger-backend

Create table logs in the database

  knex.schema.createTable('logs', table => {
    table.increments('id')
    table.dateTime('created_at').defaultTo(knex.fn.now())
    table.string('log_level')
    table.text('data')
    table.primary(['id']);
  })

Create Logs model with objection js https://vincit.github.io/objection.js/

import { Model } from 'objection';
import Knex from 'knex';

const knex = Knex({
  client: 'pg',
  connection: process.env.DATABASE_URL
});

Model.knex(knex);

export default class Logs extends Model {
  static get tableName() {
    return 'logs';
  }
}

ENV configuration

LOG_LEVEL=DEBUG,ERROR,WARN,INFO

LOG_S3_LIFECYCLE=10

LOG_FILE_NAME=logs-backend

AWS_ACCESS_KEY_ID=[AWS_ACCESS_KEY_ID]

AWS_SECRET_ACCESS_KEY=[AWS_SECRET_ACCESS_KEY]

AWS_REGION=[AWS_REGION]

AWS_BUCKET_NAME=[AWS_BUCKET_NAME]

SENTRY_DSN=[SENTRY_DSN]

Schedule for S3 Upload / Delete

Create a scheduled jobs and config it in the Heroku (1 time per day, Any time)

import Logger from '@dtails/logger-backend';
import Logs from './models/logs.js';

const logger = new Logger(Logs);
logger.syncLogToS3();

// Remove that if you don't want remove logs in the s3
logger.deleteOldLogs();

Usage/Examples

import Logger from '@dtails/logger-backend';
import Logs from './models/logs.js';

function TestLogger() {  
  const logger = new Logger(Logs);
  
  // Debug log
  logger.log('Test Debug');

  // Error log
  logger.error('Test Error');

  // Warning log
  logger.warn('Test Warning');

  // Info log
  logger.info('Test Info');

  // Log with variables
  const data = 'Test Data';
  logger.log(`A message with data: ${data}`)

  // Log with object
  const sampleObject1 = {
    name: 'John',
    age: 30,
    cars: {
      car1: 'Ford',
      car2: 'BMW',
      car3: 'Fiat'
    }
  };

  const someObject2 = {a: true};
  logger.log('Please also log as console.log does in relation to objects', sampleObject1, someObject2);

  // Log error
  try {
    errorTest = new Error('Test Error');
  } catch (error) {
    logger.error(error);
  }
}