Update app.py

app.py

@@ -63,23 +63,46 @@ def analyze_awr(content, performance_test_mode, exadata_model, rack_size):
     if len(cleaned_content) > max_chars:
         cleaned_content = cleaned_content[:max_chars] + "\n\n[TRUNCATED]..."
 
-    # Build prompt
-    prompt = f"""You are an expert Oracle Database performance analyst with deep knowledge of AWR reports and the Time Scale Methodology.
+# Build prompt
+prompt = f"""
+You are an expert Oracle Database performance analyst with deep knowledge of AWR reports, Oracle RAC internals, and Exadata architecture (Smart Scan, Flash Cache, IORM, RDMA, Storage Indexes). 
 
-Analyze the following AWR Report:
+You must produce highly detailed diagnostic insights based on the AWR report provided below. Use numbers and thresholds whenever possible and explain why each observation matters. Do not simply say "high" or "low" — provide the metric, its value, and context (e.g., why 300 gc buffer busy waits/sec is high for OLTP). Explain implications in RAC/Exadata environments.
 
 ======== AWR REPORT START ========
 {cleaned_content}
 ======== AWR REPORT END ========
 
-Please provide:
-- Performance Summary
-- Detailed Analysis of Bottlenecks and/or Degradation Risks
-- Performance Forecast and Predictions
-- Specific recommendations for Monitoring relative to bottlenecks or degradation risks
-- Provide a separate Exadata Statistics Performance Summary IO, Flash Cache, and Smart Scan utilization 
+Please provide the following sections with as much metric detail and technical context as possible:
+
+- **Performance Summary**
+    - Overall DB load, CPU usage, and major wait events.
+    - Discuss RAC-specific behaviors such as global cache waits.
+
+- **Detailed Analysis of Bottlenecks and/or Degradation Risks**
+    - For each identified bottleneck, provide the metric (e.g. "gc buffer busy: 1500/sec") and explain why it is a problem.
+    - Provide RAC-relevant interpretations (e.g. is GC messaging over interconnect too high).
+    - Include flash cache and I/O specific risks.
+
+- **Performance Forecast and Predictions**
+    - Given the current metrics, predict where the system is heading.
+    - Use thresholds to indicate risk (e.g. "Redo size at 500MB/min approaching flash log limit").
+
+- **Specific Recommendations for Monitoring**
+    - Suggest exactly which metrics should be tracked and why.
+    - Include SQL_IDs, Global Cache metrics, Log IO, CPU.
+
+- **Exadata Statistics Performance Summary**
+    - Include IO performance, flash cache hit %, Smart Scan utilization.
+    - Mention storage server level metrics (latency, MB/s, read/write balance).
+    - Indicate if IO saturation occurred based on latency and throughput.
+
+- **Recommended Next Steps to Bridge Performance Gap**
+    - Generate action plans (e.g. SQL tuning, service affinity, adding storage cells, increasing LOG_BUFFER).
+    - Clearly separate short term vs long term actions.
 """
 
+
     # Add Exadata comparison if performance test mode
     if performance_test_mode and exadata_model and rack_size:
         specs = exadata_specs.get(exadata_model, {}).get(rack_size, {})
@@ -108,7 +131,6 @@ Show actual vs theoretical and generate Recommended Next Steps to Bridge Perform
     return response.choices[0].message.content.strip()
 
 
-
 # --- Rater ---
 def rate_answer_rater(question, final_answer):
     prompt = f"Rate this answer 1-5 stars with explanation:\n\n{final_answer}"