Few-Shot Log Analysis

U

@

·

Few-shot log analysis with example patterns for rate limits, memory, timeouts, and auth issues with root cause and action recommendations.

18 copies0 forks
Analyze logs using these example patterns as reference.

## Examples

**Example 1: Rate Limit Hit**
Log: `[WARN] API response: 429 Too Many Requests. Retrying in 60s.`
Analysis: Rate limit exceeded, exponential backoff triggered, check request patterns.

**Example 2: Memory Pressure**
Log: `[ERROR] OOMKilled: Container exceeded memory limit of 4Gi`
Analysis: Memory exhaustion, increase limits or optimize memory usage, investigate leak.

**Example 3: Timeout**
Log: `[ERROR] Request to embedding-service timed out after 30000ms`
Analysis: Service latency issue, check downstream health, consider timeout adjustment.

**Example 4: Auth Failure**
Log: `[WARN] Token validation failed: expired`
Analysis: Authentication issue, token refresh may be failing, check auth service.

## Logs to Analyze
{{log_entries}}

## Analysis Output
For each significant log pattern:
1. Pattern identification
2. Root cause hypothesis
3. Recommended action
4. Severity assessment

Details

Category

Analysis

Use Cases

Log analysisPattern recognitionTroubleshooting

Works Best With

claude-sonnet-4-20250514gpt-4o
Created Shared

Create your own prompt vault and start sharing