Hi @max_ruas !
That means that needed metrics are being published by cardano-node. Now you need to go to explore menu of Grafana and try to find it. if you can’t find it, please share with me your prometheus.yml
config
Hi @max_ruas !
That means that needed metrics are being published by cardano-node. Now you need to go to explore menu of Grafana and try to find it. if you can’t find it, please share with me your prometheus.yml
config
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).
# Attach these labels to any time series or alerts when communicating with
# external systems (federation, remote storage, Alertmanager).
external_labels:
monitor: 'example'
# Alertmanager configuration
alerting:
alertmanagers:
- static_configs:
- targets: ['localhost:9093']
# Load rules once and periodically evaluate them according to the global 'evaluation_interval'.
rule_files:
# - "first_rules.yml"
# - "second_rules.yml"
# A scrape configuration containing exactly one endpoint to scrape:
# Here it's Prometheus itself.
scrape_configs:
# The job name is added as a label `job=<job_name>` to any timeseries scraped from this config.
- job_name: 'prometheus'
# Override the global default and scrape targets from this job every 5 seconds.
scrape_interval: 5s
scrape_timeout: 5s
# metrics_path defaults to '/metrics'
# scheme defaults to 'http'.
static_configs:
- targets: ['localhost:9090']
- job_name: node
# If prometheus-node-exporter is installed, grab stats about the local
# machine by default.
static_configs:
- targets: ['localhost:9100'] ```
Seems you don’t have it in your prometheus.yml
you should have targets defined with localhost:12798
P.S.
I would recommend you to put your config in code block, otherwise it a bit of mess and hard to view.
You should use ``` for beginning of code block and end:
something like this:
```
CODE
```
It Worked I had to take the ChainDB from the config on grafana panel. example:
from
cardano_node_ChainDB_metrics_slotInEpoch_int
to
cardano_node_metrics_slotInEpoch_int
Thanks again all,
Now I’m missing this panels: can someone please share the correct configuration,
I’m running Ubuntu
Node Bandwidth (bps)
Slot length
Cardano Service Restarts Per Hour
Rejected blocks since last restart
Slot leading share (% of slots led)
Cluster Aggregate Bandwidth (bps)
Node R$S (allocated memory in RAM, in MB)
Current KES Period
Cheers
Hi @max_ruas !
You need to check what metrics are being used for those panels and try to find them in Grafana explore. Maybe again you need to remove “ChainDB” word or similar. I don’t use those panels so for me it is unclear what you are missing.
These seem to be some old panels so the metrics might be outdated. Use the one in my tutorial above.
Thanks I will check it out
Hey i do have an issue with step 5.
I was able to setup a dashboard and i also do see the panels from my relays. But there are no data shown from the block producer itself.
@SNSKY are you still around?
Hi, this post is outdated. Follow the Step 5 of the current tutorial - SPO Grafana Tutorial - SNSKY - Summer Night SKY Pool
Okay now im a step further But right now i do have the problem that i dont get the stats from my bp in the panels.
Like i do see the infos from adapools like pledge etc. but i dont see stuff like peers (core), kes key rotation etc.
Do you have an idea what i did wrong?
check whether your grafana node is receiving any data from from the BP
http://localhost:9090/targets
if you are not receiving any data, check your firewall settings on the BP
Ive opened the port 9100 and 12798. Am i missing something? Oo
please send screenshot of http://localhost:9090/targets
will this guide work as is for ubuntu 22 as well?
Yes…it will
Ever since upgrading my nodes to v8.0.0, the Connected Peers metric (cardano_node_metrics_connectedPeers_int {alias=“block-producer-node”}) no longer reports any data… Anyone else have this issue?
If you run in P2P mode this might provide enough eye-candy:
curl -s -H 'Accept: application/json' http:/localhost:12788 | jq '.cardano.node.metrics.connectionManager'
{
"duplexConns": {
"type": "g",
"val": 17
},
"incomingConns": {
"type": "g",
"val": 15
},
"outgoingConns": {
"type": "g",
"val": 50
},
"prunableConns": {
"type": "g",
"val": 1
},
"unidirectionalConns": {
"type": "g",
"val": 47
}
}
Hi,
Yes it is renamed to cardano_node_metrics_peers_connectedPeers_int