Overview
Version
FineOps Version | Functional Change |
|---|---|
| V1.5.9 | / |
| V1.6.0 | 1. Added component topology viewing. 2. Adjusted the display order, moving up Health Indicator in Past 1h. |
| V2.0.0 | Optimized the interaction by adjusting the function entry location. |
Function Description
For the connected O&M projects, FineOps provides admins with multi-angle monitoring and various operations.
For each project, FineOps extracts users' most concerned information and most commonly used operations, integrating them into the Overview page.
You can log in to FineOps as the admin, click Project Management, and select an O&M project to go to the Overview page.
Project Information
The following figure shows the information that can be displayed.
Content | Description |
|---|---|
Main Application | Type of the main application in O&M projects It includes fr, bi, and fdl. |
Application Status | Whether there are surviving nodes in O&M projects It includes usable and unusable. |
Application Version | Version of the main application in O&M projects It is precise to the minor version number, such as 11.0.15. |
Proportion of Surviving Nodes | For projects deployed via the O&M platform, it displays the total number of application nodes and the number of surviving nodes. For projects not deployed via the O&M platform, it only displays the number of surviving nodes, not the total number of nodes. |
Health Indicator in Past 1h
Overview
The following figure shows the information that can be displayed.
Content | Description | Display Prerequisite |
|---|---|---|
| Number of Alerts | The number of alerts triggered by the current project in the past hour | O&M platform's grafana, prometheus, and alertmanager components must be enabled for proper display. |
Comprehensive Health Index | A comprehensive indicator of the system's health conditions in the past hour Comprehensive health score = (number of satisfactory requests + number of tolerable requests / 2) / total number of requests) * 100% Satisfactory requests: requests that take less than three seconds and are successful Tolerable requests: requests that take between 3 and 12 seconds and are successful | O&M platform's elasticsearch and skywalking_oap components are enabled. O&M projects use JDK8u211 version or above. The system O&M plugin version in the projects is 1.4.9 or above. The FineBI version is 6.0.9 or above. |
Maximum Number of Concurrent Users | The maximum number of concurrent users per minute over the past hour using request slices |
System Health Monitoring
Clicking Health Indicator in Past 1h will redirect you to the Project Monitoring > Health Monitoring page of the project, where you can view detailed system health indicators.
Usage
Overview
The following figure shows the information that can be displayed.
Content | Description | Display Prerequisite |
|---|---|---|
Number of Running Containers | Displays the total number of containers and the number of running containers for each component. | Only displays components deployed via the O&M platform. Therefore, for projects not deployed via the O&M platform, there may be no components, and they will be displayed as 0. |
Allocated CPU | Displays the sum of allocated CPUs and the total CPU number across all containers. Allocated CPU: the sum of allocated CPUs across all containers (If any container does not have CPU limits, displays --.) Total CPU number: the total CPU number across various containers | Supports displaying projects deployed via the O&M platform For projects not deployed via the O&M platform, CPU allocation is unrestricted, displays --. |
Allocated Memory | Displays the sum of allocated memories and the total memory number across all containers. Allocated memory: the sum of allocated memories across all containers (If any container does not have memory limits, displays --.) Total memory number: the total memory number across various containers | Supports displaying projects deployed via the O&M platform For projects not deployed via the O&M platform, displays the sum of heap memory and off-heap memory across all nodes. |
Allocating CPU/Memory
The following operations are only applicable to projects deployed via the O&M platform.
Application scenario:
1．Under Allocated CPU, a yellow warning appears with a tooltip stating "The project has allocated x Cores of CPU. There are x components with unrestricted CPU limits. You can set limits in Component Management."
2．Under Allocated Memory, a yellow warning appears with a tooltip stating "The project has allocated x GB of memory. There are x components with unrestricted memory limits. You can set limits in Component Management."
3．In Allocated CPU and Allocated Memory indicators, if the limit values are highlighted in red, it means that the limits exceed the available resources, suggesting an unreasonable allocation that should be adjusted.
Procedure:
1．Click Settings or choose Project Management > Project > Maintenance > Component Management.
2．Set/Modify CPU and memory limits in the Modify Configuration section for each component, then click OK to apply the changes.
Component - List
Overview
The following figure shows the information that can be displayed in the List section.
Content | Description | Display Prerequisite |
|---|---|---|
List - Component Name | Types of containerized components and the IP addresses of servers where each component resides | Only displays components deployed via the O&M platform. Therefore, for projects not deployed via the O&M platform, there may be no components, and they will be displayed as null. |
List - Component Status | Percentage of running nodes for various types of containerized components, along with their running status It includes running and stop. | |
List - Operation | Supports operations on various types of containerized components. It includes start, restart, and stop. |
Component Start/Stop
The following operations are only applicable to projects deployed via the O&M platform.
1．Supporting starting, restarting, and stopping individual/all fr, bi, and fdl components.
2．Supporting starting mysql and redis components if they are not started, but do not support any operations on started mysql and redis.
3．Supporting starting, restarting, and stopping other components integrally.
Component Management
Click Component to go to the Project > Maintenance > Component Management page and manage components.
For details, see Component Management.
Component - Topology
Component topology is mainly used for cluster projects:
It helps the admin check whether each node and cluster component is connected.
It helps the admin check whether the number of project nodes matches the planned number.
It helps the admin check whether the servers and ports occupied by each component match the plan.
Overview
The Overview page displays the structural topology relationships between various components.
Oval represents a single type of component and displays its name. (You can click it to view multiple containers under this type.)
Circle represents a single container and displays its IP address and port number.
Line represents dependency relationships between components/containers. If the line is red, it indicates that the service cannot be connected.
Component Details
Click a component in the topology diagram and click View Details to view component details.
Information | Description |
|---|---|
Component Name | Displays the component name |
Proportion of Run Containers | The number of containers run under this type of component/total number of containers |
Container Running Status | The running status of each container under this type of component It includes running and stop. |
Container IP Address | Server IP addresses where each container under this type of component resides |
Container Port Number | Server port numbers where each container under this type of component occupies |
Show Advanced Information | Only FineBI projects support showing advanced information. Ticking it for other types of projects has no effect. After ticking the button, you will see the following information of each container: id、name、ip、httpPort、grpcPort、syncType、dbPath、timestamp
|
Viewing Traffic Typology
Click View Traffic Typology to go to the Project Monitoring > Traffic Monitoring page and view the traffic relationships between components.
Previous：Template Performance