Skip to content

docs(ins): adds troubleshouting for scaleway-vmagent metrics #5774

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+51 −0
Open

docs(ins): adds troubleshouting for scaleway-vmagent metrics #5774

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 50 additions & 0 deletions ...ces/troubleshooting/filling-memory-and-gpu-metrics-on-the-cockpit-dashboard.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,50 @@
---
title: Missing memory and GPU metrics on the Cockpit dashboard
description: Steps to troubleshoot Instance metrics visibility on Cockpit.
tags: cockpit instance
dates:
validation: 2025-11-13
posted: 2025-11-13
---

## Problem
The memory pane in the `Instance Overview` dashboard or the `Instance GPUs`
dashboard do not display any metrics.

### Symptoms
- No metrics are displayed in the `Instance Overview` Cockpit dashboard.
- No GPU metrics appear in the `Instances GPUs` Cockpit dashboard (for offers with GPUs only)

## Cause
The `scaleway-vmagent` service is either:
- Not installed on the instance, or
- Not running properly.
<Message type="important">
The `scaleway-vmagent` is necessary to collect and report some system metrics (including memory and GPU usage) to the Cockpit Instance dashboards.
</Message>

## Solution
- Verify that the `scaleway-vmagent` service is running and enabled:
```bash
systemctl status scaleway-vmagent
```
- If missing, install the `scaleway-vmagent` package:

For Ubuntu: Check that the [Scaleway PPA](https://launchpad.net/~scaleway/+archive/ubuntu/stable) is added before installing:

```bash
sudo add-apt-repository ppa:scaleway/stable
sudo apt update
sudo apt install scaleway-vmagent
```

For RHEL-based distributions: check that the [Scaleway COPR repository](https://copr.fedorainfracloud.org/coprs/g/scaleway/stable/) is enabled before installing:
```bash
dnf copr enable @scaleway/instance
dnf install scaleway-vmagent
```
<Message type="note">
On RHEL, services are not started after install. You may either start `scaleway-vmagent` manually, or wait for the next boot.
</Message>

Once the service is running, metrics should begin appearing in the Cockpit dashboards within a few minutes.
1 change: 1 addition & 0 deletions pages/instances/troubleshooting/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,4 +74,5 @@ productIcon: InstanceProductIcon
- [Fix unreachable IPv6 RHEL-based Instances after transitioning to routed IP](/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance)
- [Fix unreachable Ubuntu Noble Instances following a reboot](/instances/troubleshooting/fix-unreachable-noble-after-reboot)
- [Troubleshooting issues with faulty kernel installations](/instances/troubleshooting/reboot-from-faulty-kernel)
- [Missing memory and GPU metrics on the Cockpit dashboard](/instances/troubleshooting/filling-memory-and-gpu-metrics-on-the-cockpit-dashboard)
</LinksList>
Loading