|
@ -13,17 +13,17 @@ Assuming your application is running in another container with the name |
|
|
`app`: |
|
|
`app`: |
|
|
|
|
|
|
|
|
docker run -it --rm -v "/tmp:/tendermint" tendermint/tendermint init |
|
|
docker run -it --rm -v "/tmp:/tendermint" tendermint/tendermint init |
|
|
docker run -it --rm -v "/tmp:/tendermint" -p "46657:46657" --name=tm --link=app tendermint/tendermint node --proxy_app=tcp://app:46658 |
|
|
|
|
|
|
|
|
docker run -it --rm -v "/tmp:/tendermint" -p "26657:26657" --name=tm --link=app tendermint/tendermint node --proxy_app=tcp://app:26658 |
|
|
|
|
|
|
|
|
docker run -it --rm -p "46670:46670" --link=tm tendermint/monitor tm:46657 |
|
|
|
|
|
|
|
|
docker run -it --rm -p "26670:26670" --link=tm tendermint/monitor tm:26657 |
|
|
|
|
|
|
|
|
If you don't have an application yet, but still want to try monitor out, |
|
|
If you don't have an application yet, but still want to try monitor out, |
|
|
use `kvstore`: |
|
|
use `kvstore`: |
|
|
|
|
|
|
|
|
docker run -it --rm -v "/tmp:/tendermint" tendermint/tendermint init |
|
|
docker run -it --rm -v "/tmp:/tendermint" tendermint/tendermint init |
|
|
docker run -it --rm -v "/tmp:/tendermint" -p "46657:46657" --name=tm tendermint/tendermint node --proxy_app=kvstore |
|
|
|
|
|
|
|
|
docker run -it --rm -v "/tmp:/tendermint" -p "26657:26657" --name=tm tendermint/tendermint node --proxy_app=kvstore |
|
|
|
|
|
|
|
|
docker run -it --rm -p "46670:46670" --link=tm tendermint/monitor tm:46657 |
|
|
|
|
|
|
|
|
docker run -it --rm -p "26670:26670" --link=tm tendermint/monitor tm:26657 |
|
|
|
|
|
|
|
|
### Using Binaries |
|
|
### Using Binaries |
|
|
|
|
|
|
|
@ -34,37 +34,37 @@ then run: |
|
|
tendermint init |
|
|
tendermint init |
|
|
tendermint node --proxy_app=kvstore |
|
|
tendermint node --proxy_app=kvstore |
|
|
|
|
|
|
|
|
tm-monitor localhost:46657 |
|
|
|
|
|
|
|
|
tm-monitor localhost:26657 |
|
|
|
|
|
|
|
|
with the last command being in a seperate window. |
|
|
with the last command being in a seperate window. |
|
|
|
|
|
|
|
|
## Usage |
|
|
## Usage |
|
|
|
|
|
|
|
|
tm-monitor [-v] [-no-ton] [-listen-addr="tcp://0.0.0.0:46670"] [endpoints] |
|
|
|
|
|
|
|
|
tm-monitor [-v] [-no-ton] [-listen-addr="tcp://0.0.0.0:26670"] [endpoints] |
|
|
|
|
|
|
|
|
Examples: |
|
|
Examples: |
|
|
# monitor single instance |
|
|
# monitor single instance |
|
|
tm-monitor localhost:46657 |
|
|
|
|
|
|
|
|
tm-monitor localhost:26657 |
|
|
|
|
|
|
|
|
# monitor a few instances by providing comma-separated list of RPC endpoints |
|
|
# monitor a few instances by providing comma-separated list of RPC endpoints |
|
|
tm-monitor host1:46657,host2:46657 |
|
|
|
|
|
|
|
|
tm-monitor host1:26657,host2:26657 |
|
|
Flags: |
|
|
Flags: |
|
|
-listen-addr string |
|
|
-listen-addr string |
|
|
HTTP and Websocket server listen address (default "tcp://0.0.0.0:46670") |
|
|
|
|
|
|
|
|
HTTP and Websocket server listen address (default "tcp://0.0.0.0:26670") |
|
|
-no-ton |
|
|
-no-ton |
|
|
Do not show ton (table of nodes) |
|
|
Do not show ton (table of nodes) |
|
|
-v verbose logging |
|
|
-v verbose logging |
|
|
|
|
|
|
|
|
### RPC UI |
|
|
### RPC UI |
|
|
|
|
|
|
|
|
Run `tm-monitor` and visit http://localhost:46670 You should see the |
|
|
|
|
|
|
|
|
Run `tm-monitor` and visit http://localhost:26670 You should see the |
|
|
list of the available RPC endpoints: |
|
|
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=_ |
|
|
|
|
|
|
|
|
http://localhost:26670/status |
|
|
|
|
|
http://localhost:26670/status/network |
|
|
|
|
|
http://localhost:26670/monitor?endpoint=_ |
|
|
|
|
|
http://localhost:26670/status/node?name=_ |
|
|
|
|
|
http://localhost:26670/unmonitor?endpoint=_ |
|
|
|
|
|
|
|
|
The API is available as GET requests with URI encoded parameters, or as |
|
|
The API is available as GET requests with URI encoded parameters, or as |
|
|
JSONRPC POST requests. The JSONRPC methods are also exposed over |
|
|
JSONRPC POST requests. The JSONRPC methods are also exposed over |
|
|