Hi.
Just a quick shoutout, If you would like to test or see our dashboard used in our pool JAWS & JAWSX. It was just released, you can download it from github (there’s some screenshots in the github aswell). Original by Umed [SKY], where our derivate is based on.
That’s a nice dashboard!
Thank you for sharing your dashboard @ada_jaws! Based on it, I’m able to create our own, which is for a less complex setup of only 3 separate servers - 1 core and 2 relays.
Sharing it here for anyone who have the same setup as ours at [PHRCK]. You can download it from [here].
Great work @nimrod. Great to see that you got it working, and thanks for sharing your work to the community.
Hi @nimrod,
very nice dashboard that you created here. I wanted to try it out by I am stuck with the “alias” part of your json file. Where do I have to define the alias=“relay1” etc?
Thanks and best regards
Tom
@Tom_ADADE, you’ll have to specify that in the prometheus yaml config file. Here’s how it appears in ours:
# global configs
global:
scrape_interval: 15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
# scrape_timeout is set to the global default (10s).
scrape_configs:
- job_name: 'cardano' # To scrape data from the running cardano-node
scrape_interval: 15s
static_configs:
- targets: ['123.123.12.12:9999']
labels:
alias: 'relay1'
type: 'cardano-node'
- targets: ['123.123.12.13:9999']
labels:
alias: 'relay2'
type: 'cardano-node'
- targets: ['123.123.12.14:9999']
labels:
alias: 'core'
type: 'cardano-node'
- job_name: 'node' # To scrape data from a node exporter to monitor the linux host metrics.
scrape_interval: 15s
static_configs:
- targets: ['123.123.12.12:9988']
labels:
alias: 'relay1'
type: 'host-system'
- targets: ['123.123.12.13:9988']
labels:
alias: 'relay2'
type: 'host-system'
- targets: ['123.123.12.14:9988']
labels:
alias: 'core'
type: 'host-system'
That’s the content of the config file you provide as --config.file argument when running prometheus.
Thanks for the tip @nimrod related to Pooling pool data from adapools.
Here is what I come up with after tweaking the above JSON.
glad you got it working!
Hi @nimrod,
I hope this finds you well. Thank you (and everyone else) for sharing their dashboards. I had made my own, but ended up choosing to piggy back on yours as my setup is very similar, and yours looked soooo much better 
I have a question: you have some metrics (for example active stake, live stake, pledge, etc) which are not “standard” for node exporter or the Cardano metrics. How does one create custom metrics? And where do they need to go for prometheus to pick them up?
Thank you in advance for your time,
A
That’s what @rodrigo is talking about in his reply above. 
See the link he provided on his post.
This is the same question asked by @Tom_ADADE above also. You’ll find the answer to your question in my reply to that. Hope this helps! 
Hi Rodrigo,
how did you achieve to have infos like ,LiveStake,Pledged, Delegators and more?
did you use the link you posted “Adding Pool Stats to Grafana Dashboard | Crypto2099” aand then you have all this infoss?
i find it really cool and useful.
Thom
PS
have a nice great new year
ok i see 
i will try it.
thaank you all
hi ,
i used this link Adding Pool Stats to Grafana Dashboard | Crypto2099
is reaally great this solution.
there is info " by visiting http://localhost:9100/metrics on your local machine".
did you find a way to change this port?
normally i use different port for the node_exporter.
Thank you in advanced,
Thom
Hey there!
I wrote a tutorial to configure and create a grafana dashboard from scratch: Monitoring with Grafana
This is my grafana dashboard: download here ADABooster_Monitor
You need to specify the port in the systemctl service file.
sudo find / -name node-exporter.service
vim path-to/node-exporter.service
Find this line:
ExecStart=/usr/local/bin/node_exporter
and change it to:
ExecStart=/usr/local/bin/node_exporter --web.listen-address=:<port>
sudo systemctl start node-exporter
Hi,
I would like to share my dashboard too. Monitoring is realy a cool part of a stake pool project. 
http://dashboard.qcada.com:3000
Grafana wiht Prometheus is realy powerfull, i will certainly give a try with GitLab, Apache or VMware!
I don’t have metrics about Blocks because QcADA is a baby pool for now
Here are variables for two nodes (block_producer and relay1) in prometheus.yml
static_configs:
- targets: ['block_producer_IP:9100']
labels:
alias: 'core'
type: 'core'
- targets: ['relay1_IP:9100']
labels:
alias: 'relay1'
type: 'cardano-node'
- targets: ['block_producer_IP:12798']
labels:
alias: 'block-producer-node'
type: 'core'
- targets: ['relay1_IP:12798']
labels:
alias: 'relay-node1'
type: 'cardano-node'
To download : https://www.qcada.com/share/grafana-dashboard-QcADA.json
Comments or suggestions are welcome
Luc [QcADA]
Hi,
With the new update 1.25.1, metrics name changed and Prometheus can’t find the data.
Any idea ?
Yes, update ur panels in grafana with cardano_node_metrics
For example
cardano_node_metrics_remainingKESPeriods_int
Or
cardano_node_metrics_txsProcessedNum_int
