tendermint/tm-monitor
Anton Kaliaev 31a54b0840
[tm-monitor] extract lib to monitor/ dir
because tm-bench needs these structures
2017-03-16 14:53:32 +04:00
..
eventmeter merge go-event-meter into tm-monitor (Refs #4) 2017-03-07 12:39:33 +04:00
mock merge go-event-meter into tm-monitor (Refs #4) 2017-03-07 12:39:33 +04:00
monitor [tm-monitor] extract lib to monitor/ dir 2017-03-16 14:53:32 +04:00
Dockerfile link 2 docker containers 2017-03-02 22:14:32 +04:00
Dockerfile.dev [tm-monitor] rename netmon to tools 2017-03-06 22:02:15 +04:00
LICENSE tm-monitor 0.1.0 2017-03-01 23:01:52 +04:00
Makefile [tm-monitor] extract lib to monitor/ dir 2017-03-16 14:53:32 +04:00
README.md [tm-monitor] new screencast 2017-03-06 22:41:02 +04:00
glide.lock [tm-monitor] extract lib to monitor/ dir 2017-03-16 14:53:32 +04:00
glide.yaml [tm-monitor] extract lib to monitor/ dir 2017-03-16 14:53:32 +04:00
main.go [tm-monitor] extract lib to monitor/ dir 2017-03-16 14:53:32 +04:00
rpc.go [tm-monitor] extract lib to monitor/ dir 2017-03-16 14:53:32 +04:00
ton.go [tm-monitor] extract lib to monitor/ dir 2017-03-16 14:53:32 +04:00

README.md

Tendermint monitor (tm-monitor)

Tendermint monitor watches over one or more Tendermint core applications (nodes), collecting and providing various statistics to the user.

QuickStart using Docker

docker run -it --rm -v "/tmp:/tendermint" tendermint/tendermint init
docker run -it --rm -v "/tmp:/tendermint" -p "46657:46657" --name=tm tendermint/tendermint

docker run -it --rm --link=tm tendermint/monitor tm:46657

QuickStart using binaries

Linux:

curl -L https://s3-us-west-2.amazonaws.com/tendermint/0.8.0/tendermint_linux_amd64.zip && sudo unzip -d /usr/local/bin tendermint_linux_amd64.zip && sudo chmod +x tendermint
tendermint init
tendermint node --app_proxy=dummy

tm-monitor localhost:46657

Max OS:

curl -L https://s3-us-west-2.amazonaws.com/tendermint/0.8.0/tendermint_darwin_amd64.zip && sudo unzip -d /usr/local/bin tendermint_darwin_amd64.zip && sudo chmod +x tendermint
tendermint init
tendermint node --app_proxy=dummy

tm-monitor localhost:46657

Usage

tm-monitor [-v] [-no-ton] [-listen-addr="tcp://0.0.0.0:46670"] [endpoints]

Examples:
        # monitor single instance
        tm-monitor localhost:46657

        # monitor a few instances by providing comma-separated list of RPC endpoints
        tm-monitor host1:46657,host2:46657
Flags:
  -listen-addr string
        HTTP and Websocket server listen address (default "tcp://0.0.0.0:46670")
  -no-ton
        Do not show ton (table of nodes)
  -v    verbose logging

asciicast

RPC UI

Run tm-monitor and visit http://localhost:46670. You should see the list of the available RPC endpoints:

http://localhost:46670/status
http://localhost:46670/status/network
http://localhost:46670/monitor?endpoint=_
http://localhost:46670/status/node?name=_
http://localhost:46670/unmonitor?endpoint=_

The API is available as GET requests with URI encoded parameters, or as JSONRPC POST requests. The JSONRPC methods are also exposed over websocket.

Ideas

  1. Currently we get IPs and dial, but should reverse so the nodes dial the netmon, both for node privacy and easier reconfig (validators changing ip/port).
  2. Uptime over last day, month, year (Q: how do I get this?)
  3. statsd output (plugin?)
  4. log metrics for charts (Q: what charts?)
  5. show network size (Q: how do I get the number?)
  6. metrics RPC (Q: do we need this?)