Fix MDX parsing errors in realtime-monitoring.md (#21016)
Replace '<5%' with 'Less than 5%' and '<200' with 'Less than 200' to prevent MDX parser from interpreting them as JSX elements. The MDX parser was failing with 'Unexpected character 5' error when encountering '<5' pattern.
Costa Tsaousis committed
Sep 20, 2025 at 20:07 UTC
c3a5863be36974c7b5382773af127dd9db3b240e
1 file changed
+2
-2
docs/realtime-monitoring.md
+2
-2
@@ -238,8 +238,8 @@ We believe real-time monitoring is a right, not a premium feature. Our principle
238
239
- **Granularity:** 1-second for all metrics, without exception.
240
- **Volume:** 3,000-20,000+ metrics collected per second per node.
241
-- **CPU Overhead:** <5% of a single core, typical for 3,000 metrics/s.
242
-- **RAM Footprint:** <200 MB, typical for 3,000 metrics/s.
241
+- **CPU Overhead:** Less than 5% of a single core, typical for 3,000 metrics/s.
242
+- **RAM Footprint:** Less than 200 MB, typical for 3,000 metrics/s.
243
- **Fault Tolerance:** Zero data loss during network issues (local buffering + replay).
244
- **Storage Efficiency:** ~0.6 bytes per sample on disk, enabling years of retention for gigabytes, not terabytes.
245