Skip to content

Commit 42d5dc5

Browse files
author
Rémy Noel
committed
docs(ins): adds troubleshouting for scaleway-vmagent metrics (int-add-vmagent)
1 parent 21e8f0d commit 42d5dc5

File tree

2 files changed

+20
-0
lines changed

2 files changed

+20
-0
lines changed
Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
---
2+
title: Missing memory and GPU metrics on the cockpit dashboard
3+
tags: cockpit instance
4+
dates:
5+
validation:
6+
posted:
7+
---
8+
9+
When no metrics can be seen on the cocpit's `Instance Overview` or
10+
`Instance GPUs` dashboards, you should check the vmagent (folded-by default)
11+
row. It will tell you on which vm the scaleway-vmagent is answering requests.
12+
13+
If the vmagent is not installed on your machine, you can install it by adding
14+
the [scaleway ppa (on ubuntu)](https://launchpad.net/~scaleway/+archive/ubuntu/stable) or
15+
[copr (if RHEL based)](https://copr.fedorainfracloud.org/coprs/g/scaleway/stable/)
16+
and install the `scaleway-vmagent` package (respectively with apt or dnf).
17+
18+
If installed, you may check that the service is running with
19+
`systemctl status scaleway-vmagent`.

pages/instances/troubleshooting/index.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,4 +74,5 @@ productIcon: InstanceProductIcon
7474
- [Fix unreachable IPv6 RHEL-based Instances after transitioning to routed IP](/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance)
7575
- [Fix unreachable Ubuntu Noble Instances following a reboot](/instances/troubleshooting/fix-unreachable-noble-after-reboot)
7676
- [Troubleshooting issues with faulty kernel installations](/instances/troubleshooting/reboot-from-faulty-kernel)
77+
- [Missing memory and GPU metrics on the cockpit dashboard](/instances/troubleshooting/filling-memory-and-gpu-metrics-on-the-cockpit-dashboard)
7778
</LinksList>

0 commit comments

Comments
 (0)