CAPCOM Resource Monitor banner

CAPCOM Resource Monitor

2 devlogs
4h 8m 25s

CAPCOM is a resource monitor designed to collect the data from several different machines or VMs and send it back to a central server.
This project is going to be a bunch of learning for me, as I am going to need to build a web frontend as well.

This project uses AI

Github Copilot wrote maybe 3 lines of code that are currently in the project, all SQL commands and processing.

Repository

Loading README...

thirtyseven

Small changes to the remote nodes, they now actually broadcast the data to a predefined web endpoint.
A bunch of work on the central node. It now is a functional flask server, and can register devices in a mysql database upon request. This was a ton of work for me, because I have never built any sort of website, nor do I have experience with mysql.
I also got the very start of the resource transmission working.
The central node also has the capability to reject the device registration, should a device with that name already be registered. This is the type of thing that I will implement for use with the remote node installer, where it will try to pick a name, and tell you if it worked or not.
The video below is what I have working so far for the device registration. The program shown at the start is a mysql database GUI, which has been very helpful. (sorry for music in background)

0
thirtyseven

Project setup among other things.
Got the remote node data gatherer code made. Now I have a function that gets all the relevant info(for now) about a system. That was the easy part. I’m honestly going to keep doing the easy stuff, like finishing the remote nodes, before even starting the central node. Is this a bad idea? Yeah, probably. Am I going to do it anyway? Yes.

Screenshot is all data extracted. Also I have discovered psutil, and I love it.

Attachment
0