intermediateMonitoring: Logs, Metrics, Prometheus & Grafana

Prometheus shows a service's memory metric climbing steadily for days before it gets OOM-killed

Grafana dashboards show a clear upward memory trend with no plateau, ending in a container restart. What does this suggest, and how would you confirm it? Expected reasoning: this pattern is classic for a memory leak (unbounded cache growth, unclosed resources, accumulating objects) rather than a sudden traffic spike, which would show a sharper, traffic-correlated rise. Confirm by correlating the memory metric against request volume (flat/uncorrelated rise points to a leak, not load) and by taking heap dumps or profiling the JVM at different points in the climb to identify what's actually accum

This is a Pro chapter

Sign in, then upgrade to Pro or Power to unlock this and the full DevOps Mastery library.

Prometheus shows a service's memory metric climbing steadily for days before it gets OOM-killed

Next Step

Continue to Why might a Spring Boot app work fine locally (run from the IDE) but fail to connect to Postgres once containerized?← Back to all Docker questions