Prompt design for system status digest generation

For generating a system status digest, you would typically want a prompt that can fetch data about key metrics or statuses of various systems, summarize it concisely, and maybe even flag issues. Here’s a sample prompt to get you started with generating a system status digest:

Prompt Design for System Status Digest Generation:

• Objective: Generate a system status digest that summarizes the operational health of multiple systems or components. This should be brief but detailed enough to highlight any major concerns or critical issues.

• Input Requirements:

  1. Systems to monitor: List of systems, services, or components to include in the digest (e.g., servers, databases, applications, network status, etc.).

  2. Status details: The key metrics for each system or service, such as uptime, load, memory usage, error rates, response times, etc.

  3. Thresholds for alerts: Define thresholds for performance issues (e.g., CPU usage > 85%, database latency > 200ms, etc.).

  4. Timeframe: Specify the time range for the status (e.g., daily, weekly, real-time).

  5. Data source: Whether the data is coming from monitoring tools, system logs, or custom API endpoints.

  6. Priority level: Whether the status should prioritize critical errors, warnings, or general health monitoring.

• Response Format: Summarized system status for each monitored system or component, including:

  1. Health check: Overall system health (e.g., “Healthy”, “Degraded”, “Critical”).

  2. Key metrics: Relevant statistics for each system (e.g., uptime percentage, CPU load, memory usage, etc.).

  3. Alerts/Issues: Any problems or issues detected (e.g., “Disk space running low on Server A”, “Database response time exceeding threshold”).

  4. Suggested actions: If applicable, suggest next steps or fixes (e.g., “Reboot Server B to resolve high load”).

• Example Prompt:

  diff
  CopyEdit
  Generate a system status digest for the following systems:
  
  - Web Server (Uptime, Response Time, CPU Usage, Memory Usage)
  - Database Server (Connection Count, Latency, Query Time, Error Rate)
  - Network (Packet Loss, Latency, Bandwidth Usage)
  - Application (Error Rate, Request Count, Latency)
  
  Timeframe: Last 24 hours
  Thresholds: 
  - CPU usage > 85% (Critical)
  - Memory usage > 90% (Warning)
  - Latency > 200ms (Warning)
  - Error rate > 5% (Critical)
  
  Include any alerts or issues and suggest next steps for any degraded performance or critical issues.
  

This is a general framework, and depending on your specific use case, you can adjust the systems, metrics, and thresholds accordingly.