This message was deleted.
# rke2
a
This message was deleted.
c
sounds like it’s not scraping the etcd metrics properly. If your etcd cluster didn’t have a leader you would know about it very quickly because your cluster would be non-functional.
a
Thats what I figured.
Any advice or reference on how I can work through it?
I was going to start teaching myself alerts, but I dont want to get a million ETCD errors.
c
I’m not sure what metric that field pulls from, you might poke at the dashboard and compare that to the metrics you’re actually scraping.
I don’t muck about with the reporting and monitoring stuff much
p
I have exactly the same "issue" but i figured out it was just a scraping bug
a
@powerful-librarian-10572 Were you using the integrated Grafana? Mine is just that way from the Apps/Helm, Install Rancher Monitoring package. I didnt configure any scraping.
p
Yep, rancher-monitoring, all stock.
What i mean by "i figured out it's a scraping bug" i just ignore it
a
lol
c
I have the same call from my cluster ^^. 3 nodes each Control Plane, Etcd v1.29.2+rke2r1
a
is this just like something, one of us should open an Issue for?
p
Probably @calm-coat-56369 as he's running kubes 1.29 (assuming then it's rancher 2.9), which is more bleeding edge than my 2.8.3 rancher with kubes 1.28