← All projects

Part 4 of this project

Data Layer

Collect metrics with psutil helpers

Goal for this part

Collect metrics with psutil helpers.

Treat 04-Data-Layer as the source of truth for this checkpoint. If your local tree drifted, re-clone that folder rather than mixing files from neighbors.

What you should already know

You do not need prior CustomTkinter experience for part 1. Later parts assume you finished the earlier snapshots on the same machine.

  • You can open a terminal and run python3
  • You are comfortable editing a .py file and saving it
  • You have a desktop session (not a headless SSH box without display forwarding)

Why CustomTkinter fits Pulsebay

CustomTkinter modernizes Tkinter widgets. Pair it with psutil to teach live metrics without a heavyweight GUI stack.

Tabs for CPU, memory, and processes keep the UI readable. Poll on a timer—never block the main thread on long scans.

Checkpoint

After you run the snapshot, you should recognize the behavior described in the goal—before you move on. If the window (or server) never appears, stop and fix the run steps.

Code shape

Snapshots stay small on purpose. Look for this kind of core call as you read the folder:

psutil.cpu_percent(interval=0.2)

How to run it

Clone the teaching repo, open 04-Data-Layer, install what the README asks for, then run python app.py.

git clone https://github.com/michaeldunga1/fcc-ctk-monitor.git
cd fcc-ctk-monitor/04-Data-Layer
python3 -m venv .venv
source .venv/bin/activate
pip install -r ../requirements.txt
python app.py

Common mistakes

  • Ignoring platform-specific install notes in the snapshot README
  • Creating tables twice with conflicting schemas
  • Forgetting to commit/close the database connection in long sessions
  • Looking for seed data in part 3 before the data layer exists

Related tutorials