From 30ea19741a753c99fc8bfdd8b01e24bc32b22adc Mon Sep 17 00:00:00 2001
From: Meggielqk <126552073+Meggielqk@users.noreply.github.com>
Date: Thu, 24 Oct 2024 10:43:34 +0800
Subject: [PATCH] Edit and add zh translation

---
 en_US/changes/known-issues-5.8.md |  4 ++--
 zh_CN/changes/known-issues-5.8.md | 13 +++++++++++++
 2 files changed, 15 insertions(+), 2 deletions(-)

diff --git a/en_US/changes/known-issues-5.8.md b/en_US/changes/known-issues-5.8.md
index cc24bdb0d..c5e84c12c 100644
--- a/en_US/changes/known-issues-5.8.md
+++ b/en_US/changes/known-issues-5.8.md
@@ -45,9 +45,9 @@
   > **Workaround:**
   > Adjust the **Max Dashboard Record Size** through the Dashboard, or lower the `log.audit.max_filter_size` setting. Over time, problematic events will be cleared from the Audit log as new events are recorded.
 
-- **Distorted gauge values in `GET /monitor` HTTP API and Dashboard**
+- **Distorted Gauge Values in `GET /monitor` HTTP API and Dashboard**
 
-  For fresh data points in the `GET /monitor` HTTP API, which is used in the Dashboard as well, changing the time window from 1 hour to larger windows will distort the values of gauge values.  For example, 3 connections might become 9 or more.  This is only a visual distortion.  For data points older than 1 hour, however, data is irreversibly distorted.
+  When using the `GET /monitor` HTTP API, which also provides data for the Dashboard, changing the time window from 1 hour to a larger time frame may cause fresh data points (collected within the past hour) to appear distorted.  For instance, three connections may incorrectly display as nine or more. This issue is purely visual for data points within the past hour. However, for data older than 1 hour, the distortion is irreversible.
 
   Impacted gauges:
 
diff --git a/zh_CN/changes/known-issues-5.8.md b/zh_CN/changes/known-issues-5.8.md
index 26b5046db..5abbe5d51 100644
--- a/zh_CN/changes/known-issues-5.8.md
+++ b/zh_CN/changes/known-issues-5.8.md
@@ -36,6 +36,19 @@
 
   > **解决方法：** 通过 Dashboard 调整**最大 Dashboard 记录数**，或将 `log.audit.max_filter_size` 设置为较低的值。随着新事件的记录，问题事件将逐渐从审计日志中清除。
 
+- **`GET /monitor` HTTP API 和 Dashboard 中的指标值失真**
+
+  使用 `GET /monitor` HTTP API 时，该 API 同时也为 Dashboard 提供数据。如果将时间窗口从 1 小时调整为更长的时间范围，可能会导致最近 1 小时内的数据点显示失真。例如，3 个连接可能错误地显示为 9 个或更多。对于过去 1 小时内的数据点，这个问题仅为视觉上的失真。然而，对于超过 1 小时的数据，失真是不可逆的。
+
+  受影响的指标：
+
+  - `disconnected_durable_sessions`
+  - `subscriptions_durable`
+  - `subscriptions`
+  - `topics`
+  - `connections`
+  - `live_connections`
+
 ## e5.8.0
 
 - **节点崩溃竞态条件（始于 5.0，已在 5.8.1 中修复）**