From ae12fe774e0cf4d12d1dce224af91c5c65081c4d Mon Sep 17 00:00:00 2001
From: Maayan Agranat <107346841+maayanagranat@users.noreply.github.com>
Date: Tue, 3 Jun 2025 15:11:44 +0300
Subject: [PATCH] Update v1_monitoring.md

Explain about limitation we have in v1 - where we don't expose metrics during state machine operations
---
 content/operate/rs/monitoring/v1_monitoring.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/operate/rs/monitoring/v1_monitoring.md b/content/operate/rs/monitoring/v1_monitoring.md
index 93dd095450..fcd3cc8ce2 100644
--- a/content/operate/rs/monitoring/v1_monitoring.md
+++ b/content/operate/rs/monitoring/v1_monitoring.md
@@ -48,6 +48,8 @@ The internal monitoring system, while functional, has several limitations that a
 
 - **Stale data:** Stored metrics can lag behind real-time system states, reducing the effectiveness of alerting.
 
+- **Visibility gaps during management operations:** Metrics and statistics may not be available or updated during management tasks, resulting in incomplete monitoring during critical activities.
+
 - **Scalability constraints:** Internal storage and processing introduce performance overhead and are not optimized for large-scale observability pipelines.
 
 - **Limited extensibility:** The system is tightly coupled with internal components, making it difficult to integrate with modern monitoring ecosystems.