From 947b97c20b0364f77b7e56f75c4c73fd6c6591dd Mon Sep 17 00:00:00 2001 From: Hisar Balik Date: Wed, 11 Sep 2024 11:18:14 +0200 Subject: [PATCH] fix some typos --- docs/contributor/arch/014-telemetry-self-monitor-storage.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributor/arch/014-telemetry-self-monitor-storage.md b/docs/contributor/arch/014-telemetry-self-monitor-storage.md index da49a0ade..f26a0ee49 100644 --- a/docs/contributor/arch/014-telemetry-self-monitor-storage.md +++ b/docs/contributor/arch/014-telemetry-self-monitor-storage.md @@ -9,7 +9,7 @@ Proposed ## Context The Telemetry module self-monitoring is crucial for the overall health of the system. The self-monitoring data is used to detect issues in the Telemetry module and to provide insights into the system's health. The self-monitoring data is stored in a time-series database (TSDB) and is used to generate alerts. -The current storage architecture and retention policy for the self-monitoring data are not well defined, currently, some installation faces the issue self-monitoring storage fill-up and exceed the storage limit despite the retention policies 2 hours or 50 MBytes. +The current storage configuration and retention policy for the self-monitoring data are not well-defined, currently, some installation faces the issue self-monitoring storage fill-up and exceed the storage limit despite the retention policies 2 hours or 50 MBytes. The Telemetry self-monitoring data is stored in the Prometheus TSDB, which is designed for large scale deployments, the amount data collected by the Telemetry self-monitoring is actually small compared to the Prometheus capabilities (currently few MBytes) nevertheless the storage size and retention policies have to be carefully configured.