16 releases (5 breaking)
|0.6.3||Jun 30, 2021|
|0.6.2||Apr 23, 2021|
|0.5.1||Dec 21, 2020|
|0.4.0||Nov 28, 2020|
|0.1.3||Sep 13, 2020|
#305 in Command line utilities
23 downloads per month
Status: working on Windows, MacOS and Linux and helping with Fleming testnets.
vdash is already capable of monitoring multiple logfiles on the local machine, so it
wouldn't be hard to monitor multiple remote nodes by having them publish updates to their
logfiles (e.g. using a web server) and appending changes to local copies monitored by
vdash, but this is not on the roadmap. There may even be existing tools that could do
this so if anyone wants to look into that it would be great as I'm only making
minor changes at the moment.
Here's an early
vdash (v0.2.0) working with a local testnet node:
vdash will load historic metrics from one or more Safe node
logfiles and display these with live updates in the terminal (see above).
You can cycle through different Safe nodes using left/right arrow keys, and zoom the timeline scale in/out using 'i' and 'o' (or '+' and '-').
Press 'q' to quit.
Feature requests and discussion are currently summarised in the opening post of the Safe Network forum topic: Node Dashboard ideas please!.
For more details and progress see Roadmap (below).
- Linux: works on Linux (tested on Ubuntu).
- Windows: works on Windows 10.
- MacOS: works on MacOS.
1 Install Rust via https://doc.rust-lang.org/cargo/getting-started/installation.html
2a. Linux (Ubuntu)
sudo apt-get install build-essential
2b. Linux/MacOS install vdash:
cargo install vdash vdash --help
2c. Windows install vdash-crossterm:
To install on Windows you must build manually and use the 'nightly' compiler
until the 'itarget' feature becomes part of 'stable', so install Rust nightly
rustup toolchain install nightly
vdash-crossterm on Windows, clone vdash, build with
+nightly and use the binary it creates under
git clone https://github.com/happybeing/vdash cd vdash cargo +nightly build -Z features=itarget --bin vdash-crossterm --release --no-default-features ./target/release/vdash-crossterm --help
vdash is provides a terminal based graphical dashboard of SAFE Network Node activity on the local machine. It parses input from one or more node logfiles to gather live node metrics which are displayed using terminal graphics.
Status: work-in-progress, not useful yet unless you want to help!
Get the SAFE CLI: either download using an install script or build the SAFE CLI locally. Instructions for both options are here.
Get the SAFE Node: when you have the SAFE CLI working you can install the node software with the command
safe node install(details here).
You are now ready to install
vdash and can test it by running a local test network.
In the terminal type the command and the paths of one or more node logfiles you want to monitor. For example:
When the dashboard is active, pressing 's' or 'd' switches between summary and detail views. For more information:
IMPORTANT: You must ensure the node logfile includes the telemetry information used by vdash by setting the required logging level (e.g. 'info', or 'debug' etc).
The required level may change as things progress, so for now I recommend using a logging level of 'info' to keep resources minimal. The logfile will be larger and vdash become slower, but may have access to more metrics if you increase the logging level to 'debug', or even 'trace'.
You control the node logging level by setting the environment variable
RUST_LOG but be aware that setting this to one of to one of 'warn', 'info', 'debug', or 'trace' will apply this to all modules used by
sn_node code, not just the
sn_node module. You can though set the default to one level and different levels for other modules.
For example, to set the default level to 'debug' for everything, except for the
quinn module which generates a lot of unnecessary INFO log messages, module use:
safe node killall rm -f ~/.safe/node/local-test-network/*/sn_node.log RUST_LOG=safe=trace safe node join
save node killallmakes sure no existing nodes are still running, and deleting existing logfiles prevents you picking up statistics from previous activity. If you leave the logfile in place then
vdashwill waste time processing that, although you can skip that process using a command line option.
setting RUST_LOG ensures the logfiles contain the data which vdash needs, and excludes some that gets in the way.
On Windows to set RUST_LOG environment variable:
Using Windows Command Line:
set RUST_LOG="safe=trace" safe node run-baby-fleming -t
Using Windows PowerShell:
$env:RUST_LOG="safe=trace" safe node run-baby-fleming -t
Start a local test network: follow the instructions to Run a local network, but I suggest using the
-toption to create an account and authorise the CLI with it altogether. As here:
safe node killall rm -f ~/.safe/node/local-test-network/*/sn_node.log RUST_LOG=safe=trace safe node run-baby-fleming -t
Windows: see "Note" immediately above for how to set RUST_LOG on Windows.
Run vdash: in a different terminal window (so you can continue to use the safe-cli in the first terminal), start
Or with a live network:
Upload files using SAFE CLI: in the SAFE CLI window you can perform operations on the local test network that will affect the node and the effects will be shown in
vdash. For example, to use the SAFE CLI to upload files:
safe files put ./<some-directory>/ --recursive
If you want to try
vdash with a live network, check to see if one is running at the SAFE Network community forum: https://safenetforum.org
git clone https://github.com/happybeing/vdash cd vdash
vdash with the termion backend (see tui-rs).
Note: MacOS is untested but may 'just work'.
cargo build --features="termion" --features="vdash" --release
vdash the crossterm backend (see tui-rs), with the intention to support Windows.
NOT working on Windows yet, this is being worked on at the moment. Help with testing appreciated.
cargo build --bin vdash-crossterm --features="crossterm" --features="vdash" --release
vdash is headed:
- implement ability to parse logfiles
- add --debug-parser to show results in second logfile
- implement parsing log file for simple metrics and timeline
- keep the debug UI available (selected with 'D' when using --debug-parse)
- change events to use tokio mpsc (unbounded) channel
- does tokio mpsc fix loss of updates from linemux (see linemux issue #17)
- implement node dashboard
- node status summary page (single node)
- debug window (--debug-window)
- add basic node stats (age/PUTs/GETs)
- scroll node logfile (arrow keys)
- multiple nodes (navigate with tab and arrow keys)
- add a timeline
- simple timeline with PUTS and GETS
- implement multiple timeline durations (hour, minute etc)
- add status/timeline for ERRORS
- anchor 'now' to right border
- mod sparkline widget to have a minimum Y scale (e.g. 10 units)
- reduce lag in processing logfile changes
- implement simple rate limit on redraws
- implement update/redraw tick (for timeline and stats)
- fix load from logfile to timeline (currently all ends up in last bucket)
- change timeline scaling to use +/- an i/o keys rather than s, m, d etc
- optimise redraw rate limit
- make a CLI option for redraw rate limit
- track sn_node issue #1126 (maintain Get/Put response in)
- implement storage 'meter'
- code to get node storage used
- code to get free space on same device
- implement storage used/free 'progress' bar
- implement bandwidth 'meter'
- code to get node bandwidth
- code to get total bandwidth
- implement bandwidth node/total/max in last day 'progress' bar
- Implement DashOverview: all nodes on one page (rename from DashSummary)
- trim NodeMetrics timeline
- logtail-dash Issue #1: Implement popup help on ?, h, H
- FIXED by upate to tui-rs v0.11.0 Issue #382: Window titles corrupted when using --debug-window
- Implement --features="vdash" / --features="logtail" to select app and UI
Everything is GPL3.0 unless otherwise stated. Any contributions are accepted on the condition they conform to this license.
See also ./LICENSE