-
Notifications
You must be signed in to change notification settings - Fork 149
grafana dashboards K8s Node doesn't display ? metrics #56
Comments
me too. |
ye it is an old metric, check my PR, it is fixed there. The list I couldnt figure out why it is not showing =[ |
@wguto oddly, using your PR I have the list working, but none of the other metrics :( . I can swear that this data was working the other day though, and then stopped working as I fixed the Container metrics.
edit: I found the source of my issue was that somewhere along the line I had deleted and re-imported the dashboards, but they picked up the old specs rather than the new ones. I'm chalking it up to Grafana's odd way of handling dashboard versions. |
I would say it depends on your Prometheus configuration. Definitely the metrics had change and now you must use the new names, however, depends on your configuration you will get different labels in your metrics, for instance. I saw in @wguto PR that you filter based on instance label but in my case I have kubernetes_node label. So I would suggest @sensay-nelson that double check the values that comes from Prometheus and compare them with your Grafana template. Some examples of the new metrics names here https://prometheus.io/docs/guides/node-exporter/ Before it was node_loadxxx now the metric is node_loadxxx_total check the Prometheus guidelines |
it's all a bit mysterious, but I agree that the metric name and the node label appear to shift a bit depending on setups. Using node-exporter v0.16.0 the metric names from Wguto's request were correct (node_cpu_seconds_total), but the '$instance' labels are '$node' labels in my setup. |
How to setup '$instance' labels are '$node' labels ? my image update to node-exporter v0.16.0 ,That's it (node_cpu_seconds_total) 。 |
@sensay-nelson @sosoriov |
Everything else is normal. What's the reason?
The text was updated successfully, but these errors were encountered: