fix: chars_limit logger config is not exposed from dashboard

en_US/observability/log.md

@@ -53,12 +53,8 @@ Configure the following fields for general settings of the console log handler:
 
 - **Time Offset**: Define the format of the timestamp in the log. `system` is typed by default.
 
-- **Single Log Max Length**: Disabled by default, which means the maximum length of a single log message is unlimited. If you enable the toggle switch, you can specify the maximum length. When the length exceeds the limit, the log message will be truncated.
-
 - **Log Formatter**: Select the log format from the drop-down list. Optional values are: `text` and `json`. Default value is `text`. 
 
-  Note: If you select `json`, it is recommended to disable the toggle switch for **Single Log Max Length**, otherwise you will get incomplete json data.
-
 - **Single Line Mode**: Enabled by default. If you disable the toggle switch, log messages wrap around when being printed.
 
 - **Queue Length before Entering Sync Mode**: Set the number limit of buffered log events. If the message queue grows larger than the set value, the handler starts handling log events synchronously, which means that the client process sending the event must wait for a response. It is set to `100` by default. 
@@ -105,12 +101,8 @@ Configure the following fields for the general settings of the console log handl
 
 - **Time Offset**: Define the format of the timestamp in the log. `system` is typed by default.
 
-- **Single Log Max Length**: Disabled by default, which means the maximum length of a single log message is unlimited. If you enable the toggle switch, you can specify the maximum length. When the length exceeds the limit, the log message will be truncated.
-
 - **Log Formatter**: Select the log format from the drop-down list. Optional values are: `text` and `json`. Default value is `text`. 
 
-  Note: If you select `json`, it is recommended to disable the toggle switch for **Single Log Max Length**, otherwise you will get incomplete json data.
-
 - **Single Line Mode**: Enabled by default. When disabled, log messages wrap around when being printed.
 
 - **Queue Length before Entering Sync Mode**: Set the number limit of buffered log events. If the message queue grows larger than the set value, the handler starts handling log events synchronously, which means that the client process sending the event must wait for a response. It is set to `100` by default. 

zh_CN/observability/log.md

@@ -54,12 +54,8 @@ debug < info < notice < warning < error < critical < alert < emergency
 
 - **时间偏移量**：定义日志中时间戳的格式。默认情况下为 `system`。
 
-- **单条日志长度限制**：默认禁用，即不限制单条日志消息的最大长度。如果您启用切换开关，则可以指定最大长度。当长度超过限制时，日志消息将被截断。
-
 - **日志格式类型**：从下拉列表中选择日志格式。可选值为：`text` 和 `json`。默认值为 `text`。
 
-  注意：如果选择 `json`，建议禁用 **单条日志最大长度**，否则 json 数据不会完整显示。
-
 - **单行模式**：默认启用。如果禁用，日志消息打印时会自动换行。
 
 - **进入同步模式的队列长度**：设置缓冲日志事件的数量限制。如果消息队列超过设置值，则处理进程开始同步处理日志事件，这表明发送事件的客户端进程必须等待响应。默认设置为 `100`。
@@ -102,12 +98,8 @@ debug < info < notice < warning < error < critical < alert < emergency
 
 - **时间偏移量**：定义日志中时间戳的格式。默认情况下为 `system`。
 
-- **单条日志长度限制**：默认禁用，即不限制单条日志消息的最大长度。如果您启用切换开关，则可以指定最大长度。当长度超过限制时，日志消息将被截断。
-
 - **日志格式类型**：从下拉列表中选择日志格式。可选值为：`text` 和 `json`。默认值为 `text`。
 
-  注意：如果选择 `json`，建议禁用 **单条日志最大长度** 的切换开关，否则 json 数据不会完整显示。
-
 - **单行模式**：默认启用。如果禁用切换开关，日志消息打印时会自动换行。
 
 - **进入同步模式的队列长度**：设置缓冲日志事件的数量限制。如果消息队列超过设置值，则处理进程开始同步处理日志事件，这意味着发送事件的客户端进程必须等待响应。默认设置为 `100`。