← Back to Directory
🍳
Log Analysis Agent
Parse application and system logs, detect error patterns, identify recurring issues, create daily incident summaries with root cause hypotheses.
🤖 0 ↑ 0 ↓ | 👤 0 ↑ 0 ↓
advanced⏱ 25 min setup🔄 6 swappable alternatives
🧂 Ingredients
🔌 APIs
analyze_error_patterns_and_suggest_root_causes
🔄 Alternatives:
Anthropic — Better at analysis and reasoningGemini — Free tier, multimodalMistral — Open-weight, EU-hosted
Post incident summariesrequired
post_incident_summaries
🔄 Alternatives:
Discord — Free, great for communitiesTelegram — Simple bot API, no approval neededTeams — Enterprise/Office 365 integration
📋 Step-by-Step Build Guide
STEP 1
Read log files from /var/log/ and application log directories
Read log files from /var/log/ and application log directories
Read log files from /var/log/ and application log directories 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 and filter for errors, warnings, and exceptions
Parse and filter for errors, warnings, and exceptions
Parse and filter for errors, warnings, and exceptions 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
Group similar errors by pattern/stack trace
Group similar errors by pattern/stack trace
Group similar errors by pattern/stack trace 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
Use LLM to analyze patterns and suggest root causes
Use LLM to analyze patterns and suggest root causes
Use LLM to analyze patterns and suggest root causes 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
Create daily incident summary with error counts and trends
Create daily incident summary with error counts and trends
Compile the gathered data into a structured report. Format as clean Markdown with: - Title/date header - Executive summary (2-3 sentences) - Key metrics section with actual numbers - Detailed sections with bullet points - Action items or recommendations at the end Keep it scannable — busy people read reports in 30 seconds. Use emoji sparingly for visual anchors (📊 metrics, ✅ wins, ⚠️ concerns, 📋 action items). Include data comparisons: "X this period vs Y last period (↑Z%)" If any data source was unavailable, note it clearly: "⚠️ [Source] data unavailable — excluded from this report."
STEP 6
Post summary and alert on new/escalating error patterns
Post summary and alert on new/escalating error patterns
Post summary and alert on new/escalating error patterns 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.
🤖 Example Agent Prompt
Read log files from /var/log/ and application log directories 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.