← Back to Directory
🍳

Server Health Dashboard

Continuous monitoring of CPU, memory, disk, and processes. Alert on anomalies, maintain health history, catch problems before they become outages.

🤖 00 ↓  |  👤 00
advanced20 min setup🔄 5 swappable alternatives

🧂 Ingredients

🔌 APIs

send_anomaly_alerts

🔄 Alternatives:

Discord Free, great for communitiesTelegram Simple bot API, no approval neededTeams Enterprise/Office 365 integration

post_health_dashboard

🔄 Alternatives:

Slack Professional team notificationsTelegram Simple, no approval needed

📋 Step-by-Step Build Guide

STEP 1

Run system commands: top, df, free, ps aux

Run system commands: top, df, free, ps aux

Run system commands: top, df, free, ps aux

Steps:
1. Validate all required inputs are available
2. Execute the operation described above
3. Verify the result meets expected output format
4. Handle errors gracefully — retry transient failures, log and alert on persistent ones
5. Return structured output with status and any relevant data

If any required data is missing, request it from the user before proceeding.
STEP 2

Parse CPU usage, memory usage, disk usage per volume

Parse CPU usage, memory usage, disk usage per volume

Parse CPU usage, memory usage, disk usage per volume

Steps:
1. Validate all required inputs are available
2. Execute the operation described above
3. Verify the result meets expected output format
4. Handle errors gracefully — retry transient failures, log and alert on persistent ones
5. Return structured output with status and any relevant data

If any required data is missing, request it from the user before proceeding.
STEP 3

Check for processes consuming >80% CPU or >2GB memory

Check for processes consuming >80% CPU or >2GB memory

Check for processes consuming >80% CPU or >2GB memory

Steps:
1. Validate all required inputs are available
2. Execute the operation described above
3. Verify the result meets expected output format
4. Handle errors gracefully — retry transient failures, log and alert on persistent ones
5. Return structured output with status and any relevant data

If any required data is missing, request it from the user before proceeding.
STEP 4

Compare against baseline — flag anomalies

Compare against baseline — flag anomalies

Compare against baseline — flag anomalies

Steps:
1. Validate all required inputs are available
2. Execute the operation described above
3. Verify the result meets expected output format
4. Handle errors gracefully — retry transient failures, log and alert on persistent ones
5. Return structured output with status and any relevant data

If any required data is missing, request it from the user before proceeding.
STEP 5

If any metric exceeds threshold, send immediate alert

If any metric exceeds threshold, send immediate alert

Send a notification to the user via the configured messaging channel.

For Pushover:
POST https://api.pushover.net/1/messages.json
Body: { token: {APP_TOKEN}, user: {USER_KEY}, message: "{notification_text}", title: "{title}", priority: 0 }

For Twilio SMS:
POST https://api.twilio.com/2010-04-01/Accounts/{SID}/Messages
Body: To={phone}, From={twilio_number}, Body={message_text}

Keep the message concise — under 160 characters for SMS, under 500 for push.
Include the most actionable information first.
Log: timestamp, channel, recipient, message preview, delivery status.
STEP 6

Save snapshot to health-history.json for trend analysis

Save snapshot to health-history.json for trend analysis

Persist the data to the configured storage.

Data structure:
- Include timestamp (ISO 8601) with every record
- Use consistent field names across entries
- Store raw values (not formatted) for future analysis
- Add a source/origin field for audit trail

Storage operation:
1. Validate the data before writing
2. Check for duplicates (by timestamp + unique key)
3. Append to existing records — never overwrite
4. Verify the write succeeded
5. Return the stored record ID/reference

🤖 Example Agent Prompt

Run system commands: top, df, free, ps aux

Steps:
1. Validate all required inputs are available
2. Execute the operation described above
3. Verify the result meets expected output format
4. Handle errors gracefully — retry transient failures, log and alert on persistent ones
5. Return structured output with status and any relevant data

If any required data is missing, request it from the user before proceeding.

Copy this prompt into your agent to get started.