Announcement

This page is also available in Português, Deutsch, Español, Italiano, Français, and 日本語.

New: Max Memory & OOM Event Visibility in PodFit

Understand why memory recommendations are set where they are — now with a toggleable Max Memory metric line and OOM kill event markers directly on the ZoomIn chart.

By Oleg Merkulov

·

Shipped by

Oleksii KoshkinKarim ShakirovPavel Kostychev

What's New

PodFit's ZoomIn memory chart now exposes two pieces of data that were previously invisible:

  • Max Memory toggle — A dashed line showing peak memory usage (including OS page caches and buffers), the exact metric that drives memory limit recommendations
  • OOM Kill markers — Visual markers on the memory timeline showing when and how often a container was OOM-killed

Why It Matters

Memory limit recommendations are based on max memory (which includes reclaimable page cache), but the chart previously showed only working set (active memory only). In edge cases, max memory can be 10–100× higher than working set — making recommendations look unreasonably high with no explanation.

This feature closes that gap: you can now see exactly why a recommendation was set where it was.

How to Use It

  1. Open ZoomIn for any container in PodFit
  2. Click Max Memory in the chart legend to overlay the peak memory line
  3. OOM kill events appear automatically as red markers on the timeline when they exist
  4. Hover over any data point to see Max Memory values and OOM counts in the tooltip

Details

  • Max Memory line is hidden by default — opt in per session
  • OOM markers are on by default when OOM events exist in the selected time range
  • Tooltips use plain language — no Prometheus metric names