mirror of
https://github.com/bigchaindb/bigchaindb.git
synced 2024-10-13 13:34:05 +00:00
reorganize documentation
This commit is contained in:
parent
9b662ff199
commit
5bc591c6c4
17
README.md
17
README.md
@ -79,20 +79,3 @@ $ bigchaindb show-config
|
||||
```
|
||||
$ py.test -v
|
||||
```
|
||||
|
||||
#### Monitoring
|
||||
|
||||
BigchainDB uses [statsd](https://github.com/etsy/statsd) for monitoring. To fully take advantage of this functionality requires some additional infrastructure: an agent to listen for metrics (e.g. [telegraf](https://github.com/influxdata/telegraf)), a time-series database (e.g. [influxdb](https://influxdata.com/time-series-platform/influxdb/), and a frontend to display analytics (e.g. [Grafana](http://grafana.org/)).
|
||||
|
||||
For ease of use, we've provided a docker compose file that sets up all these services for testing. Simply run in the BigchainDB directory:
|
||||
|
||||
```sh
|
||||
$ docker-compose -f docker-compose-monitor.yml build
|
||||
$ docker-compose -f docker-compose-monitor.yml up
|
||||
```
|
||||
|
||||
and point a browser tab to `http://localhost:3000/dashboard/script/bigchaindb_dashboard.js`. Login and password are `admin` by default. If BigchainDB is running and processing transactions, you should see analytics—if not, start BigchainDB as above, and refresh the page after a few seconds.
|
||||
|
||||
If you're not interested in monitoring, don't worry: BigchainDB will function just fine without any monitoring setup.
|
||||
|
||||
Feel free to modify the [custom Grafana dashboard](https://github.com/rhsimplex/grafana-bigchaindb-docker/blob/master/bigchaindb_dashboard.js) to your liking!
|
@ -21,6 +21,7 @@ Table of Contents
|
||||
models
|
||||
json-serialization
|
||||
developer-interface
|
||||
monitoring
|
||||
contributing
|
||||
faq
|
||||
release-notes
|
||||
|
16
docs/source/monitoring.md
Normal file
16
docs/source/monitoring.md
Normal file
@ -0,0 +1,16 @@
|
||||
# Monitoring
|
||||
|
||||
BigchainDB uses [statsd](https://github.com/etsy/statsd) for monitoring. To fully take advantage of this functionality requires some additional infrastructure: an agent to listen for metrics (e.g. [telegraf](https://github.com/influxdata/telegraf)), a time-series database (e.g. [influxdb](https://influxdata.com/time-series-platform/influxdb/), and a frontend to display analytics (e.g. [Grafana](http://grafana.org/)).
|
||||
|
||||
For ease of use, we've provided a docker compose file that sets up all these services for testing. Simply run in the BigchainDB directory:
|
||||
|
||||
```text
|
||||
$ docker-compose -f docker-compose-monitor.yml build
|
||||
$ docker-compose -f docker-compose-monitor.yml up
|
||||
```
|
||||
|
||||
and point a browser tab to `http://localhost:3000/dashboard/script/bigchaindb_dashboard.js`. Login and password are `admin` by default. If BigchainDB is running and processing transactions, you should see analytics—if not, start BigchainDB as above, and refresh the page after a few seconds.
|
||||
|
||||
If you're not interested in monitoring, don't worry: BigchainDB will function just fine without any monitoring setup.
|
||||
|
||||
Feel free to modify the [custom Grafana dashboard](https://github.com/rhsimplex/grafana-bigchaindb-docker/blob/master/bigchaindb_dashboard.js) to your liking!
|
Loading…
x
Reference in New Issue
Block a user