From 93aaec3c8018e5e3b68e253a66cf66c28a6a2e0d Mon Sep 17 00:00:00 2001
From: "abby.huang" <78209557+abby-cyber@users.noreply.github.com>
Date: Tue, 26 Apr 2022 15:42:25 +0800
Subject: [PATCH] Update 2.deploy-connect-dashboard-ent.md (#1298)

* Update 2.deploy-connect-dashboard-ent.md

* Update 2.deploy-connect-dashboard-ent.md
---
 docs-2.0/nebula-dashboard-ent/2.deploy-connect-dashboard-ent.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs-2.0/nebula-dashboard-ent/2.deploy-connect-dashboard-ent.md b/docs-2.0/nebula-dashboard-ent/2.deploy-connect-dashboard-ent.md
index 880a21a1969..905fc716638 100644
--- a/docs-2.0/nebula-dashboard-ent/2.deploy-connect-dashboard-ent.md
+++ b/docs-2.0/nebula-dashboard-ent/2.deploy-connect-dashboard-ent.md
@@ -17,6 +17,7 @@ Before deploying Dashboard Enterprise Edition, you must do a check of these:
   | 9090 | The port of the prometheus service. |
   | 9200 | The port of the nebula-stats-exporter service. |
   | 9093 | The port of the Alertmanager service, used to receive Prometheus alerts and then send them to Dashboard.|
+  | 9100   | The port of the node-exporter service. The node-exporter is aumatically deployed on the target machine after a cluster is created or imported. It is used to collect the source information of machines in the cluster, including the CPU, memory, load, disk, and network.   |
   
 - The license is ready.