#glances — Public Fediverse posts

𝗚𝗹𝗮𝗻𝗰𝗲𝘀:

#Monitoring #Python #Glances

https://thewhale.cchttps://thewhale.cc/posts/glances

Glances is a cross-platform system monitoring tool written in Python.

𝗚𝗹𝗮𝗻𝗰𝗲𝘀:

#Monitoring #Python #Glances

https://thewhale.cchttps://thewhale.cc/posts/glances

Glances is a cross-platform system monitoring tool written in Python.

𝗚𝗹𝗮𝗻𝗰𝗲𝘀:

#Monitoring #Python #Glances

https://thewhale.cchttps://thewhale.cc/posts/glances

Glances is a cross-platform system monitoring tool written in Python.

#glances auf meinem #Homeserver

#glances auf meinem #Homeserver

#glances auf meinem #Homeserver

#glances auf meinem #Homeserver

#glances auf meinem #Homeserver

Grafana-Ablösung – Monitoring in Home Assistant

https://www.myhome.zone/grafana-abloesung-monitoring-in-home-assistant/

Grafana-Ablösung – Monitoring in Home Assistant

https://www.myhome.zone/grafana-abloesung-monitoring-in-home-assistant/

Grafana-Ablösung – Monitoring in Home Assistant

https://www.myhome.zone/grafana-abloesung-monitoring-in-home-assistant/

Grafana-Ablösung – Monitoring in Home Assistant

https://www.myhome.zone/grafana-abloesung-monitoring-in-home-assistant/

Grafana-Ablösung – Monitoring in Home Assistant

https://www.myhome.zone/grafana-abloesung-monitoring-in-home-assistant/

CVE Alert: CVE-2026-32596 - nicolargo - glances - https://www.redpacketsecurity.com/cve-alert-cve-2026-32596-nicolargo-glances/

#OSINT #ThreatIntel #CyberSecurity #cve-2026-32596 #nicolargo #glances

CVE Alert: CVE-2026-32596 - nicolargo - glances - https://www.redpacketsecurity.com/cve-alert-cve-2026-32596-nicolargo-glances/

#OSINT #ThreatIntel #CyberSecurity #cve-2026-32596 #nicolargo #glances

CVE Alert: CVE-2026-32596 - nicolargo - glances - https://www.redpacketsecurity.com/cve-alert-cve-2026-32596-nicolargo-glances/

#OSINT #ThreatIntel #CyberSecurity #cve-2026-32596 #nicolargo #glances

CVE Alert: CVE-2026-32596 - nicolargo - glances - https://www.redpacketsecurity.com/cve-alert-cve-2026-32596-nicolargo-glances/

#OSINT #ThreatIntel #CyberSecurity #cve-2026-32596 #nicolargo #glances

CVE Alert: CVE-2026-32596 - nicolargo - glances - https://www.redpacketsecurity.com/cve-alert-cve-2026-32596-nicolargo-glances/

#OSINT #ThreatIntel #CyberSecurity #cve-2026-32596 #nicolargo #glances

🐧 #Glances — моніторинг ресурсів у #Linux

Термінальна утиліта, яка показує в реальному часі статистику по CPU, пам’яті, дисках, мережі та процесах

Відстежує:
• навантаження на CPU та температуру
• використання пам’яті та середнє навантаження
• процеси та їх кількість
• мережеві інтерфейси та дискові операції
• стан RAID, IRQ та сенсорів
• вільне місце на диску й розподіл по папках
• контейнери та їх ресурси
• аптайм, алерти та інші корисні показники

🔗 https://github.com/nicolargo/glances

🐧 #Glances — моніторинг ресурсів у #Linux

Термінальна утиліта, яка показує в реальному часі статистику по CPU, пам’яті, дисках, мережі та процесах

Відстежує:
• навантаження на CPU та температуру
• використання пам’яті та середнє навантаження
• процеси та їх кількість
• мережеві інтерфейси та дискові операції
• стан RAID, IRQ та сенсорів
• вільне місце на диску й розподіл по папках
• контейнери та їх ресурси
• аптайм, алерти та інші корисні показники

🔗 https://github.com/nicolargo/glances

🐧 #Glances — моніторинг ресурсів у #Linux

Термінальна утиліта, яка показує в реальному часі статистику по CPU, пам’яті, дисках, мережі та процесах

Відстежує:
• навантаження на CPU та температуру
• використання пам’яті та середнє навантаження
• процеси та їх кількість
• мережеві інтерфейси та дискові операції
• стан RAID, IRQ та сенсорів
• вільне місце на диску й розподіл по папках
• контейнери та їх ресурси
• аптайм, алерти та інші корисні показники

🔗 https://github.com/nicolargo/glances

🐧 #Glances — моніторинг ресурсів у #Linux

Термінальна утиліта, яка показує в реальному часі статистику по CPU, пам’яті, дисках, мережі та процесах

Відстежує:
• навантаження на CPU та температуру
• використання пам’яті та середнє навантаження
• процеси та їх кількість
• мережеві інтерфейси та дискові операції
• стан RAID, IRQ та сенсорів
• вільне місце на диску й розподіл по папках
• контейнери та їх ресурси
• аптайм, алерти та інші корисні показники

🔗 https://github.com/nicolargo/glances

🐧 #Glances — моніторинг ресурсів у #Linux

Термінальна утиліта, яка показує в реальному часі статистику по CPU, пам’яті, дисках, мережі та процесах

Відстежує:
• навантаження на CPU та температуру
• використання пам’яті та середнє навантаження
• процеси та їх кількість
• мережеві інтерфейси та дискові операції
• стан RAID, IRQ та сенсорів
• вільне місце на диску й розподіл по папках
• контейнери та їх ресурси
• аптайм, алерти та інші корисні показники

🔗 https://github.com/nicolargo/glances

Cá nhân đang gặp sự cố tích hợp Glances từ Raspberry Pi vào trang web (hiện hiển thị dữ liệu giống NAS). Kiểm tra lại cấu hình services.yaml, đặc biệt URL widget (có thể thiếu "://" hoặc lỗi địa chỉ IP). Đảg bảo Glances chạy đúng trên Pi và truy cập được qua trình duyệt. #NAS #RaspberryPi #Glances #CấuHìnhMạng #HomeAssistant #SelfHosted #Troubleshooting #YAML #Linux #IoT

https://www.reddit.com/r/selfhosted/comments/1phjtkx/i_need_some_help_with_integrating_glances_with/

Cá nhân đang gặp sự cố tích hợp Glances từ Raspberry Pi vào trang web (hiện hiển thị dữ liệu giống NAS). Kiểm tra lại cấu hình services.yaml, đặc biệt URL widget (có thể thiếu "://" hoặc lỗi địa chỉ IP). Đảg bảo Glances chạy đúng trên Pi và truy cập được qua trình duyệt. #NAS #RaspberryPi #Glances #CấuHìnhMạng #HomeAssistant #SelfHosted #Troubleshooting #YAML #Linux #IoT

https://www.reddit.com/r/selfhosted/comments/1phjtkx/i_need_some_help_with_integrating_glances_with/

Cá nhân đang gặp sự cố tích hợp Glances từ Raspberry Pi vào trang web (hiện hiển thị dữ liệu giống NAS). Kiểm tra lại cấu hình services.yaml, đặc biệt URL widget (có thể thiếu "://" hoặc lỗi địa chỉ IP). Đảg bảo Glances chạy đúng trên Pi và truy cập được qua trình duyệt. #NAS #RaspberryPi #Glances #CấuHìnhMạng #HomeAssistant #SelfHosted #Troubleshooting #YAML #Linux #IoT

https://www.reddit.com/r/selfhosted/comments/1phjtkx/i_need_some_help_with_integrating_glances_with/

Cá nhân đang gặp sự cố tích hợp Glances từ Raspberry Pi vào trang web (hiện hiển thị dữ liệu giống NAS). Kiểm tra lại cấu hình services.yaml, đặc biệt URL widget (có thể thiếu "://" hoặc lỗi địa chỉ IP). Đảg bảo Glances chạy đúng trên Pi và truy cập được qua trình duyệt. #NAS #RaspberryPi #Glances #CấuHìnhMạng #HomeAssistant #SelfHosted #Troubleshooting #YAML #Linux #IoT

https://www.reddit.com/r/selfhosted/comments/1phjtkx/i_need_some_help_with_integrating_glances_with/

Proof-of-concept:
I ran Glances inside Apple’s new native container runtime on macOS 26 — I call it Gamur (Icelandic for “container”).
Even cooler: Gamur Glances monitors Docker Glances.
Apple nailed this.

#macOS26 #AppleSilicon #containers #homelab #virtualization #DevOps #Glances

Ho pubblicato un nuovo post per chi ama il self-hosting: monitoraggio in tempo reale con Glances Web UI su Debian, installazione pulita con pipx, avvio automatico con systemd e consigli per la sicurezza. Se ti piace smanettare, potrebbe interessarti: https://emanuelegori.uno/monitoraggio-in-tempo-reale-di-cpu-ram-e-filesystem-con-glances-web-ui-e-avvio-automatico-su-debian-systemd/

#linux #unolinux #foss #opensource #homelab @linux #smanettoni #glances

Ho pubblicato un nuovo post per chi ama il self-hosting: monitoraggio in tempo reale con Glances Web UI su Debian, installazione pulita con pipx, avvio automatico con systemd e consigli per la sicurezza. Se ti piace smanettare, potrebbe interessarti: https://emanuelegori.uno/monitoraggio-in-tempo-reale-di-cpu-ram-e-filesystem-con-glances-web-ui-e-avvio-automatico-su-debian-systemd/

#linux #unolinux #foss #opensource #homelab @linux #smanettoni #glances

Ho pubblicato un nuovo post per chi ama il self-hosting: monitoraggio in tempo reale con Glances Web UI su Debian, installazione pulita con pipx, avvio automatico con systemd e consigli per la sicurezza. Se ti piace smanettare, potrebbe interessarti: https://emanuelegori.uno/monitoraggio-in-tempo-reale-di-cpu-ram-e-filesystem-con-glances-web-ui-e-avvio-automatico-su-debian-systemd/

#linux #unolinux #foss #opensource #homelab @linux #smanettoni #glances

Ho pubblicato un nuovo post per chi ama il self-hosting: monitoraggio in tempo reale con Glances Web UI su Debian, installazione pulita con pipx, avvio automatico con systemd e consigli per la sicurezza. Se ti piace smanettare, potrebbe interessarti: https://emanuelegori.uno/monitoraggio-in-tempo-reale-di-cpu-ram-e-filesystem-con-glances-web-ui-e-avvio-automatico-su-debian-systemd/

#linux #unolinux #foss #opensource #homelab @linux #smanettoni #glances

Yup, #glances is it. If you're curious:

```bash
pipx install glances[all]
glances -w
```

Then just load up http://yourserverip:61208/

Yup, #glances is it. If you're curious:

```bash
pipx install glances[all]
glances -w
```

Then just load up http://yourserverip:61208/

Yup, #glances is it. If you're curious:

```bash
pipx install glances[all]
glances -w
```

Then just load up http://yourserverip:61208/

Yup, #glances is it. If you're curious:

```bash
pipx install glances[all]
glances -w
```

Then just load up http://yourserverip:61208/

Yup, #glances is it. If you're curious:

```bash
pipx install glances[all]
glances -w
```

Then just load up http://yourserverip:61208/

Run Glances at RBPI startup

If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

In my previous post, I struggled to run glances on my Raspberry Pi Zero W. After a first reboot I stared to my Home Assistant dashboard and wondered where is the data from my RaspberryPi. Of course, I ran it manually from the shell, it didn’t restart by itself.

If you ask me to tell you out of my head how to make a service/script start after a reboot, I will stare you blank.

After a bit of googling, I found out there are at least 4 different ways to do it.

Firstly, I tried to make glances to start using crontab method:

sudo crontab -e#then I added the following command to crontab:@reboot sh /<path to my glances>/glances -w

It failed, don’t know why, maybe because Raspbian doesn’t like @restart command.

Second try – rc.local:

I tinkered a bit with rc.local but I gave up quickly.

Third try – systemd – it worked!

1. Go to systemd directory

cd /etc/systemd/system

2. create a definition file for the service

sudo nano glances_w.service

3. Add the following text to glances_w.service file:

[Install]WantedBy=multi-user.target[Unit]Description=Glances Web ServerWants=network-online.targetAfter=network-online.target[Service]User=tomiGroup=admExecStart=/home/tomi/glances/bin/glances -wExecStartPre=/bin/sleep 10Type=simple[Timer]OnStartupSec=25

Change parameter User (tomi) to your user and ExecStart (/home/tomi/glances/bin/glances -w) with path to your glances start command.

4. Enable and start service

sudo systemctl enable glances_w.servicesudo systemctl start glances_w.service

5. Check the status of the service

systemctl status glances_w.service

It should give you something like:

Thanks to this forum post – now my glances start autmatically after a reboot. Of course it didn’t go smoothly as described above. I had to tinker with the User and Group parameter. I didn’t know which user should I insert. Then I didn’t know the name of the group.

So I had to find it out using:

groupsgroups tomi

The bottom line is: without forums and manuals for linux commands, I’d be completely disabled when using linux. I’m using it on and off for 30 years, but still struggling with basic commands. I wonder if I will ever climb above my current level: google-the-command-copy-paste-modify-repeat

Tags: #homeasistant #glances #raspberrypi #systemd

https://blog.rozman.info/run-glances-at-raspberry-pi-startup/

#glances #homeasistant #raspberrypi #systemd #then

Run Glances at RBPI startup

If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

In my previous post, I struggled to run glances on my Raspberry Pi Zero W. After a first reboot I stared to my Home Assistant dashboard and wondered where is the data from my RaspberryPi. Of course, I ran it manually from the shell, it didn’t restart by itself.

If you ask me to tell you out of my head how to make a service/script start after a reboot, I will stare you blank.

After a bit of googling, I found out there are at least 4 different ways to do it.

Firstly, I tried to make glances to start using crontab method:

sudo crontab -e#then I added the following command to crontab:@reboot sh /<path to my glances>/glances -w

It failed, don’t know why, maybe because Raspbian doesn’t like @restart command.

Second try – rc.local:

I tinkered a bit with rc.local but I gave up quickly.

Third try – systemd – it worked!

1. Go to systemd directory

cd /etc/systemd/system

2. create a definition file for the service

sudo nano glances_w.service

3. Add the following text to glances_w.service file:

[Install]WantedBy=multi-user.target[Unit]Description=Glances Web ServerWants=network-online.targetAfter=network-online.target[Service]User=tomiGroup=admExecStart=/home/tomi/glances/bin/glances -wExecStartPre=/bin/sleep 10Type=simple[Timer]OnStartupSec=25

Change parameter User (tomi) to your user and ExecStart (/home/tomi/glances/bin/glances -w) with path to your glances start command.

4. Enable and start service

sudo systemctl enable glances_w.servicesudo systemctl start glances_w.service

5. Check the status of the service

systemctl status glances_w.service

It should give you something like:

Thanks to this forum post – now my glances start autmatically after a reboot. Of course it didn’t go smoothly as described above. I had to tinker with the User and Group parameter. I didn’t know which user should I insert. Then I didn’t know the name of the group.

So I had to find it out using:

groupsgroups tomi

The bottom line is: without forums and manuals for linux commands, I’d be completely disabled when using linux. I’m using it on and off for 30 years, but still struggling with basic commands. I wonder if I will ever climb above my current level: google-the-command-copy-paste-modify-repeat

Tags: #homeasistant #glances #raspberrypi #systemd

https://blog.rozman.info/run-glances-at-raspberry-pi-startup/

#glances #homeasistant #raspberrypi #systemd #then

Run Glances at RBPI startup

If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

In my previous post, I struggled to run glances on my Raspberry Pi Zero W. After a first reboot I stared to my Home Assistant dashboard and wondered where is the data from my RaspberryPi. Of course, I ran it manually from the shell, it didn’t restart by itself.

If you ask me to tell you out of my head how to make a service/script start after a reboot, I will stare you blank.

After a bit of googling, I found out there are at least 4 different ways to do it.

Firstly, I tried to make glances to start using crontab method:

sudo crontab -e#then I added the following command to crontab:@reboot sh /<path to my glances>/glances -w

It failed, don’t know why, maybe because Raspbian doesn’t like @restart command.

Second try – rc.local:

I tinkered a bit with rc.local but I gave up quickly.

Third try – systemd – it worked!

1. Go to systemd directory

cd /etc/systemd/system

2. create a definition file for the service

sudo nano glances_w.service

3. Add the following text to glances_w.service file:

[Install]WantedBy=multi-user.target[Unit]Description=Glances Web ServerWants=network-online.targetAfter=network-online.target[Service]User=tomiGroup=admExecStart=/home/tomi/glances/bin/glances -wExecStartPre=/bin/sleep 10Type=simple[Timer]OnStartupSec=25

Change parameter User (tomi) to your user and ExecStart (/home/tomi/glances/bin/glances -w) with path to your glances start command.

4. Enable and start service

sudo systemctl enable glances_w.servicesudo systemctl start glances_w.service

5. Check the status of the service

systemctl status glances_w.service

It should give you something like:

Thanks to this forum post – now my glances start autmatically after a reboot. Of course it didn’t go smoothly as described above. I had to tinker with the User and Group parameter. I didn’t know which user should I insert. Then I didn’t know the name of the group.

So I had to find it out using:

groupsgroups tomi

The bottom line is: without forums and manuals for linux commands, I’d be completely disabled when using linux. I’m using it on and off for 30 years, but still struggling with basic commands. I wonder if I will ever climb above my current level: google-the-command-copy-paste-modify-repeat

Tags: #homeasistant #glances #raspberrypi #systemd

https://blog.rozman.info/run-glances-at-raspberry-pi-startup/

#glances #homeasistant #raspberrypi #systemd #then

Run Glances at RBPI startup

If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

In my previous post, I struggled to run glances on my Raspberry Pi Zero W. After a first reboot I stared to my Home Assistant dashboard and wondered where is the data from my RaspberryPi. Of course, I ran it manually from the shell, it didn’t restart by itself.

If you ask me to tell you out of my head how to make a service/script start after a reboot, I will stare you blank.

After a bit of googling, I found out there are at least 4 different ways to do it.

Firstly, I tried to make glances to start using crontab method:

sudo crontab -e#then I added the following command to crontab:@reboot sh /<path to my glances>/glances -w

It failed, don’t know why, maybe because Raspbian doesn’t like @restart command.

Second try – rc.local:

I tinkered a bit with rc.local but I gave up quickly.

Third try – systemd – it worked!

1. Go to systemd directory

cd /etc/systemd/system

2. create a definition file for the service

sudo nano glances_w.service

3. Add the following text to glances_w.service file:

[Install]WantedBy=multi-user.target[Unit]Description=Glances Web ServerWants=network-online.targetAfter=network-online.target[Service]User=tomiGroup=admExecStart=/home/tomi/glances/bin/glances -wExecStartPre=/bin/sleep 10Type=simple[Timer]OnStartupSec=25

Change parameter User (tomi) to your user and ExecStart (/home/tomi/glances/bin/glances -w) with path to your glances start command.

4. Enable and start service

sudo systemctl enable glances_w.servicesudo systemctl start glances_w.service

5. Check the status of the service

systemctl status glances_w.service

It should give you something like:

Thanks to this forum post – now my glances start autmatically after a reboot. Of course it didn’t go smoothly as described above. I had to tinker with the User and Group parameter. I didn’t know which user should I insert. Then I didn’t know the name of the group.

So I had to find it out using:

groupsgroups tomi

The bottom line is: without forums and manuals for linux commands, I’d be completely disabled when using linux. I’m using it on and off for 30 years, but still struggling with basic commands. I wonder if I will ever climb above my current level: google-the-command-copy-paste-modify-repeat

Tags: #homeasistant #glances #raspberrypi #systemd

https://blog.rozman.info/run-glances-at-raspberry-pi-startup/

#glances #homeasistant #raspberrypi #systemd #then

Run Glances at RBPI startup

If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

In my previous post, I struggled to run glances on my Raspberry Pi Zero W. After a first reboot I stared to my Home Assistant dashboard and wondered where is the data from my RaspberryPi. Of course, I ran it manually from the shell, it didn’t restart by itself.

If you ask me to tell you out of my head how to make a service/script start after a reboot, I will stare you blank.

After a bit of googling, I found out there are at least 4 different ways to do it.

Firstly, I tried to make glances to start using crontab method:

sudo crontab -e#then I added the following command to crontab:@reboot sh /<path to my glances>/glances -w

It failed, don’t know why, maybe because Raspbian doesn’t like @restart command.

Second try – rc.local:

I tinkered a bit with rc.local but I gave up quickly.

Third try – systemd – it worked!

1. Go to systemd directory

cd /etc/systemd/system

2. create a definition file for the service

sudo nano glances_w.service

3. Add the following text to glances_w.service file:

[Install]WantedBy=multi-user.target[Unit]Description=Glances Web ServerWants=network-online.targetAfter=network-online.target[Service]User=tomiGroup=admExecStart=/home/tomi/glances/bin/glances -wExecStartPre=/bin/sleep 10Type=simple[Timer]OnStartupSec=25

Change parameter User (tomi) to your user and ExecStart (/home/tomi/glances/bin/glances -w) with path to your glances start command.

4. Enable and start service

sudo systemctl enable glances_w.servicesudo systemctl start glances_w.service

5. Check the status of the service

systemctl status glances_w.service

It should give you something like:

Thanks to this forum post – now my glances start autmatically after a reboot. Of course it didn’t go smoothly as described above. I had to tinker with the User and Group parameter. I didn’t know which user should I insert. Then I didn’t know the name of the group.

So I had to find it out using:

groupsgroups tomi

The bottom line is: without forums and manuals for linux commands, I’d be completely disabled when using linux. I’m using it on and off for 30 years, but still struggling with basic commands. I wonder if I will ever climb above my current level: google-the-command-copy-paste-modify-repeat

Tags: #homeasistant #glances #raspberrypi #systemd

https://blog.rozman.info/run-glances-at-raspberry-pi-startup/

#glances #homeasistant #raspberrypi #systemd #then

Few years ago (2019?) it was like:

pip install glances

And voila, I could monitor CPU, disk etc. of my Raspberry remotely via web browser (if my memory servers but it’s probably not).

After I started tinkering AGAIN with my Raspberry PIs after 4 years, I found out things got … complicated. Or I’m just old.

Instead of ONE step, I had to research quite a bit how to enable Glances again. Now it’s like:

1. Create virtual environment in Python just for Glances (venv something something)
   • sorry, no command here, my RBPI crashed in between and I don’t know how to find the history of commands.
   • probably not needed
   • The official Python docs are great: you have to 1. install venv and then 2. activate it. The commands below include <path to venv> because I didn’t know that I don’t need to use the path if I activate this venv.
2. Install Glances
   • <path to venv>/bin/pip3 install glances
3. Run Glances in web server mode just ot find out a bunch of stuff is missing (fastapi)
   • <path to venv>/bin/glances -w
4. Spend 1 day figuring out why ‘pip install’ is not installing just to find out I have to use pip3 (thanks forums)
   • when I used ‘pip install’, it started installing, but threw a whole bunch of weird errors. I thought something was wrong with my internet connection.
5. Install Fastapi (web framework)
   • <path to venv>/bin/pip3 install fastapi
6. Run Glances again to find out more of stuff is missing (uvicorn)
7. Install Uvicorn (web server)
   • <path to venv>/bin/pip3 install uvicorn
8. Run Glances again to find out more of stuff is missing (jinja2)
9. Install Jinja2 (templating language)
   • <path to venv>/bin/pip3 install jinja2

But hey, not everything is bleak. I finally learnt what venv is and used it for the first time. It’s just an island with an isolated python environment. Yes, I know, I’m slow.

Glances run at <your host>: 61208 and when I access it via web browser, it looks like this:

The whole reason why I wanted to install Glances is to monitor RBPI from Home Assistant. There is a nice Glances integration that works out of the box:

Glances consume ~40% of poor RBPI Zero W CPU, which is quite a lot.

I wonder if there is a tool to monitor CPU that is not CPU intensive…

Tags: #homeasistant #glances #raspberrypi

https://blog.rozman.info/monitoring-rbpi-with-glances-home-assistant-in-2024/

#glances #homeasistant #homeassistant #raspberrypi

Monitoring RBPi with Glances & Home Assistant in 2024

If you’re reading this on fediverse and the layout is off, here’s the link to the original blog post with a nice text & pictures layout.

Few years ago (2019?) it was like:

pip install glances

And voila, I could monitor CPU, disk etc. of my Raspberry remotely via web browser (if my memory serves but it probably doesn’t).

After I started tinkering AGAIN with my Raspberry PIs after 4 years, I found out things got … complicated. Or I’m just old.

Instead of ONE step, I had to research quite a bit how to enable Glances again. Now it’s like:

1. Create virtual environment in Python just for Glances (venv something something)
   • sorry, no command here, my RBPI crashed in between and I don’t know how to find the history of commands.
   • probably not needed
   • The official Python docs are great: you have to 1. install venv and then 2. activate it. The commands below include <path to venv> because I didn’t know that I don’t need to use the path if I activate this venv.
2. Install Glances
   • <path to venv>/bin/pip3 install glances
3. Run Glances in web server mode just ot find out a bunch of stuff is missing (fastapi)
   • <path to venv>/bin/glances -w
4. Spend 1 day figuring out why ‘pip install’ is not installing just to find out I have to use pip3 (thanks forums)
   • when I used ‘pip install’, it started installing, but threw a whole bunch of weird errors. I thought something was wrong with my internet connection.
5. Install Fastapi (web framework)
   • <path to venv>/bin/pip3 install fastapi
6. Run Glances again to find out more of stuff is missing (uvicorn)
7. Install Uvicorn (web server)
   • <path to venv>/bin/pip3 install uvicorn
8. Run Glances again to find out more of stuff is missing (jinja2)
9. Install Jinja2 (templating language)
   • <path to venv>/bin/pip3 install jinja2

But hey, not everything is bleak. I finally learnt what venv is and used it for the first time. It’s just an island with an isolated python environment. Yes, I know, I’m slow.

Glances run at <your host>: 61208 and when I access it via web browser, it looks like this:

The whole reason why I wanted to install Glances is to monitor RBPI from Home Assistant. There is a nice Glances integration that works out of the box:

Glances consume ~40% of poor RBPI Zero W CPU, which is quite a lot.

I wonder if there is a tool to monitor CPU that is not CPU intensive…

Update: if I don’t access it via web browser (only via Home Assistant), the CPU usage is 12%. Much better.

Tags: #homeasistant #glances #raspberrypi

https://blog.rozman.info/monitoring-rbpi-with-glances-home-assistant-in-2024/

#glances #homeasistant #homeassistant #raspberrypi

Few years ago (2019?) it was like:

pip install glances

And voila, I could monitor CPU, disk etc. of my Raspberry remotely via web browser (if my memory servers but it’s probably not).

After I started tinkering AGAIN with my Raspberry PIs after 4 years, I found out things got … complicated. Or I’m just old.

Instead of ONE step, I had to research quite a bit how to enable Glances again. Now it’s like:

1. Create virtual environment in Python just for Glances (venv something something)
   • sorry, no command here, my RBPI crashed in between and I don’t know how to find the history of commands.
   • probably not needed
   • The official Python docs are great: you have to 1. install venv and then 2. activate it. The commands below include <path to venv> because I didn’t know that I don’t need to use the path if I activate this venv.
2. Install Glances
   • <path to venv>/bin/pip3 install glances
3. Run Glances in web server mode just ot find out a bunch of stuff is missing (fastapi)
   • <path to venv>/bin/glances -w
4. Spend 1 day figuring out why ‘pip install’ is not installing just to find out I have to use pip3 (thanks forums)
   • when I used ‘pip install’, it started installing, but threw a whole bunch of weird errors. I thought something was wrong with my internet connection.
5. Install Fastapi (web framework)
   • <path to venv>/bin/pip3 install fastapi
6. Run Glances again to find out more of stuff is missing (uvicorn)
7. Install Uvicorn (web server)
   • <path to venv>/bin/pip3 install uvicorn
8. Run Glances again to find out more of stuff is missing (jinja2)
9. Install Jinja2 (templating language)
   • <path to venv>/bin/pip3 install jinja2

But hey, not everything is bleak. I finally learnt what venv is and used it for the first time. It’s just an island with an isolated python environment. Yes, I know, I’m slow.

Glances run at <your host>: 61208 and when I access it via web browser, it looks like this:

The whole reason why I wanted to install Glances is to monitor RBPI from Home Assistant. There is a nice Glances integration that works out of the box:

Glances consume ~40% of poor RBPI Zero W CPU, which is quite a lot.

I wonder if there is a tool to monitor CPU that is not CPU intensive…

Tags: #homeasistant #glances #raspberrypi

https://blog.rozman.info/monitoring-rbpi-with-glances-home-assistant-in-2024/

#glances #homeasistant #homeassistant #raspberrypi

Few years ago (2019?) it was like:

pip install glances

And voila, I could monitor CPU, disk etc. of my Raspberry remotely via web browser (if my memory servers but it’s probably not).

After I started tinkering AGAIN with my Raspberry PIs after 4 years, I found out things got … complicated. Or I’m just old.

Instead of ONE step, I had to research quite a bit how to enable Glances again. Now it’s like:

1. Create virtual environment in Python just for Glances (venv something something)
   • sorry, no command here, my RBPI crashed in between and I don’t know how to find the history of commands.
   • probably not needed
   • The official Python docs are great: you have to 1. install venv and then 2. activate it. The commands below include <path to venv> because I didn’t know that I don’t need to use the path if I activate this venv.
2. Install Glances
   • <path to venv>/bin/pip3 install glances
3. Run Glances in web server mode just ot find out a bunch of stuff is missing (fastapi)
   • <path to venv>/bin/glances -w
4. Spend 1 day figuring out why ‘pip install’ is not installing just to find out I have to use pip3 (thanks forums)
   • when I used ‘pip install’, it started installing, but threw a whole bunch of weird errors. I thought something was wrong with my internet connection.
5. Install Fastapi (web framework)
   • <path to venv>/bin/pip3 install fastapi
6. Run Glances again to find out more of stuff is missing (uvicorn)
7. Install Uvicorn (web server)
   • <path to venv>/bin/pip3 install uvicorn
8. Run Glances again to find out more of stuff is missing (jinja2)
9. Install Jinja2 (templating language)
   • <path to venv>/bin/pip3 install jinja2

But hey, not everything is bleak. I finally learnt what venv is and used it for the first time. It’s just an island with an isolated python environment. Yes, I know, I’m slow.

Glances run at <your host>: 61208 and when I access it via web browser, it looks like this:

The whole reason why I wanted to install Glances is to monitor RBPI from Home Assistant. There is a nice Glances integration that works out of the box:

Glances consume ~40% of poor RBPI Zero W CPU, which is quite a lot.

I wonder if there is a tool to monitor CPU that is not CPU intensive…

Tags: #homeasistant #glances #raspberrypi

https://blog.rozman.info/monitoring-rbpi-with-glances-home-assistant-in-2024/

#glances #homeasistant #homeassistant #raspberrypi

Few years ago (2019?) it was like:

pip install glances

And voila, I could monitor CPU, disk etc. of my Raspberry remotely via web browser (if my memory servers but it’s probably not).

After I started tinkering AGAIN with my Raspberry PIs after 4 years, I found out things got … complicated. Or I’m just old.

Instead of ONE step, I had to research quite a bit how to enable Glances again. Now it’s like:

1. Create virtual environment in Python just for Glances (venv something something)
   • sorry, no command here, my RBPI crashed in between and I don’t know how to find the history of commands.
   • probably not needed
   • The official Python docs are great: you have to 1. install venv and then 2. activate it. The commands below include <path to venv> because I didn’t know that I don’t need to use the path if I activate this venv.
2. Install Glances
   • <path to venv>/bin/pip3 install glances
3. Run Glances in web server mode just ot find out a bunch of stuff is missing (fastapi)
   • <path to venv>/bin/glances -w
4. Spend 1 day figuring out why ‘pip install’ is not installing just to find out I have to use pip3 (thanks forums)
   • when I used ‘pip install’, it started installing, but threw a whole bunch of weird errors. I thought something was wrong with my internet connection.
5. Install Fastapi (web framework)
   • <path to venv>/bin/pip3 install fastapi
6. Run Glances again to find out more of stuff is missing (uvicorn)
7. Install Uvicorn (web server)
   • <path to venv>/bin/pip3 install uvicorn
8. Run Glances again to find out more of stuff is missing (jinja2)
9. Install Jinja2 (templating language)
   • <path to venv>/bin/pip3 install jinja2

But hey, not everything is bleak. I finally learnt what venv is and used it for the first time. It’s just an island with an isolated python environment. Yes, I know, I’m slow.

Glances run at <your host>: 61208 and when I access it via web browser, it looks like this:

The whole reason why I wanted to install Glances is to monitor RBPI from Home Assistant. There is a nice Glances integration that works out of the box:

Glances consume ~40% of poor RBPI Zero W CPU, which is quite a lot.

I wonder if there is a tool to monitor CPU that is not CPU intensive…

Tags: #homeasistant #glances #raspberrypi

https://blog.rozman.info/monitoring-rbpi-with-glances-home-assistant-in-2024/

#glances #homeasistant #homeassistant #raspberrypi

Did you know #glances can show you info about running #docker containers? Neat! #Linux #system #admin https://glances.readthedocs.io/en/latest/aoa/containers.html

Did you know #glances can show you info about running #docker containers? Neat! #Linux #system #admin https://glances.readthedocs.io/en/latest/aoa/containers.html

Did you know #glances can show you info about running #docker containers? Neat! #Linux #system #admin https://glances.readthedocs.io/en/latest/aoa/containers.html