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

@livy/http-handler

v1.0.4

Published

Sends Livy log records to an HTTP endpoint

Downloads

85

Readme

@livy/http-handler

This Livy handler sends log records to an HTTP endpoint using got.


Synchronous logger support: no

Runtime: Node.js


Basic Example

const { HttpHandler } = require('@livy/http-handler')

const handler = new HttpHandler('https://example.com/logs')

Installation

Install it via npm:

npm install @livy/http-handler

Options

The first argument to this handler's constructor determines where to send logs.

It is either

  • the URL endpoint (as a string):

    new HttpHandler('https://example.com')
  • a got options object:

    new HttpHandler({
      url: 'https://example.com/logs',
      method: 'post'
    })
  • a callback creating one of the above from a log record (or an array of log records when batch-handling and allowBatchRequests is enabled):

    new HttpHandler(record => `https://example.com/logs/${record.channel}`)

An object of options can be passed to the constructor as the second argument.

The following options are available:

allowBatchRequests

Type: boolean

Default: false

Description: Whether batch handling should send all pending records as an array in one request

bubble

Type: boolean

Default: true

Description: Controls whether records handled by this handler should bubble up to other handlers.

See also: Bubbling

level

Type: LogLevel

Default: 'debug'

Description: Controls which log records should be handled based on their log level.

requestOptions

Type: object | (record: LogRecord | LogRecord[]) => object

Default: false

Description: got options to use. May be the bare options object or a callback creating that object from a log record (or an array of log records when batch-handling and allowBatchRequests is enabled).

sequential

Type: boolean

Default: false

Description: Whether HTTP requests in batch handling must be executed sequentially instead of in parallel. This has no effect if allowBatchRequests is enabled.

Public API

bubble

Controls whether records handled by this handler should bubble up to other handlers. Initially set through the bubble option.

See also: Bubbling

level

The minimum log level of a log record to be considered by this handler. Initially set through the level option.

processors

This handler supports processors by implementing the ProcessableHandlerInterface.

reset()

This handler implements the ResettableInterface. Resetting it resets all attached processors.

You usually don't want to call this method manually on an individual handler. Consider calling it on the logger instead.