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

@bristlecone-labs/neo-logger-sdk

v2.0.1

Published

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.

Downloads

5

Readme

NeoLoggerSdk

This library was generated with Angular CLI version 7.2.0.

Summary

Programmers frequently use console.log to record errors or other informational messages in their Angular applications. Although this is fine while debugging your application, it’s not a best practice for production applications. As Angular is all about services, it’s a better idea to create a logging service that you can call from other services and components. In this logging service, you can still call console.log, but you can also modify the service later to record messages to store them in local storage or a database table via the Web API.

A Simple Logging Service

To get started, create a very simple logging service that only logs to the console. The point here is to replace all of your console.log statements in your Angular application with calls to a service.

A logger has different levels of logging:

'audit', 'error', 'warn', 'info', 'debug' Each of these log levels has its own method on the logging instance. You can set the maximum log level on a logger at runtime.

  1. info(logMessage: string, appName: string, userEmail: string, source?: string, stackTrace?: string)
  2. error(logMessage: string, appName: string, userEmail: string, source?: string, stackTrace?: string)
  3. warn(logMessage: string, appName: string, userEmail: string, source?: string, stackTrace?: string)
  4. debug(logMessage: string, appName: string, userEmail: string, source?: string, stackTrace?: string)
  5. audit(logMessage: string, appName: string, userEmail: string)
  6. fileLineage(logMessage: string, appName: string, userEmail: string, filePath: string)

source and stackTrace will be optional. Audit type logging will be user audit and file audit(fileLineage).

How to use neo-logger-sdk

npm i @bristlecone-labs/neo-logger-sdk

import NeoLoggerSdkService in particular component like below

Example

import { Component } from '@angular/core';
import { NeoLoggerSdkService } from '@bristlecone-labs/neo-logger-sdk';

@Component({
  selector: 'al-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.css']
})
export class AppComponent {
  title = 'al';
  constructor(private loggerService: NeoLoggerSdkService) {
    this.loggerService.audit('Login to App', 'NEO Data Platform', '[email protected]');
    this.loggerService.fileLineage('test.csv file is downloaded', 'NEO Data Platform', '[email protected]', 's3n://us-east-1-neo-dev-data-lake-raw/test.csv');
     this.loggerService.info('Getting Logs', 'NEO Data Platform', '[email protected]', 'app.component.ts');
  }
}

While ingesting any logs appName and userEmail is required. Application will push the logs through log ingestion api to Athena DB.

Code scaffolding

Run ng generate component component-name --project neo-logger-sdk to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project neo-logger-sdk.

Note: Don't forget to add --project neo-logger-sdk or else it will be added to the default project in your angular.json file.

Build

Run ng build neo-logger-sdk to build the project. The build artifacts will be stored in the dist/ directory.

Publishing

After building your library with ng build neo-logger-sdk, go to the dist folder cd dist/neo-logger-sdk and run npm publish.

Running unit tests

Run ng test neo-logger-sdk to execute the unit tests via Karma.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI README.