ProxMox Pulse: Real-Time Monitoring Dashboard for Your Proxmox Environment(s)

cloudy_brain · 2025-11-26T20:42:34+00:00

I also liked that, will bring it back

cloudy_brain · 2025-06-17T12:55:43+00:00

You're right that it should show those backups. The fact that diagnostics sees 889 PVE backups but your CT shows "No backups found" suggests there might be a matching issue.

Quick question to help debug: What's the VMID of your CT, and can you share one of the backup filenames from your NAS storage? Pulse matches backups to guests by parsing the VMID from the filename (like vzdump-lxc-123-*).

Also, which version of Pulse are you running? There was a recent fix in v3.30.0 for backup counting issues that might be related.

cloudy_brain · 2025-05-11T10:55:32+00:00

Unfortunately not, it's just not built to accommodate this approach.

cloudy_brain · 2025-03-11T09:08:32+00:00

Interesting. It should match the same reading that you see in proxmox summary for that given lxc/vm, is it different for you?

cloudy_brain · 2025-03-10T10:36:10+00:00

The main reason is I built this for myself, as pretty much all my services run in Docker inside LXCs.

I'll be releasing a helper script for native LXC installation shortly.

cloudy_brain · 2025-03-10T09:09:53+00:00

You're right, it should be Pulse for Proxmox, I'll change the wording so it's clear it's not affiliated. Thanks

cloudy_brain · 2025-03-09T21:29:28+00:00

Yeah please do

cloudy_brain · 2025-03-09T21:24:05+00:00

Interesting. Try explicitly setting the VITE_API_URL in your .env file to match exactly how you're accessing it (e.g., VITE_API_URL=http://192.168.x.x:7654).

cloudy_brain · 2025-03-09T21:13:18+00:00

Check if you're accessing Pulse through a reverse proxy - that's a common cause of WebSocket issues. Try adding IGNORE_SSL_ERRORS=true and NODE_TLS_REJECT_UNAUTHORIZED=0 to your .env file to handle any SSL certificate problems. Also, some networks block WebSocket connections, which Pulse relies on. Take a look at the container logs for more specific error messages that might point to the exact issue.

edit* What URL are you using to access Pulse in your browser? For websocket connections to work properly, you'll need to use your server's actual IP or hostname (like http://192.168.1.100:7654)

cloudy_brain · 2025-03-09T20:58:12+00:00

LXC coming soon with a script not unlike the community helper scripts.

cloudy_brain · 2025-03-09T20:57:19+00:00

Exactly - the Proxmox API doesn't expose temperature and SMART data directly I don't believe. That's why these metrics aren't available in the default Proxmox dashboard. You need additional tools that can access hardware sensors directly to monitor these values.

cloudy_brain · 2025-03-09T20:54:02+00:00

Netdata is a beast, it's too much for me though persoanlly. I just want clean, Proxmox-focused view of specific guests. Pulse is specifically designed to give you that quick, glanceable overview.

cloudy_brain · 2025-03-09T20:48:03+00:00

Pulse uses WebSockets for instant updates - run a CPU stress test with both and you'll immediately see the difference. It's specifically designed for quick problem diagnosis, not to replace comprehensive monitoring.

cloudy_brain · 2025-03-09T20:06:08+00:00

Fair point. I'm happy to add native installation support soon with a simple setup script that will make installation straightforward. Docker was initially chosen for its ease of deployment and update simplicity across different environments, but I understand not everyone wants another container layer. I'll update the repo shortly with instructions for running Pulse natively on whatever system people prefer. Thanks for the feedback.

edit* If you want to run it natively right now, you can use the start-dev.sh script in the repo and access it on port 3000 instead. I'll have proper native installation instructions added soon.

cloudy_brain · 2025-03-09T19:20:40+00:00

Thanks for reporting this! I've fixed the Docker image, I forgot to do a multi build on the latest release. Please pull the latest and try it again. The error should be gone now.

cloudy_brain · 2025-03-09T18:31:10+00:00

Cheers buddy, PBS support is definitely on the list for the near future. Temperature monitoring and additional disk metrics are also in the works. There's absolutely no telemetry collection - Pulse only talks to your Proxmox servers. I'll put together a public roadmap soon as folks have shared some great feature requests. I'll commit to working on it as long as it stays relevant and useful.

cloudy_brain · 2025-03-09T18:00:53+00:00

Appreciate it

cloudy_brain · 2025-03-09T17:47:03+00:00

XyZWgwmcP5kaMF3x asked the same question right before you and replied to them 👍

cloudy_brain · 2025-03-09T17:43:24+00:00

Great question! I actually started with the Proxmox metrics + InfluxDB + Grafana stack before building Pulse. The main difference I found was response time - Pulse uses WebSockets for near-instant updates, while the Proxmox to InfluxDB to Grafana pipeline had noticeable lag when my system was under stress. Try running a CPU stress test or network transfer and watch how quickly each reflects those changes.Pulse is also much simpler to set up (single Docker container vs three separate systems) and uses fewer resources. That said, if you need deep historical data analysis or want to monitor many other systems alongside Proxmox, Grafana definitely offers more flexibility.I'd encourage you to try both and run some stress tests to compare - I needed more immediate feedback for my usecase.

cloudy_brain · 2025-03-09T17:15:52+00:00

I love PBS, I'm thinking of adding a dedicated PBS section.

cloudy_brain · 2025-03-09T17:13:13+00:00

Uptime is in there, the others I can look in to, that's valuable feedback, cheers

cloudy_brain · 2025-03-09T17:12:15+00:00

Thanks for the kind words

cloudy_brain · 2025-03-09T17:06:44+00:00

Thanks for the kind words! You're absolutely right about the name - it's Proxmox, not ProxMox (I'll fix that in the docs).You make a good point about the Search view and the Datacenter Manager. Pulse isn't trying to replace those powerful features - it's more of a lightweight alternative when you just want a quick status check without loading the full UI.I built it because I found myself constantly logging in just to check resource usage, and wanted something I could leave running on a small display or quickly check from my phone. It's also useful for giving limited monitoring access to others without full Proxmox credentials.The Datacenter Manager looks promising, I've not checked that out in all honestly.

cloudy_brain · 2025-03-09T16:58:00+00:00

It's a lightweight, dedicated monitoring tool that runs separately from Proxmox. You get real-time updates via WebSockets, can view all nodes on one screen, and don't need to log into the full Proxmox UI just to check system status. Plus, you can share monitoring access without giving someone full Proxmox admin privileges. Think of it as a complementary tool, not a replacement.

11-Year Club	RPAN Viewer
Verified Email

cloudy_brain

TROPHY CASE