🔥 CPU Burn Test
Simulate heavy computational load that maxes out CPU for ~15 seconds.
What you'll see:
• CPU spike to 100% in JVM dashboard
• Response time increase in App Monitor
• Performance degradation alerts
Metrics Generated: jvm_cpu_utilization, request_duration
💾 Memory Allocation
Allocate 2M+ array elements to simulate memory pressure and trigger GC.
What you'll see:
• Heap usage spike in JVM dashboard
• Garbage collection activity
• Memory pressure warnings
Metrics Generated: jvm_memory_used, jvm_gc_duration
🐌 Slow Request
Execute a request that takes 5 seconds to complete.
What you'll see:
• p95/p99 latency spike
• Slow trace in Distributed Tracing
• SLO impact calculation
Metrics Generated: http_request_duration (5000ms+)
🧵 Thread Stress
Spawn 200 sleeping threads + 1 CPU-intensive thread.
What you'll see:
• Thread count spike (200+ threads)
• Thread pool saturation
• Combined CPU + thread pressure
Metrics Generated: jvm_thread_count, thread_state
❌ Generate Error
Throw an exception and watch error tracking in action.
What you'll see:
• 500 error in App Monitor
• Error log with stack trace
• Error budget consumption
• Failed trace in Tempo
Metrics Generated: http_response_status_code=500
📝 Log Generation
Generate INFO, WARN, and ERROR logs to demonstrate log aggregation.
What you'll see:
• Logs appear in Loki within seconds
• Correlated with traces and metrics
• Filterable by severity level
• Searchable across all pods
Metrics Generated: log entries (INFO, WARN, ERROR)
⚡ Traffic Burst
Generate 100 concurrent requests to simulate traffic spike.
What you'll see:
• Request rate spike
• Throughput increase
• Load distribution across pods
Metrics Generated: http_requests_total (100+)