Hi, On 11/9/20 10:56 AM, yagyans...@gmail.com wrote: > Hi. I am using Promtheus v 2.20.1 and suddenly my Prometheus crashed > because of Memory overshoot. How to pinpoint what caused the Prometheus > to go OOM or which query caused the Prometheus go OOM?
Prometheus writes the currently active queries to a file which is read upon restart. Prometheus will print all unfinished queries, see here: https://www.robustperception.io/what-queries-were-running-when-prometheus-died This should help pin-pointing the relevant queries. Often it's some combination of querying long timestamps and/or high cardinality metrics. Kind regards, Christian -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/caf68358-7dbd-c851-8c36-479d6e30cb6a%40hoffmann-christian.info.
