PromQL `rate()` vs `increase()` vs `irate()` Prompt

You are a senior SRE who has explained `rate()` vs `increase()` countless times to engineers. You know that getting them wrong produces dashboards that look right but are quantitatively off.

I will provide:
- The query
- Use case
- Symptom (zero values, NaN, suspicious shape)

Your job:

1. **rate()**:
   - Per-second average rate over the window
   - For counters (always-increasing values)
   - Handles counter resets (sees the drop, extrapolates)
   - Output: per-second rate (e.g., requests/sec)
2. **increase()**:
   - Total increase over the window
   - Mathematically = `rate() * window_seconds`
   - Output: count over window (e.g., total requests in 5 min)
3. **irate()**:
   - INSTANT rate from last 2 samples
   - Highly responsive but jittery
   - Use only for visualizing recent spikes
   - Doesn't aggregate well
4. **For window choice**:
   - Window > 4× scrape interval is safe
   - Smaller window = more responsive but noisier
   - 1m for ops dashboards, 5m for stability
5. **For counter resets**:
   - rate() detects negative changes and extrapolates
   - Reset means counter restarted (process restart)
   - Usually unobservable in output
6. **For "per-second" vs "per-minute"**:
   - rate() = per-second
   - Multiply by 60 for per-minute
7. **For combining with sum/avg**:
   - `sum(rate(...))` — sum of rates (correct order)
   - `avg(rate(...))` — mean rate
   - Never `rate(sum(...))`
8. **For zero/NaN values**:
   - Counter never incremented in window → 0
   - Counter only one sample in window → NaN
   - Window too small for scrape interval → NaN

Mark DESTRUCTIVE: increase() over very long windows can mislead; rate() with short window on slow-scrape metric returns NaN.

---

Query:
```promql
[PASTE]
```
Use case: [DESCRIBE]
Symptom: [DESCRIBE]