From 4101eaeeae6e6e1fba4010584ecadf99a0e3da5f Mon Sep 17 00:00:00 2001 From: Quentin Bisson Date: Thu, 6 Jun 2024 22:47:30 +0200 Subject: [PATCH] Update docs/monitoring/sharding.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Théo Brigitte --- docs/monitoring/sharding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/monitoring/sharding.md b/docs/monitoring/sharding.md index 65be7273..45a3dce0 100644 --- a/docs/monitoring/sharding.md +++ b/docs/monitoring/sharding.md @@ -2,7 +2,7 @@ To be able to ingest metrics without disrupting the workload running in the clusters, the observability operator chooses the number of running __prometheus agent shards__ on each workload cluster. The number of shards is based on the __total number of time series__ ingested for a given cluster. -__By default__, the operator configures a shard for every 1M time series present in Mimir for the workload cluster. To avoid scaling down too abruptly, we defined a scale down threshold of 20%. +__By default__, the operator configures 1 shard for every 1M time series present in Mimir for the workload cluster. To avoid scaling down too abruptly, we defined a scale down threshold of 20%. As this default value was not enough to avoid workload disruptions, we added 2 ways to be able to override the scale up series count target and the scale down percentage.