cozystack

0 Fork 0

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

Files

T

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

The per-job limit replaces the global flag downward as well, so an
install that raised promscrape.maxScrapeSize past it through extraArgs
has to raise this value too; say so where the value is set. Pin that a
numeric value still renders as a string, which the CRD field requires,
and pin the alert severity. Name the cluster in the alert and say where
the apiserver value lives, since a guest cluster cannot set it.

Assisted-by: LLM
Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>

2026-09-23 20:56:07 +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

fix(monitoring): give the kube-apiserver scrape its own size limit

2026-09-23 20:27:00 +03:00

tests

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