fix: modify the vhost_socket_path type

deepflowio · Nov 27, 2024 · 990c811 · 990c811
1 parent aa056a1
commit 990c811
Show file tree

Hide file tree

Showing 3 changed files with 17 additions and 17 deletions.
diff --git a/server/agent_config/README-CH.md b/server/agent_config/README-CH.md
@@ -2811,7 +2811,7 @@ inputs:
 **模式**:
 | Key  | Value                        |
 | ---- | ---------------------------- |
-| Type | bool |
+| Type | string |
 
 **详细描述**:
 

diff --git a/server/agent_config/README.md b/server/agent_config/README.md
@@ -2876,7 +2876,7 @@ inputs:
 **Schema**:
 | Key  | Value                        |
 | ---- | ---------------------------- |
-| Type | bool |
+| Type | string |
 
 **Description**:
 
@@ -3554,15 +3554,15 @@ You can use the command 'lspci -vmmk' to find the network card driver type. For
      Rev:    02
      Driver: igb_uio
      Module: i40e
-     
-In the example above, "Driver: igb_uio" indicates a DPDK-managed device (other options include 
-"vfio-pci" and "uio_pci_generic", which are also managed by DPDK). The actual driver is 'i40e' 
+
+In the example above, "Driver: igb_uio" indicates a DPDK-managed device (other options include
+"vfio-pci" and "uio_pci_generic", which are also managed by DPDK). The actual driver is 'i40e'
 (derived from 'Module: i40e').
 
-You can use the sustainable profiling feature provided by DeepFlow to perform function profiling on the DPDK application and check the specific interface names. Alternatively, you can run the `perf` command on the node where the agent is located:  
-`perf record -F97 -a -g -p <DPDK application PID> -- sleep 30`  
-and then use  
-`perf script | grep -E 'recv|xmit'`  
+You can use the sustainable profiling feature provided by DeepFlow to perform function profiling on the DPDK application and check the specific interface names. Alternatively, you can run the `perf` command on the node where the agent is located:
+`perf record -F97 -a -g -p <DPDK application PID> -- sleep 30`
+and then use
+`perf script | grep -E 'recv|xmit'`
 to confirm the driver interfaces.
 
      Below are some common interface names for different drivers, for reference only:

diff --git a/server/agent_config/template.yaml b/server/agent_config/template.yaml
@@ -1790,7 +1790,7 @@ inputs:
       # name: vHost User
       # description:
       vhost_user:
-        # type: bool
+        # type: string
         # name: vHost Socket Path
         # unit:
         # range: []
@@ -2228,16 +2228,16 @@ inputs:
           #     Driver: igb_uio
           #     Module: i40e
           #     ```
-          #     In the example above, "Driver: igb_uio" indicates a DPDK-managed device (other options include 
-          #     "vfio-pci" and "uio_pci_generic", which are also managed by DPDK). The actual driver is 'i40e' 
+          #     In the example above, "Driver: igb_uio" indicates a DPDK-managed device (other options include
+          #     "vfio-pci" and "uio_pci_generic", which are also managed by DPDK). The actual driver is 'i40e'
           #     (derived from 'Module: i40e').
           #
           #     You can use the sustainable profiling feature provided by DeepFlow to perform function profiling
           #     on the DPDK application and check the specific interface names. Alternatively, you can run the
-          #     `perf` command on the node where the agent is located:  
-          #     `perf record -F97 -a -g -p <DPDK application PID> -- sleep 30`  
-          #     and then use  
-          #     `perf script | grep -E 'recv|xmit'`  
+          #     `perf` command on the node where the agent is located:
+          #     `perf record -F97 -a -g -p <DPDK application PID> -- sleep 30`
+          #     and then use
+          #     `perf script | grep -E 'recv|xmit'`
           #     to confirm the driver interfaces.
           #
           #     Below are some common interface names for different drivers, for reference only:
@@ -2294,7 +2294,7 @@ inputs:
           #
           #     可以使用 deepflow 提供的可持续剖析功能对 DPDK 应用做函数剖析查看具体接口名字，也可以使用 perf 命令
           #     在agent所在节点上运行 `perf record -F97 -a -g -p <dpdk应用进程号> -- sleep 30`，`perf script | grep -E 'recv|xmit'`
-          #     来确认驱动接口。 
+          #     来确认驱动接口。
           #
           #     下面列出了不同驱动对应的接口名称，仅供参考:
           #      1. Physical NIC Drivers: