Monitoring a Node with Prometheus
- 1.In contrast to EKG, Prometheus allows monitoring a Cardano Node running on an AWS instance without the need for port forwarding. We do however need to configure the AWS firewall to open the right port. If we want to use port 12789, we have to add a new inbound rule to the launch wizard of our browser.You can find the link in the Instances dashboard of the AWS console
Click "Edit inbound rules".
Then add a new rule for "Custom TCP", port range 12789, source "Anywhere".
- 1.On the AWS instance we edit the node configuration file shelley_testnet-config.json providing the host and port:hasPrometheus:- "0.0.0.0"- 12789(Using
0.0.0.0as host will bind to all provided interfaces, all of which you can list with
ifconfig. You can be more selective if you want and provide a specific IP-address instead.)
- 2.We restart the node, and it will now make Prometheus metrics available at port 12789 (or whatever port you specified in
- 4.Prometheus needs to be configured to monitor your Cardano Node. A minimalistic configuration file doing this could look like this:global:scrape_interval: 15sexternal_labels:monitor: 'codelab-monitor'scrape_configs:- job_name: 'cardano' # To scrape data from the cardano nodescrape_interval: 5sstatic_configs:- targets: ['a.b.c.d:12789']- job_name: 'node' # To scrape data from a node exporter to monitor your linux host metrics.scrape_interval: 5sstatic_configs:- targets: ['a.b.c.d:9100']You have to replace
a.b.c.dwith the public IP-address of your Cardano Node server, which you can find on the dashboard under IPv4 Public IP.
- 5.Start Prometheus on your local machine or monitoring server with this configuration, for example:$ ./prometheus --config.file=prometheus.yml
- 6.Start Prometheus node exporter on your Cardano node server, for example:$ ./node_exporter
- 7.On your browser open
a.b.c.d:9090, pick one or more interesting metrics to graph and enjoy!
**NOTE: Security configurations you should perform on your monitoring server are out of scope for this tutorial.