Grafana only showing relay node and missing BP

Staking & Delegation Operate a Stake Pool
21

Screenshot from 2021-03-20 22-11-01
Screenshot from 2021-03-20 22-11-011837×890 190 KB

This is what is showing now

22

Check again the yml config on relay (check the BP ip)… and restart the services

BP

sudo systemctl restart prometheus-node-exporter.service

Relay
sudo systemctl restart grafana-server.service
sudo systemctl restart prometheus.service
sudo systemctl restart prometheus-node-exporter.service

How is the service on relay? Running?

sudo systemctl status prometheus.service

1 Like
23

AH!! I had ‘<’ in one of the targets!

1 Like
24

Thanks Alex, silly mistake on my part.

1 Like
25

No problem, also opening the ports helped

1 Like
26

Hi Alex,

Hope you are well. I have a slight issue with prometheus.service. I read through some threads on the forum relating to the same issue but I couldn’t get it fixed. attached are the Prometheus status and .yml file

Cheers

Prom Service
Prom Service1037×412 82.7 KB
yml

27

How many nodes do u have?

28

Just BP and 1 Relay atm

29

it was working fine up until I updated the nodes to 1.26.1

30

Aaa ok. So it worked before and now don’t;
Try to install again prometheus and see if it will starts with the default configuration

Then update again the prometheus.yml file and restart prometheus

31

I did that earlier but, something isn’t syncing properly, I am guessing its something to do with the config file. I will try to do it again later :pray::pray:

32

@Anti.biz has the same issue with one of relay after update… keep us informed

2 Likes
33

During the update… a new config file was downloaded?

34

Hi Alex,

so I reinstalled prometheus and prometheus node exporter onto the Relay and BP but still no luck on the prometheus .service. It is still failing. I might edit the yml config file to match the one that @Anti.biz has.

1 Like
35

image
image1227×912 23.2 KB

Spaces gotta be exact.

1 Like
36

Thanks! I will edit mine now :pray:

37

Make sure your ip didnt change at all, mine disapeared because my private ip changed on my server.

38

YML

39

I restarted prometheus and service still fails. I think the relay node exporter ip should be 0.0.0.0? and changed port to 9100. Still no luck

Screenshot from 2021-04-10 21-27-17

41

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: ‘BP_cnode’
    static_configs:
    • targets: [‘x.x.x.x:12798’]
      labels:
      instance: “Producer”
  • job_name: ‘BP_node_exporter’
    static_configs:
    • targets: [‘x.x.x.x:9100’]
      labels:
      instance: “Producer”
  • job_name: ‘Relay1_cnode’
    static_configs:
    • targets: [‘127.0.0.1:12798’]
      labels:
      instance: “Relay1”
  • job_name: ‘Relay1_node_exporter’
    static_configs:
    • targets: [‘127.0.0.1:9100’]
      labels:
      instance: “Relay1”
  • job_name: ‘Relay2_cnode’
    static_configs:
    • targets: [‘x.x.x.x:12798’]
      labels:
      instance: “Relay2”
  • job_name: ‘Relay2_node_exporter’
    static_configs:
    • targets: [‘x.x.x.x:9100’]
      labels:
      instance: “Relay2”