History

kdeme 48391744ff Add metrics config files generation for wakusim		2020-01-23 12:39:36 +02:00
..
docker	Add waku node Dockerfile [skip ci]	2020-01-23 12:39:36 +02:00
examples	Add metrics config files generation for wakusim	2020-01-23 12:39:36 +02:00
rpc	Generate and use random topics in waku simulation	2020-01-23 12:39:36 +02:00
README.md	Add metrics config files generation for wakusim	2020-01-23 12:39:36 +02:00
config.nim	Add lightNode and logMetrics options	2020-01-23 12:39:36 +02:00
nim.cfg	Start implementation of waku node	2020-01-23 12:39:36 +02:00
process_dashboard.nim	Add metrics config files generation for wakusim	2020-01-23 12:39:36 +02:00
quicksim.nim	Generate and use random topics in waku simulation	2020-01-23 12:39:36 +02:00
start_network.sh	Add metrics config files generation for wakusim	2020-01-23 12:39:36 +02:00
wakunode.nim	Add quick waku simulation with hardcoded network	2020-01-23 12:39:36 +02:00

README.md

Introduction

wakunode is a cli application that allows you to run a Waku enabled node.

The application and Waku specification are still experimental and fully in flux.

Additionally the original Whisper (EIP-627) protocol can also be enabled as can an experimental Whisper - Waku bridging option.

How to Build & Run

make wakunode
./build/wakunode --help

Using Metrics

Metrics are available for valid envelopes and dropped envelopes.

To compile in an HTTP endpoint for accessing the metrics we need to provide the insecure flag:

make NIMFLAGS="-d:insecure" wakunode
./build/wakunode --metrics-server

Ensure your Prometheus config prometheus.yml contains the targets you care about, e.g.:

scrape_configs:
  - job_name: "waku"
    static_configs:
      - targets: ['localhost:8008', 'localhost:8009', 'localhost:8010']

For visualisation, similar steps can be used as is written down for Nimbus here.

There is a similar example dashboard that includes visualisation of the envelopes available at waku/examples/waku-grafana-dashboard.json.

Testing Waku Protocol

One can set up several nodes, get them connected and then instruct them via the JSON-RPC interface. This can be done via e.g. web3.js, nim-web3 (needs to be updated) or simply curl your way out.

The JSON-RPC interface is currently the same as the one of Whisper. The only difference is the addition of broadcasting the topics interest when a filter with a certain set of topics is subcribed.

Example of a quick simulation using this approach:

# Build wakunode + quicksim
make NIMFLAGS="-d:insecure" wakusim

# Start the simulation nodes
./waku/start_network.sh
# Or when multitail is installed
USE_MULTITAIL="yes" ./waku/start_network.sh

# In another shell
./build/quicksim

The start_network.sh script will also provide a prometheus.yml with targets set to all simulation nodes that are started. This way you can easily start prometheus with this config, e.g.:

cd waku/metrics/prometheus
prometheus

A Grafana dashboard containing the example dashboard for each simulation node is also generated and can be imported in case you have Grafana running. This dashboard can be found at ./waku/metrics/waku-sim-all-nodes-grafana-dashboard.json