cozystack

0 Fork 0

mirror of https://github.com/cozystack/cozystack.git synced 2026-11-09 14:02:56 +09:00

Files

T

History

Myasnikov Daniil 361311c5c9 docs(monitoring-agents): note what object count the 2Gi limit covers

The sizing comment named the measured peak without saying how much
room 2Gi leaves above it, which left open why the chart pins 2Gi when
the default LimitRange limit proposed in #3494 is 4Gi.

2Gi is 6.7x the measured 307Mi peak working set. Read as linear in
object count, that is roughly 2100 pods and 170k series against the
322 pods and ~25.6k series the peak was measured on, so the limit
stays a ceiling rather than a bound on a cluster several times larger
than the one behind the numbers.

Comment only. The requests, the limit and the deliberate absence of a
CPU limit are all unchanged.

Assisted-by: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>

2026-10-07 04:56:09 +03:00

alerts

fix(monitoring): pin the scrape size rendering and sharpen the alert

2026-09-23 20:56:07 +03:00

charts

[system:monitoring-agents] separate metrics-server

2025-12-01 20:51:26 +03:00

templates

feat(monitoring): route tenant logs to the tenant's own VictoriaLogs

2026-09-29 17:10:54 +02:00

tests

fix(monitoring-agents): give kube-state-metrics a sized memory limit