> Forward your [Meshblu]( messages and events to Splunk.
Last updated 6 years ago by octoblu .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install meshblu-splunk-forwarder 
SYNC missed versions from official npm registry.

Meshblu Splunk Forwarder

Forward your Meshblu messages and events to Splunk.

Oh, cool! But, why?

Meshblu devices contain lots of valuable data. Often times, you may want to analyze your data to discover interesting, meaningful patterns to better inform how you can react, plan, or predict. Meshblu Splunk Forwarder is a logger that enables you to forward your data to your Splunk instance.


  1. First, create a splunk config file.

  2. Now, we'll need to pull down Meshblu:

  • mkdir meshblu && cd $_
  • npm install meshblu
  1. Also, let's pull down the Meshblu Splunk Forwarder:
  • mkdir && cd $_
  • npm install meshblu-splunk-forwarder
  1. In order to more easily create a Meshblu device -- which is just a JSON object -- we'll use Meshblu Util:
  • npm install -g meshblu-util


Since Meshblu Splunk Forwarder is a part of Meshblu, we consider it a device and must be registered to Meshblu. Here's how to register your device:

meshblu-util register -s {YOUR-DOMAIN} > meshblu.json

Meshblu Util uses Meshblu to generate an UUID and token for your forwarder, registers it, and saves its configuration to meshblu.json.

Now, within your meshblu.json, we'll need to update the "server" property name to "hostname" (keep the value the same). Also, we need to add a "protocol" property with the value of "ws".

Here is how your meshblu.json (device configuration) should look:

  "uuid": "YOUR-UUID",
  "token": "YOUR-TOKEN",
  "hostname": "localhost",
  "port": "3000",
  "protocol": "ws",
  "type": "device:splunk"

You created your device. Awesome. This device is strictly a forwarder; it listens for messages from other devices to be logged/sent/forwarded to Splunk. So let's create another device, which this new forwarder can use.

  • mkdir device-a && cd $_

Again, in order to create and register a device, we'll use Meshblu Util.

meshblu-util register -o -s localhost:3000

Your new device may look something like this:

  "uuid": "GENERATED-UUID",
  "token": "GENERATED-TOKEN",
  "server": "localhost",
  "port": "3000",
  "type": "device:test"

Also in the sample device directory, let's create a message.json file -- a pretend message that our sample device happened to create and we intend to pass to the forwarder:

  "devices": ["*"],
  "payload": {
    "temp": 88


Now that we've installed packages and set-up devices, let's use 'em.

Open up a terminal, navigate to your meshblu directory to run meshblu with the following command:


Now that meshblu is running, open up a new terminal tab or window, navigate to your sample device's directory and run this command:

  • meshblu-util-message -f message.json

Using Meshblu Util, Meshblu will broadcast your message.json. The forwarder will listen for that message and push it to your splunk instance.

Current Tags

  • 1.0.2                                ...           latest (6 years ago)

3 Versions

  • 1.0.2                                ...           6 years ago
  • 1.0.1                                ...           6 years ago
  • 1.0.0                                ...           6 years ago
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 1
Dependencies (4)
Dev Dependencies (3)
Dependents (2)

Copyright 2014 - 2021 © |