Docker file fix

Dockerfile

@@ -1,27 +1,30 @@
 # Dockerfile for a Python application with user permissions
 FROM python:3.11-slim
 
-# Install system dependencies as root (BEFORE switching users)
+# Install system dependencies as root
 RUN apt-get update && apt-get install -y build-essential
 
-# Create user and switch to it
-RUN useradd -m -u 1000 user
-USER user
-ENV PATH="/home/user/.local/bin:$PATH"
+# Create user and set up directory structure as root
+RUN useradd -m -u 1000 user && \
+    mkdir -p /app && \
+    chown -R user:user /app
 
 # Set working directory
 WORKDIR /app
 
+# Switch to user AFTER setting up permissions
+USER user
+ENV PATH="/home/user/.local/bin:$PATH"
+
 # Copy files with proper ownership
 COPY --chown=user:user . /app
 
 # Install Python dependencies
 COPY --chown=user:user ./requirements.txt requirements.txt
 RUN pip install --no-cache-dir --upgrade pip && \
-    pip install --no-cache-dir --user -r requirements.txt && chmod -R 777 /app
+    pip install --no-cache-dir --user -r requirements.txt
 
-    
 EXPOSE 8000 7860
 
-#CMD ["bash", "run.sh"]
-CMD ["sh", "-c", "python mcp_server.py && python app.py"]
+#CMD ["sh", "-c", "uvicorn mcp_server:app --host 0.0.0.0 --port 8000 && python app.py"]
+CMD bash -c "python /app/mcp_server.py & sleep 60 && python /app/app.py"

app.py

@@ -114,6 +114,8 @@ try:
     agent.name = "Outage Odyssey Agent"
     GradioUI(agent=agent).launch(share=True,mcp_server=True) ##, file_upload_folder="uploaded_data", mcp_server=True,debug=True
 
+except Exception as e:
+    print(f"Error starting Gradio: {str(e)}")
 finally:
     mcp_client.disconnect()
     print("MCP client disconnected")

mcp_server.py

@@ -25,7 +25,6 @@ import PyPDF2
 # Load environment variables
 load_dotenv()
 MISTRAL_API_KEY = os.getenv("MISTRAL_API_KEY")
-OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
 # Setup logging
 log_handler = RotatingFileHandler("mcp_server.log", maxBytes=10 * 1024 * 1024, backupCount=7)
 log_handler.setFormatter(logging.Formatter('%(asctime)s - %(levelname)s - %(message)s'))
@@ -522,7 +521,7 @@ def execute_incident_code(code: str) -> str:
     #     >>> generate_image_with_flux("A cartoon server room with smoke coming out")
     #     "generated_images/comic_image_123456789.png"
     # """
-#
+#     OPENAI_API_KEY = os.getenv("OPENAI_API_KEY")
 #     try:
 #         client = openai.OpenAI()
 #         response = client.images.generate(
@@ -664,11 +663,11 @@ async def health_check(request: Request) -> Response:
     return JSONResponse({"status": "ok"})
 
 
-def start_mcp_server():
+async def start_mcp_server():
     try:
         print("🚀 Starting server...")
         logger.info("Starting Incident Comic Generator server")
-        mcp.run(transport="sse")
+        await mcp.run(transport="sse")
         # mcp.run(transport="stdio")
     except Exception as e:
         logger.error(f"Server failed to start: {str(e)}")

outage_odyssey_ui.py

@@ -718,7 +718,7 @@ Actions taken: Rolled back changes, investigating access controls"""
                         # Add a link to the GitHub repository
                         gr.Markdown("""
                         ### 📖 **Source Code**
-                        Check out the source code on [GitHub](https://github.com)
+                        Check out the source code on [GitHub](https://github.com/Mandark-droid/OutageOdyssey)
                         """, elem_classes="panel")
             
 

sample_incidents.md

@@ -1,187 +1,320 @@
-The Case of the Phantom Pepperoni: A NullPointerException Saga
-Incident Summary: On 2025-06-05T18:30:00Z, the PizzaTrackerService at CheesyBytes Inc. (a food delivery app) began reporting "Phantom Pepperoni" orders due to a NullPointerException in the calculateOvenTime() method. The incident caused 42% of pizzas to bake indefinitely, triggering smoke alarms at 3 pizzerias and confusing delivery drones that circled HQ for hours.
-🔥 Affected Services
-PizzaTrackerService (critical path for order processing)
-OvenScheduler (automated baking system)
-DroneNavigation (relied on bake-time ETA)
-📉 Violated KPIs
-Order Accuracy: Dropped to 58% (target: 99.9%)
-Delivery Time: Increased to ∞ minutes (target: 30 mins)
-Customer Satisfaction: Fell to "Why is my pizza literally on fire?"
-🚨 Critical Alerts
-text
-[18:30:00] CRITICAL: NullPointerException at CheesyBytes.PizzaTrackerService.calculateOvenTime(Pizza.java:127) - Failed to invoke 'getToppingConfig()' on null object reference [18:31:23] ALERT: Oven #7 reported "unusual cheese flare-up" [18:35:45] WARNING: Drone fleet stuck in loop singing "Never Gonna Give You Up"
-🔍 Forensic Data
-Stack Trace:
-text
-java.lang.NullPointerException: Cannot invoke "ToppingConfig.getCookingTime()" because the return value of "Pizza.getToppingConfig()" is null
-Variables at Fault:
-currentPizza.getToppingConfig(): null
-oven.preheat(): Called with null temperature value
-Log Anomalies:
-127 instances of Pizza{name='Phantom Pepperoni', config=null}
-Drone logs showed 694 attempts to calculate route to "NaN,NaN"
-⏰ Event Timeline
-18:29:55: Deployment of "Pepperoni++" v2.1.3 (removed null-check in PizzaFactory)
-18:30:01: First NullPointerException observed
-18:32:00: OvenScheduler began interpreting null bake time as "MAX_INT minutes"
-18:40:00: Security cameras captured engineers offering burnt pizzas to a NPE gremlin drawn on the whiteboard
-🛠️ Resolution
-The team:
-Rolled back to v2.1.2 (which had a if (config != null) check)
-Deployed @NonNull annotations on all getToppingConfig() calls
-Hired a "NullPointerException Prevention Clown" for code review parties
-Post-Incident Confession:
-A developer later admitted: "I thought pepperoni didn’t need configs. It’s just meat confetti!"
-Clues for Root Cause Hunters:
-The deployment removed a null-check that previously handled legacy pizza types
-Forensic data shows Phantom Pepperoni had no corresponding entry in the ToppingConfig database
-The Pizza object constructor allowed toppingConfig to default to null if unspecified
-The answer lies in the cheese... or the lack thereof. 🧀👻
+**The Case of the Phantom Pepperoni: A NullPointerException Saga**  
+**Incident Summary**: On **2025-06-05T18:30:00Z**, the *PizzaTrackerService* at **CheesyBytes Inc.** (a food delivery app) began reporting **"Phantom Pepperoni" orders** due to a `NullPointerException` in the `calculateOvenTime()` method. The incident caused **42% of pizzas** to bake indefinitely, triggering smoke alarms at 3 pizzerias and confusing delivery drones that circled HQ for hours.  
 
---- 
-The Curious Case of the Exploding Cupcake Counter: An Integer Overflow Incident
-Incident Summary: On 2025-06-06T14:22:00Z, the CupcakeCounter microservice at SweetStats Analytics experienced a catastrophic integer overflow. This resulted in the system reporting negative cupcake sales, causing the finance dashboard to display “You owe the universe 2,147,483,648 cupcakes.” The marketing team briefly launched a “Cupcake Debt Forgiveness” campaign before the error was traced.
+---
 
-🧁 Affected Services
-CupcakeCounter (real-time sales tally)
+### 🔥 **Affected Services**  
+- **PizzaTrackerService** (critical path for order processing)  
+- **OvenScheduler** (automated baking system)  
+- **DroneNavigation** (relied on bake-time ETA)  
 
-FinanceDashboard (exec-level reporting)
+---
 
-RewardsEngine (customer loyalty points)
+### 📉 **Violated KPIs**  
+1. **Order Accuracy**: Dropped to 58% (target: 99.9%)  
+2. **Delivery Time**: Increased to **∞ minutes** (target: 30 mins)  
+3. **Customer Satisfaction**: Fell to "Why is my pizza *literally* on fire?"  
 
-📉 Violated KPIs
-Sales Accuracy: -2,147,483,648% (target: 100%)
+---
 
-Reward Points Issued: 0 (target: 1 per cupcake)
+### 🚨 **Critical Alerts**  
+```
+[18:30:00] CRITICAL: NullPointerException at  
+CheesyBytes.PizzaTrackerService.calculateOvenTime(Pizza.java:127)  
+- Failed to invoke 'getToppingConfig()' on null object reference  
+[18:31:23] ALERT: Oven #7 reported "unusual cheese flare-up"  
+[18:35:45] WARNING: Drone fleet stuck in loop singing "Never Gonna Give You Up"  
+```
 
-Dashboard Uptime: 78% (target: 99.9%)
+---
 
-🚨 Critical Alerts
-text
-[14:22:01] CRITICAL: ArithmeticException: integer overflow in CupcakeCounter.updateSales()  
-[14:22:03] ALERT: FinanceDashboard shows negative cupcake revenue  
-[14:23:10] WARNING: RewardsEngine issued 0 points for 2 million cupcake purchases  
-🔍 Forensic Data
-Error Log:
+### 🔍 **Forensic Data**  
+**Stack Trace**:  
+```
+java.lang.NullPointerException: Cannot invoke "ToppingConfig.getCookingTime()"  
+because the return value of "Pizza.getToppingConfig()" is null  
+```
+**Variables at Fault**:  
+- `currentPizza.getToppingConfig()`: **null**  
+- `oven.preheat()`: Called with `null` temperature value  
 
-text
-java.lang.ArithmeticException: integer overflow  
-  at SweetStats.CupcakeCounter.updateSales(CupcakeCounter.java:88)
-  at SweetStats.SalesService.processOrder(SalesService.java:45)
-Variable State:
+**Log Anomalies**:  
+- 127 instances of `Pizza{name='Phantom Pepperoni', config=null}`  
+- Drone logs showed 694 attempts to calculate route to "NaN,NaN"  
 
-int totalCupcakesSold = 2147483647 (max value for signed 32-bit int)
+---
 
-Next sale increments value to -2,147,483,648
+### ⏰ **Event Timeline**  
+1. **18:29:55**: Deployment of "Pepperoni++" v2.1.3 (removed null-check in `PizzaFactory`)  
+2. **18:30:01**: First `NullPointerException` observed  
+3. **18:32:00**: OvenScheduler began interpreting `null` bake time as "MAX_INT minutes"  
+4. **18:40:00**: Security cameras captured engineers offering burnt pizzas to a NPE gremlin drawn on the whiteboard  
 
-Database Snapshot:
+---
 
-sales_total column in CupcakeSales table: -2,147,483,648
+### 🛠️ **Resolution**  
+The team:  
+1. Rolled back to v2.1.2 (which had a `if (config != null)` check)  
+2. Deployed `@NonNull` annotations on all `getToppingConfig()` calls  
+3. Hired a "NullPointerException Prevention Clown" for code review parties  
 
-Loyalty points for user cupcake_queen: 0 (expected: 1,000,000)
+**Post-Incident Confession**:  
+A developer later admitted: "I thought pepperoni didn’t *need* configs. It’s just meat confetti!"  
 
-⏰ Event Timeline
-14:21:55: “Cupcake Mania” flash sale begins
+--- 
 
-14:22:00: Record-breaking 2 million orders in 5 seconds
+**Clues for Root Cause Hunters**:  
+- The deployment removed a null-check that previously handled legacy pizza types  
+- Forensic data shows `Phantom Pepperoni` had no corresponding entry in the `ToppingConfig` database  
+- The `Pizza` object constructor allowed `toppingConfig` to default to `null` if unspecified  
 
-14:22:01: Integer overflow triggers ArithmeticException
+*The answer lies in the cheese... or the lack thereof.* 🧀👻
 
-14:23:30: FinanceDashboard replaced currency symbols with crying emojis
+[1] https://sentry.io/answers/what-is-a-nullpointerexception-and-how-do-i-fix-it/
+[2] http://support.sas.com/kb/47290
+[3] https://www.weblineindia.com/blog/fix-nullpointerexception-in-java-with-examples/
+[4] https://stackoverflow.com/questions/218384/what-is-a-nullpointerexception-and-how-do-i-fix-it
+[5] https://www.youtube.com/watch?v=2b22PiQx8xc
+[6] https://www.digitalocean.com/community/tutorials/java-lang-nullpointerexception
+[7] https://www.harness.io/blog/java-nullpointerexception-solving-it
+[8] https://howtodoinjava.com/java/exception-handling/how-to-effectively-handle-nullpointerexception-in-java/
+[9] https://forum.step.esa.int/t/java-null-pointer-exception/40829
+[10] https://blogs.oracle.com/fusionhcmcoe/post/autocomplete-java-null-pointer-exception
 
-14:25:00: CEO tweets “We are now in negative cupcakes. Please eat responsibly.”
+--- 
+**The Great Bread Uprising: A Foreign Key Fiasco**  
+**Incident Summary**: On **2025-06-06T08:15:00Z**, **DoughyDelights Bakery**’s inventory system triggered a **SQL error 1451** after attempting to delete the "Sourdough Starter" recipe. This caused **12,000 baguettes** to morph into pretzels in delivery apps, stranded 45 delivery drivers at "Bread Narnia" coordinates, and spawned customer complaints like "My ciabatta is judging me."  
 
-🛠️ Resolution
-The team:
+---
 
-Migrated int to long in all cupcake counters
+### 🥖 **Affected Services**  
+- **RecipeRegistry** (core recipe database)  
+- **BreadGenerator** (batch baking scheduler)  
+- **DeliveryPathfinder** (GPS routing tied to recipe IDs)  
 
-Added overflow detection and alerts
+---
 
-Sent apology cupcakes to all affected customers (with apology sprinkles)
+### 📉 **Violated KPIs**  
+1. **Inventory Accuracy**: Dropped to -7% (target: 99.5%)  
+2. **Waste Metrics**: Increased by 420% (target: ≤5%)  
+3. **Driver Sanity**: Replaced with "Why am I delivering *negative bread*?"  
 
-Post-Incident Confession:
-A developer admitted: “Who knew there were that many cupcake lovers? I thought 2 billion was enough for everyone!”
+---
 
-Clues for Root Cause Sleuths:
+### 🚨 **Critical Alerts**  
+```
+[08:15:02] CRITICAL: SQL Error 1451 - "Cannot delete parent row: foreign key constraint fails"  
+[08:16:10] ALERT: Baker #3 reported "rye dough singing *Never Bake Alone*"  
+[08:20:00] WARNING: Delivery maps now route to /dev/null  
+```
+
+---
+
+### 🔍 **Forensic Data**  
+**Error Log**:  
+```
+ERROR 1451: Cannot delete or update a parent row: a foreign key constraint fails  
+(`DoughyDelights`.`orders`, CONSTRAINT `fk_recipe_id` FOREIGN KEY (`recipe_id`)  
+REFERENCES `RecipeRegistry` (`id`))  
+```
+**Offending Query**:  
+```sql  
+DELETE FROM RecipeRegistry WHERE recipe_name = 'Sourdough Starter';  
+```
 
-CupcakeCounter used a signed 32-bit integer for sales totals
+**Database Snapshot**:  
+- **Orphaned Orders**: 14,892 orders referencing `recipe_id=NULL`  
+- **GPS Anomalies**: 67 drivers attempted deliveries to `POINT(∅,∅)`  
 
-No overflow checks or exception handling
+---
 
-Database column type matched Java int
+### ⏰ **Event Timeline**  
+1. **08:14:55**: Overzealous intern executed "Legacy Recipe Purge" script  
+2. **08:15:01**: First foreign key violation detected  
+3. **08:17:30**: BreadGenerator interpreted missing recipes as "pretzel mode"  
+4. **08:25:00**: Surveillance footage showed CFO trying to bribe a baguette  
 
-Flash sale volume exceeded maximum representable value
+---
+
+### 🛠️ **Resolution**  
+The team:  
+1. Restored `Sourdough Starter` from backup (with **ON DELETE RESTRICT** added)  
+2. Deployed regex filter blocking `DELETE` commands containing "starter"  
+3. Hosted a "Foreign Key Appreciation Day" with constraint-themed cupcakes  
+
+**Post-Incident Confession**:  
+The intern later tweeted: "#YOLO DELETE statements are the gluten-free option of SQL."  
 
-The mystery is baked in the numbers. 🧁💥
 --- 
-The Great Bread Uprising: A Foreign Key Fiasco
-Incident Summary: On 2025-06-06T08:15:00Z, DoughyDelights Bakery’s inventory system triggered a SQL error 1451 after attempting to delete the "Sourdough Starter" recipe. This caused 12,000 baguettes to morph into pretzels in delivery apps, stranded 45 delivery drivers at "Bread Narnia" coordinates, and spawned customer complaints like "My ciabatta is judging me."
 
-🥖 Affected Services
-RecipeRegistry (core recipe database)
+**Clues for Root Cause Detectives**:  
+- The `orders` table had a foreign key dependency on `RecipeRegistry.id` [3]  
+- No `ON DELETE CASCADE` clause existed in the schema  
+- Audit logs showed 127 pre-incident warnings about "unreferenced recipe deletions"  
+
+*The proof is in the foreign pudding.* 🍮🔑
+
+[1] https://www.linkedin.com/pulse/10-common-bugs-sql-query-zita-demeter-yumuc
+[2] https://www.ibm.com/docs/en/idr/11.4.0?topic=sm-sql-error-codes-nnnn
+[3] https://ai2sql.io/common-sql-error-codes
+[4] https://learnsql.com/blog/five-common-sql-errors/
+[5] https://docs.intersystems.com/latest/csp/docbook/DocBook.UI.Page.cls?KEY=RERR_sql
+[6] http://blog.solvaria.com/top-common-errors-sql-oracle
+[7] https://www.stratascratch.com/blog/top-most-common-sql-coding-errors-in-data-science/
+[8] https://www.metabase.com/learn/sql/debugging-sql/sql-syntax
+--- 
+**The Curious Case of the Exploding Cupcake Counter: An Integer Overflow Incident**  
+**Incident Summary:** On **2025-06-06T14:22:00Z**, the CupcakeCounter microservice at **SweetStats Analytics** experienced a catastrophic integer overflow. This resulted in the system reporting negative cupcake sales, causing the finance dashboard to display “You owe the universe 2,147,483,648 cupcakes.” The marketing team briefly launched a “Cupcake Debt Forgiveness” campaign before the error was traced.
 
-BreadGenerator (batch baking scheduler)
+---
 
-DeliveryPathfinder (GPS routing tied to recipe IDs)
+### 🧁 **Affected Services**  
+- **CupcakeCounter** (real-time sales tally)  
+- **FinanceDashboard** (exec-level reporting)  
+- **RewardsEngine** (customer loyalty points)  
 
-📉 Violated KPIs
-Inventory Accuracy: Dropped to -7% (target: 99.5%)
+---
 
-Waste Metrics: Increased by 420% (target: ≤5%)
+### 📉 **Violated KPIs**  
+1. **Sales Accuracy:** -2,147,483,648% (target: 100%)  
+2. **Reward Points Issued:** 0 (target: 1 per cupcake)  
+3. **Dashboard Uptime:** 78% (target: 99.9%)  
 
-Driver Sanity: Replaced with "Why am I delivering negative bread?"
+---
 
-🚨 Critical Alerts
-text
-[08:15:02] CRITICAL: SQL Error 1451 - "Cannot delete parent row: foreign key constraint fails"  
-[08:16:10] ALERT: Baker #3 reported "rye dough singing *Never Bake Alone*"  
-[08:20:00] WARNING: Delivery maps now route to /dev/null  
-🔍 Forensic Data
-Error Log:
+### 🚨 **Critical Alerts**  
+```
+[14:22:01] CRITICAL: ArithmeticException: integer overflow in CupcakeCounter.updateSales()  
+[14:22:03] ALERT: FinanceDashboard shows negative cupcake revenue  
+[14:23:10] WARNING: RewardsEngine issued 0 points for 2 million cupcake purchases  
+```
 
-text
-ERROR 1451: Cannot delete or update a parent row: a foreign key constraint fails  
-(DoughyDelights.orders, CONSTRAINT fk_recipe_id FOREIGN KEY (recipe_id)  
-REFERENCES RecipeRegistry (id))  
-Offending Query:
+---
 
-sql
-DELETE FROM RecipeRegistry WHERE recipe_name = 'Sourdough Starter';  
-Database Snapshot:
+### 🔍 **Forensic Data**  
+**Error Log:**  
+```
+java.lang.ArithmeticException: integer overflow  
+  at SweetStats.CupcakeCounter.updateSales(CupcakeCounter.java:88)
+  at SweetStats.SalesService.processOrder(SalesService.java:45)
+```
+**Variable State:**  
+- `int totalCupcakesSold = 2147483647` (max value for signed 32-bit int)  
+- Next sale increments value to -2,147,483,648  
+
+**Database Snapshot:**  
+- `sales_total` column in `CupcakeSales` table: -2,147,483,648  
+- Loyalty points for user `cupcake_queen`: 0 (expected: 1,000,000)  
+
+---
+
+### ⏰ **Event Timeline**  
+1. **14:21:55:** “Cupcake Mania” flash sale begins  
+2. **14:22:00:** Record-breaking 2 million orders in 5 seconds  
+3. **14:22:01:** Integer overflow triggers ArithmeticException  
+4. **14:23:30:** FinanceDashboard replaced currency symbols with crying emojis  
+5. **14:25:00:** CEO tweets “We are now in negative cupcakes. Please eat responsibly.”  
+
+---
+
+### 🛠️ **Resolution**  
+The team:  
+1. Migrated `int` to `long` in all cupcake counters  
+2. Added overflow detection and alerts  
+3. Sent apology cupcakes to all affected customers (with apology sprinkles)  
+
+**Post-Incident Confession:**  
+A developer admitted: “Who knew there were that many cupcake lovers? I thought 2 billion was enough for everyone!”  
+
+---
+
+**Clues for Root Cause Sleuths:**  
+- CupcakeCounter used a signed 32-bit integer for sales totals  
+- No overflow checks or exception handling  
+- Database column type matched Java `int`  
+- Flash sale volume exceeded maximum representable value  
+
+*The mystery is baked in the numbers.* 🧁💥
+
+---
+
+## The Great Database Traffic Jam: SQLTimeoutException Tango
+
+**Incident Summary:**  
+On **2025-06-06T16:45:00Z**, the **OrderProcessor** microservice at **GadgetGuru Inc.** (an e-commerce platform for quirky gadgets) experienced a severe **SQLTimeoutException** during a flash sale on "Self-Stirring Coffee Mugs." The database connection pool ran dry, causing **15,000 pending orders** to queue indefinitely and triggering a wave of confused support tickets titled "Why is my coffee mug still manual?"
+
+---
+
+### 🛒 **Affected Services**  
+- **OrderProcessor** (order placement and payment)  
+- **InventoryTracker** (real-time stock management)  
+- **NotificationService** (order confirmation emails)  
 
-Orphaned Orders: 14,892 orders referencing recipe_id=NULL
+---
 
-GPS Anomalies: 67 drivers attempted deliveries to POINT(∅,∅)
+### 📉 **Violated KPIs**  
+1. **Order Processing Time:** Spiked to 9999 seconds (target: 2 seconds)  
+2. **Successful Order Rate:** Dropped to 8% (target: 99.9%)  
+3. **Customer Satisfaction:** "My coffee is getting cold waiting for my self-stirring mug!"  
 
-⏰ Event Timeline
-08:14:55: Overzealous intern executed "Legacy Recipe Purge" script
+---
 
-08:15:01: First foreign key violation detected
+### 🚨 **Critical Alerts**  
+```
+[16:45:01] CRITICAL: SQLTimeoutException in OrderProcessor.processOrder()
+[16:45:02] ALERT: Connection pool exhausted (maxConnections=50, active=50, waiters=14,987)
+[16:46:30] WARNING: NotificationService backlogged with 9,000 unsent emails
+```
 
-08:17:30: BreadGenerator interpreted missing recipes as "pretzel mode"
+---
 
-08:25:00: Surveillance footage showed CFO trying to bribe a baguette
+### 🔍 **Forensic Data**  
+**Error Log:**  
+```
+com.mysql.jdbc.exceptions.jdbc4.MySQLTimeoutException: Connection timed out after 30 seconds
+  at OrderProcessor.processOrder(OrderProcessor.java:73)
+  at OrderService.submitOrder(OrderService.java:45)
+```
+**Connection Pool Metrics:**  
+- **Max Connections:** 50  
+- **Active Connections:** 50  
+- **Waiting Requests:** 14,987 at peak  
+- **Average Query Duration:** 32 seconds (normal: <0.5s)  
 
-🛠️ Resolution
-The team:
+**Database Snapshot:**  
+- **Locked Rows:** 23,000 (due to long-running transactions)  
+- **CPU Utilization:** 98%  
+- **Deadlock Events:** 0 (not a deadlock, just a traffic jam)  
 
-Restored Sourdough Starter from backup (with ON DELETE RESTRICT added)
+---
 
-Deployed regex filter blocking DELETE commands containing "starter"
+### ⏰ **Event Timeline**  
+1. **16:44:50:** Flash sale on "Self-Stirring Coffee Mugs" begins  
+2. **16:45:00:** Order volume spikes to 20,000 requests per minute  
+3. **16:45:01:** First SQLTimeoutException observed  
+4. **16:46:00:** Connection pool fully exhausted, orders start queuing  
+5. **16:50:00:** Support team overwhelmed with "Where’s my mug?" tickets  
+6. **16:55:00:** Engineers panic and try to "stir" the database with a spoon  
 
-Hosted a "Foreign Key Appreciation Day" with constraint-themed cupcakes
+---
 
-Post-Incident Confession:
-The intern later tweeted: "#YOLO DELETE statements are the gluten-free option of SQL."
+### 🛠️ **Resolution**  
+The team:  
+1. **Increased the database connection pool size** from 50 to 500  
+2. **Optimized long-running queries** and added query timeouts  
+3. **Implemented rate limiting** for flash sales  
+4. **Hosted a "Connection Pool Appreciation Brunch"** with free coffee (manually stirred)  
 
-Clues for Root Cause Detectives:
+**Post-Incident Confession:**  
+A database admin later admitted: "I thought 50 connections was enough for everyone. Turns out, everyone wants self-stirring mugs!"  
 
-The orders table had a foreign key dependency on RecipeRegistry.id 
+---
 
-No ON DELETE CASCADE clause existed in the schema
+## **Clues for Root Cause Investigators**
 
-Audit logs showed 127 pre-incident warnings about "unreferenced recipe deletions"
+- **Connection pool size was static and too small for flash sale traffic**
+- **Long-running queries blocked connections, causing a backlog**
+- **No rate limiting or circuit breakers were in place for peak events**
+- **Monitoring did not alert on pending request queues until after the pool was exhausted**
 
-The proof is in the foreign pudding. 🍮🔑
+*The culprit? A coffee mug that stirred up more trouble than coffee!* ☕🛑