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 🙏

© 2025 – Pkg Stats / Ryan Hefner

winston-splunk-http-transport

v1.1.0

Published

A simple winston transport for logging to splunk.

Downloads

394

Readme

winston-splunk-http-transport

A simple winston transport for logging to Splunk via the HTTP Event Collector.

Log events are sent in batches by default. To disable batching, set the "splunk.batchInterval" config param to 0.

Installation

npm install --save winston winston-splunk-http-transport

Usage

const winston = require("winston");
const SplunkTransport = require("winston-splunk-http-transport");

// Now use winston as normal
const logger = winston.createLogger({
  transports: [new SplunkTransport({ splunk: { token: "your token" } })]
});

logger.info("Hello world!");

API

splunkTransport = new SplunkTransport(opts);

Create a new instance of SplunkTransport. Takes the following configuration:

  • opts: Transport configuration options.
  • opts.splunk: Splunk-specific transport options.
  • opts.splunk.token: The token used for connecting to the Splunk HTTP appender.
  • [opts.splunk.source=winston]: The value used for the "source" metadata passed to Splunk.
  • [opts.splunk.sourcetype=winston-splunk-http-transport]: The value used for the "sourcetype" metadata passed to Splunk.
  • [opts.batchInterval=1000]: The number of milliseconds to wait before flushing logs.
  • [opts.maxBatchCount=10]: The number of logs to batch before flushing.
  • [opts.maxBatchSize=1024]: The size of the batch, in bytes, to accumulate before flushing.
  • [opts.splunk.maxRetries=10]: The number of times the transport should retry sending failed batches.
  • [opts.splunk.url=https://localhost:8088]: The url used to connect to the Splunk appender.
  • [opts.splunk.index]: The Splunk index to log to. Logs to the default index for the token if not specified.