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

juttle-splunk-adapter

v0.1.2

Published

Juttle adapter for Splunk

Downloads

10

Readme

Juttle Splunk Adapter

Build Status

Splunk adapter for the Juttle data flow language, with read support.

Currently supports Splunk 6.3.

Examples

Read entries from the _internal index where the host is www123:

read splunk index='_internal' host='www123' | view text

Installation

Like Juttle itself, the adapter is installed as a npm package. Both Juttle and the adapter need to be installed side-by-side:

$ npm install juttle
$ npm install juttle-splunk-adapter

Configuration

The adapter needs to be registered and configured so that it can be used from within Juttle. To do so, add the following to your ~/.juttle/config.json file:

{
    "adapters": {
        "splunk": {
            "scheme": "https",
            "host": "localhost",
            "port": "8089",
            "username": "admin",
            "password": "splunk"
        }
    }
}

The scheme, host and port should point to the API url of your Splunk instance. The default settings of https, localhost and 8089 will be used as defaults.

Please note that Splunk 6.3 won't allow access to the API if default admin password changeme is used. To enable it, please change the password and update the Juttle config accordingly.

Usage

Read options

When reading data, large part of SPL syntax is expressible through and similar to Juttle filter expressions.

Notable omissions, which aren't translated from Juttle to SPL are:

  • Juttle supports in operator for testing inclusion of a value in an array. This operator is missing from SPL. This Juttle query can be rewritten using a sequence of or operators.

  • Juttle supports filtering results using regular expression operators on fields - =~ and !~. Instead, SPL uses | regex filter to accomplish a similar task. Same pattern can be used in Juttle - read splunk ... | filter field =~ /regexp/.

The following options are supported by read:

Name | Type | Required | Description -----|------|----------|------------- fields | string | no | additional fields to add to the results (default: none) from | moment | no | select points after this time (inclusive) to | moment | no | select points before this time (exclusive)

The filter expressions can be placed after the above options in read splunk. Supported filters are:

  • fieldname = value also !=, and </> for numbers
  • combining filter expressions with AND, OR, NOT

Contributing

Want to contribute? Awesome! Don’t hesitate to file an issue or open a pull request.