ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #prometheus
Write-Ahead Log Recovery Behavior The Prometheus time series database (TSDB) uses a Write-Ahead Log (WAL) to ensure data durability for samples that have not yet been compacted into permanent blocks. In scenarios involving abrupt power loss or unclean shutdowns (such as a SIGKILL), the trailing segment of the WAL can become malformed. Current server behavior
Evaluating Rancher memory leak detection options Goal: Choose between Rancher’s native /metrics endpoint and an external Prometheus stack from the monitoring catalog to identify upward memory trends in the server or agent components. Constraint: The Rancher HA setup recommends a metrics scrape interval of no more than 15 seconds to limit overhead, yet the ag
Query Timeout Behavior in Prometheus Prometheus utilizes a global --query.timeout flag to prevent resource exhaustion from long-running queries. While the HTTP API allows for per-request timeout overrides, the server must manage the lifecycle of the underlying PromQL engine process when these limits are reached or when a client abruptly closes the connection
rancher