Indy Node Monitor is a set of tools for monitoring the status of an Indy Ledger by querying the validator information of the nodes on the ledger. These tools are integrated into a full monitoring stack including the following components:
This allows you to:
The stack is easily managed and spun up in docker using the included ./manage
script. Starting the stack is as easy as:
./manage build
./manage start
A browser window to the Grafana instance should launch automatically. The login username is admin
and the password foobar
. Once logged in you are able to browse the various (auto-provisioned) dashboards which will begin to populate after a few minutes. Please note:- In order to collect detailed data from the network to populate many of the graphs you will require a privileged DID (NETWORK_MONITOR at minimum) on the ledger and you will need to configure the monitoring stack with the seed(s).
For more information about the commands available in the ./manage
script refer to the command list
For more infomration on how to setup and use the monitoring stack refer to this readme
This simple tool is the heart of the Indy Node Monitor. It is used to retrieve "validator-info"—detailed status data about an Indy node (aka "validator")—from all the nodes in a network. The results are returned as a JSON array with a record per validator, and the data can be manipulated and formatted through the use of plugins. Fetch validator status can be used as a stand-alone command line tool or through the Indy Node Monitor REST API which is used by the monitoring stack. The Indy Node Monitor REST API can be spun up easily by running ./manage start indy-node-monitor
, and a browser window will automatically launch to display the API documents and interface.
For more details see the Fetch Validator Status readme
For more details on how to contribute follow the link to this readme
Pull requests are welcome! Please read our contributions guide and submit your PRs. We enforce developer certificate of origin (DCO) commit signing. See guidance here.
We also welcome issues submitted about problems you encounter in using the tools within this repo.
All contributors are required to adhere to our Code of Conduct guidelines.