Tobias/Porygon-Monitoring
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Tobias
2026-10-11 00:20:49 +00:00
parent a9ef7605ff
commit fc97e24b21
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -2
View File
@@ -1,8 +1,8 @@
## Overview ## Overview
For my personal self-hosted infrastructure I found the typical Prometheus and Grafana set up to be too bloated, involving too much network traffic and overhead, for what I actually want to monitor For my personal self-hosted infrastructure I found the typical Prometheus and Grafana set up to be too bloated, involving too much overhead for what I actually want to monitor
Consequently I decided to build my own lightweight tooling with Python, Linux commands, SSH, Cron, JSON, HTML/CSS and Javascript Consequently I decided to build my own lightweight tooling with Python, Bash, SSH, Cron, JSON, HTML/CSS and Javascript
It is capable of sending offline/healing alerts via email, as well as scraping relevant metrics, (CPU, RAM, Disk Space etc), to display on a centralized webpage It is capable of sending offline/healing alerts via email, as well as scraping relevant metrics, (CPU, RAM, Disk Space etc), to display on a centralized webpage
@@ -10,6 +10,8 @@ The metrics page, as well as the generated JSON files and Python script is hoste
The remote server set-up, including creating the monitoring user, installing required software, copying the Python script and adding ssh keys, is fully automated via Ansible playbooks The remote server set-up, including creating the monitoring user, installing required software, copying the Python script and adding ssh keys, is fully automated via Ansible playbooks
Adding a new server to be monitored is easily achieved via the porygon-management.sh CLI tool written in Bash
## High Level Architecture Overview ## High Level Architecture Overview
``` ```