Issue #8

[walletkun]

Finished setting up the basic LLM analysis of the monitoring. Let me know if theres any part that is confusing.Or let me know if theres anything that needs to be changed. But for now this script will analyze the basic monitoring commands like top, df, etc.

[sidsun1]

LGTM (mostly - still would like a couple of changes), very elegant code design! I have run it locally and had a couple of thoughts/fixes I wanted to mention:

Upon first run once my env file was configured with my API key, I found a deprecation warning which I've since fixed.

Despite the mostly elegant code design, I find that it could be useful to follow PEP8 conventions using a formatting/linting tool like Ruff that uses flake8. I'll go ahead and assign this to you since it's a quick fix and you've written most of the code already! This should be our standard as we continue to develop the project, and I will make notes of this for everyone to follow.
The following commands:
ruff check and ruff format are helpful.

I did see that there are some instances of summaries that could be unwanted. There are instances where the model itself returns detailed responses and actions to take despite the system being virtually idle. I did see that you've set the model temperature to 0.1 but there is a noticeable inconsistency in responses (at least when using my key).

Example output here:

Analysis:
SUMMARY: The system is significantly underutilized with very low CPU, memory, 
and disk usage.

ISSUES:
*   System resources are largely idle, indicating potential over-provisioning
and inefficient resource allocation.

ACTIONS:
*   **Review Resource Allocation:** Evaluate if the current system
specifications (CPU cores, RAM, disk size) are appropriate for the actual
workload.
*   **Cost Optimization:** Consider scaling down the instance size (e.g., fewer
vCPUs, less RAM) or consolidating services onto fewer machines to reduce
operational costs.
*   **Workload Analysis:** Investigate if the current workload is lower than
expected or if the system is provisioned for future growth.

System is healthy, no fixes needed

vs. the more common:

Analysis:
SUMMARY: The system is currently idle with very low resource utilization.

System is healthy, no fixes needed

Try to find a way to fix this.