Overview
This article explains the ports to be used by components and the ports to be opened on the FineOps server.
Component-Occupied Port
There are many components in FineOps, and their operation will occupy some server ports.
Before deployment, ensure that the default mapping port is not in use. If it is already in use, arrange other free ports.
| Component | Default Port Number |
|---|---|
| ops | 8081 |
| nginx | Root user deployment: 80 Non-root user deployment: 8090 |
ops-agent | 9071 |
| pushgateway | 9091 |
| prometheus | 9090 |
| grafana | 3000 |
| alertmanager | 9093 |
| elasticsearch | 9200 |
| skywalking_oap | 11800 and 12800 |
| registry | 5000 |
Networking
To ensure normal access to FineOps and smooth deployment and monitoring of O&M projects, certain server ports must be opened for use in different scenarios.
Extranet and FineOps
| Description | Extranet | Relation | FineOps |
|---|---|---|---|
| For the admin to access FineOps | O&M personnel (unlimited IP address | Access -> | FineOps nginx
|
| For FineOps to pull images from the cloud repository | FanRuan Cloud Image Repository (fineops-registry.cn-hangzhou.cr.aliyuncs.com:443) | <- Access | registry: 5000 |
FineOps
| Description | Internal Component of FineOps | Relation | Internal Component of FineOps |
|---|---|---|---|
| Request forwarding | FineOps nginx
| <-Access-> | ops: 8081 |
FineOps and O&M Project
| Description | FineOps | Relation | O&M Project |
|---|---|---|---|
| Basic O&M | FineOps nginx
| <- Access | FR/BI/FDL project node |
| Tracing | FineOps skywalking_oap: 11800 and 12800 | <- Access | FR/BI/FDL project node |
| Transmitting the server and component indicator information of the project to FineOps | FineOps nginx
| <- Access | ops-agent (project nodes and component nodes in clusters of unlimited servers): 9070 |
Pulling components from the image repository of FineOps for project deployment | registry: 5000 | <- Access | Project nodes and component nodes in clusters of unlimited servers |
