Upgrade dashboard (#692)

* Delete search.html (#676) * upgrade dashboard Co-authored-by: min.wu <[email protected]>
vesoft-inc · Sep 3, 2021 · 38e30c0 · 38e30c0
1 parent c282569
commit 38e30c0
Show file tree

Hide file tree

Showing 2 changed files with 47 additions and 36 deletions.
diff --git a/docs-2.0/nebula-dashboard/1.what-is-dashboard.md b/docs-2.0/nebula-dashboard/1.what-is-dashboard.md
@@ -12,7 +12,7 @@ Dashboard monitors:
 
 - The information of clusters, including the information of services, partitions, configurations, and long-term tasks.
 
-Features of the enterprise package (TODO: planning)
+- Features of the enterprise package (TODO: planning)
 
 !!! enterpriseonly
 

diff --git a/docs-2.0/nebula-dashboard/2.deploy-dashboard.md b/docs-2.0/nebula-dashboard/2.deploy-dashboard.md
@@ -8,7 +8,7 @@ The correspondence between the Dashboard release and the Nebula Graph release is
 
 |Dashboard|Nebula Graph|
 |:---|:---|
-|{{dashboard.release}}|2.5.0, 2.0.1|
+|{{dashboard.release}}|2.x|
 
 ## Port
 
@@ -26,12 +26,11 @@ The deployment of Dashboard occupies the following ports:
 
 ## Download Dashboard
 
-Download the configuration files for the deployment.
+Download the tar package as needed, and it is recommended to select the latest version.
 
-| Dashboard tar-package | Nebula Graph version |
+| Dashboard package | Nebula Graph version |
 | :----- | :----- |
-| [nebula-graph-dashboard-{{ dashboard.release }}.x86_64.tar.gz](https://oss-cdn.nebula-graph.io/nebula-graph-dashboard/{{ dashboard.release }}/nebula-graph-dashboard-{{ dashboard.release }}.x86_64.tar.gz) | 2.5.0 |
-
+| [nebula-graph-dashboard-{{ dashboard.release }}.x86_64.tar.gz](https://oss-cdn.nebula-graph.com.cn/nebula-graph-dashboard/{{ dashboard.release }}/nebula-graph-dashboard-{{ dashboard.release }}.x86_64.tar.gz) | v{{nebula.release}} |
 
 ## Service
 
@@ -58,7 +57,7 @@ The above five services should be deployed as follows.
 To start the service, run the following statement in `node-exporter`:
 
 ```bash
-$ nohup ./node-exporter --web.listen-address=:9100 &
+$ nohup ./node-exporter --web.listen-address=":9100" &
 ```
 
 After the service is started, you can enter `<IP>:9100` in the browser to check whether the service is started normally.
@@ -73,40 +72,51 @@ After the service is started, you can enter `<IP>:9100` in the browser to check
 
   ```bash
   version: v0.0.4
-  nebulaItems:
-      - instanceName: metad0
-        endpointIP: 192.168.xx.1
-        endpointPort: 19559
-        componentType: metad
-      - instanceName: metad1
-        endpointIP: 192.168.xx.2
-        endpointPort: 19559
-        componentType: metad
-      - instanceName: metad2
-        endpointIP: 192.168.xx.3
-        endpointPort: 19559
-        componentType: metad
-      - instanceName: graphd0
-        endpointIP: 192.168.xx.4
-        endpointPort: 19669
-        componentType: graphd
-      - instanceName: storaged0
-        endpointIP: 192.168.xx.5
-        endpointPort: 19779
-        componentType: storaged
-      - instanceName: storaged1
-        endpointIP: 192.168.xx.6
-        endpointPort: 19779
-        componentType: storaged
-      - instanceName: storaged2
-        endpointIP: 192.168.xx.7
-        endpointPort: 19779
+  clusters:
+    - name: nebula
+      instances:
+        - name: metad0
+          endpointIP: 192.168.8.157
+          endpointPort: 19559
+          componentType: metad
+        - name: metad1
+          endpointIP: 192.168.8.155
+          endpointPort: 19559
+          componentType: metad
+        - name: metad2
+          endpointIP: 192.168.8.154
+          endpointPort: 19559
+          componentType: metad
+        - name: graphd0
+          endpointIP: 192.168.8.157
+          endpointPort: 19669
+          componentType: graphd
+        - name: graphd1
+          endpointIP: 192.168.8.155
+          endpointPort: 19669
+          componentType: graphd
+        - name: graphd2
+          endpointIP: 192.168.8.154
+          endpointPort: 19669
+          componentType: graphd
+        - name: storaged0
+          endpointIP: 192.168.8.157
+          endpointPort: 19779
+          componentType: storaged
+        - name: storaged1
+          endpointIP: 192.168.8.155
+          endpointPort: 19779
+          componentType: storaged
+        - name: storaged2
+          endpointIP: 192.168.8.154
+          endpointPort: 19779
+          componentType: storaged
   ```
 
 2. Run the following statement to start the service:
 
   ```bash
-  $ nohup ./nebula-stats-exporter --bare-metal --bare-metal-config=./config.yaml &
+  $ nohup  ./nebula-stats-exporter --listen-address=":9200" --bare-metal --bare-metal-config=./config.yaml &
   ```
 
 After the service is started, you can enter `<IP>:9200` in the browser to check whether the service is started normally.
@@ -128,6 +138,7 @@ After the service is started, you can enter `<IP>:9200` in the browser to check
       static_configs:
         - targets: [
             '192.168.xx.100:9200',  # The IP address and port of the nebula-stats-exporter service.
+            '192.168.xx.101:9200'
           ]
     - job_name: 'node-exporter'
       static_configs: