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

good-splunk-http

v1.1.0

Published

Http(s) Splunk broadcasting for Good process monitor

Downloads

3

Readme

good-splunk-http

Http(s) Splunk broadcasting for Good process monitor

Build Status Current Version

Usage

good-splunk-http is a write stream use to send event to remote Splunk endpoints in batches. It makes a "POST" request with a JSON payload to the supplied endpoint. It will make a final "POST" request to the endpoint to flush the rest of the data on "finish". It conforms to the Splunk batch HTTP events format: http://dev.splunk.com/view/event-collector/SP-CAAAE6P.

Good Splunk Http

GoodSplunkHttp (endpoint, config)

Creates a new GoodSplunkHttp object where:

  • endpoint - full path to remote server to transmit logs.
  • config - configuration object
    • [threshold] - number of events to hold before transmission. Defaults to 20. Set to 0 to have every event start transmission instantly. It is strongly suggested to have a set threshold to make data transmission more efficient.
    • [errorThreshold] - number of consecutive failed transmissions allowed (ECONNRESET, ECONNREFUSED, etc). Defaults to 0. Failed events will be included in the next transmission until they are successfully logged or the threshold is reached (whichever comes first) at which point they will be cleared. Set to null to ignore all errors and always clear events.
    • [wreck] - configuration object to pass into wreck. Defaults to { timeout: 60000, headers: {} }. content-type is always "application/json".
    • [hecToken] - Splunk HEC token.

Schema

Each POST will match the following schema. The payload that is POSTed to the endpoint has the following schema:

{
  "host": "servername.home",
  "event": {
    "eventType": "log",
    "tags": ["request"],
    "data": {
      ...
    },
    "pid": 25685
  },
  "time": 1413464014739,
  ...
}

{
  "host": "servername.home",
  "event": {
    "eventType": "log",
    "tags": ["response"],
    "data": {
      ...
    },
    "pid": 25685
  },
  "time": 1414221317758,
  ...
}

{
  "host": "servername.home",
  "event": {
    "eventType": "log",
    "tags": ["request"],
    "data": {
      ...
    },
    "pid": 25685
  },
  "time": 1415088216608,
  ...
}