chore: fix bad metric name

GreptimeTeam · Jan 9, 2024 · adbcaf2 · adbcaf2
1 parent 4ab7400
commit adbcaf2
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/docs/metrics-display.md b/docs/metrics-display.md
@@ -36,7 +36,7 @@ By default, 2 files are generated in the program's working directory
 | Meter     | write_failure_num                                  | Statistics on the number of failed writes.                                                                                                                                                                                                                                                                            |
 | Meter     | write_qps                                          | Write Request QPS                                                                                                                                                                                                                                                                                                     |
 | Timer     | async_write_pool.time                              | Asynchronous pool time statistics for asynchronous write tasks in SDK, this is important and it is recommended to focus on it.                                                                                                                                                                                        |
-| Timer     | direct_executor_timer_rpc-direct-pool              | he appearance of this metric means that we are using the current thread to execute the asynchronous callback of the rpc client, which is the default configuration.<br/> This is usually sufficient and very resource-saving, but it needs attention. When there are problems, replace it with a thread pool in time. |
+| Timer     | direct_executor_timer_rpc_direct_pool              | he appearance of this metric means that we are using the current thread to execute the asynchronous callback of the rpc client, which is the default configuration.<br/> This is usually sufficient and very resource-saving, but it needs attention. When there are problems, replace it with a thread pool in time. |
 | Timer     | req_rt_${service_name}/${method_name}              | The time consumption statistics of the request, the service name and method name are the names of the service and method of the grpc request.                                                                                                                                                                         |
 | Timer     | scheduled_thread_pool.${schedule_thread_pool_name} | Schedule thread pool execution task time statistics.                                                                                                                                                                                                                                                                  |
 | Timer     | serializing_executor_drain_timer_${name}           | Serializing executor. Drains all tasks for time consumption statistics                                                                                                                                                                                                                                                |

diff --git a/ingester-grpc/src/main/java/io/greptime/rpc/GrpcClient.java b/ingester-grpc/src/main/java/io/greptime/rpc/GrpcClient.java
@@ -131,7 +131,7 @@ public boolean init(RpcOptions opts) {
         if (this.useSharedRpcPool) {
             this.asyncPool = SHARED_ASYNC_POOL.getObject();
         } else {
-            this.asyncPool = new DirectExecutor("rpc-direct-pool");
+            this.asyncPool = new DirectExecutor("rpc_direct_pool");
         }
 
         initInterceptors();