Node metrics not showing
See original GitHub issueHi, I got one trains-agent running and I liked it to my Trains installation. Everything looks good and the Agent is capable of consuming task from default queue as expected.
A minor issue is the fact I don’t get any Usage statistic in the Workers & Queues
tab.

I checked docs but I didn’t find any help.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
No metrics with 5.3.0-latest.2021125.2 · Issue #4435 - GitHub
Notice how there is no longer a "node" label with the hostname, and this is why metrics aren't showing up in Lens. Similar...
Read more >prometheus past metrics not shown on target node restart
I am new to Prometheus and need help to understand why past metric data is not shown when the target node restarts.
Read more >Cluster Metrics | Rancher Manager
Cluster metrics display the hardware utilization for all nodes in your cluster, regardless of its role. They give you a global monitoring ...
Read more >Collect metrics with Metrics Server in Amazon EKS
I can't collect metrics from containers, pods, or nodes with Metrics Server in my Amazon Elastic Kubernetes Service (Amazon EKS) cluster.
Read more >Kubectl Top Pod/Node: Collecting Kubernetes Metrics
Start trying it out by running kubectl top pod. This will show you metrics from all the pods in the default namespace. If...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I moved to agent instances using K8s helm chart and I don’t have the problem there. I suspect there was something related that specific host so, for now I’d say this should not be an application related issue.
Thanks!