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

@dvsa/azure-logger

v7.0.0

Published

Shareable Logging Facade, implemented with Winston

Downloads

87

Readme

Azure Logger

Winston Logger with a custom Azure Application Insights Transport

Logging levels

  • critical
  • error
  • warning
  • event
  • request
  • dependency
  • security
  • audit
  • info
  • debug

Installation

If using npm:

npm install @dvsa/azure-logger

or if using Yarn

yarn add @dvsa/azure-logger

Specify the environment variables in a .env file, for example

LOG_LEVEL=event

NODE_ENV=development

APPLICATIONINSIGHTS_CONNECTION_STRING={APPLICATION_INSIGHTS_CONNECTION_STRING}

Example Use:

  1. Create a file logger.ts and export the azure logger from it, instantiating it with the project and component names.
import { Logger } from '@dvsa/azure-logger';

export default new Logger('ftts', 'ftts-location-api');
  1. For Azure Functions, two wrappers are provided to enable auto correlation of all logs and telemetry including external requests and dependencies. For HTTP triggers use the httpTriggerContextWrapper with req passed in. Use nonHttpTriggerContextWrapper for all other trigger types. For example, wrap a time trigger function in your function index file like so:
import { nonHttpTriggerContextWrapper } from '@dvsa/azure-logger';
import { AzureFunction, Context } from '@azure/functions';

const myTimeTrigger: AzureFunction = async (): Promise<void> => {
    // do something
};

export default async (context: Context): Promise<void> => nonHttpTriggerContextWrapper(myTimeTrigger, context);

Request and dependency log methods are still provided for manual tracing if it is needed e.g. for service bus correlation. These require context to be passed in to fetch the correct trace ids.

  1. Whenever you want to log an item import the logger.ts file.
import logger from './logger';

function getData(): void {
    try {
        // Do calculations
    } catch(error) {
        logger.error(error);
    }
}

APPLICATIONINSIGHTS_CONNECTION_STRING

When using an Azure function app the following environment variable must be present and contain the connection string for the application insights instance you wish to use.

APPLICATIONINSIGHTS_CONNECTION_STRING