Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update 2.deploy-connect-dashboard-ent.md #1298

Merged
merged 2 commits into from
Apr 26, 2022
Merged

Update 2.deploy-connect-dashboard-ent.md #1298

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
abb912a
Update 2.deploy-connect-dashboard-ent.md
abby-cyber Apr 26, 2022
9a4755d
Update 2.deploy-connect-dashboard-ent.md
abby-cyber Apr 26, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs-2.0/nebula-dashboard-ent/2.deploy-connect-dashboard-ent.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down