/
V2.0.0
Optimized the interaction by adjusting the function entry location.
Administrators should conduct regular health inspections for applications to ensure proper configuration of the application environment and in-app items for normal application operation.
The inspection content includes port, network service, storage service, environment configuration, and business configuration.
System Inspection
Inspects the CPU clock speed, the core quantity, the memory size, the memory usage, the available memory, the swap, the inspection time, the root directory disk, and the available space of root directory disk.
System Operation Status
Inspects the project startup path, the abnormal project folder size, the Xms configuration, the plugin information, the registration information, the web.xml file, the container version, the project JAR package information, and the server time.
Port Inspection
Inspects whether the server ports required for the normal use of FanRuan applications are open to avoid system function abnormalities
Network Inspection
Inspects whether the application components can ping each other and whether package loss exists.
Service Connectivity Inspection
Inspects whether services are connected.
Business Inspection
Inspects the FineDB, the log level, the log cleanup, the limit of disk space occupied by automatic backup, the quantity limit of automatic backup records retained, and the cleanup configuration of scheduled tasks.
Environment Inspection
Inspects the configurations of vm.overcommit_memory and vm.overcommit_ratio, Code Cache Configuration, Language Configuration-Duser.country, Language Configuration-Duser.language, ZIP-Related Configuration - Dsun.zip.disableMemoryMapping, and Configuration Related to Glibc Memory Leak.
Disk Inspection
1. Inspects the disk performance and usage to ensure the normal business operation.
2. Inspects the free disk space to prevent insufficient disk space from affecting normal system operation.
VM Inspection
Inspects the current system memory and the configuration of Headless Mode.
Non-Containerized Deployment Information
Inspects the process user and server main folder permissions.
Configuration Inspection
Inspects the external database coding, the NGINX health inspection, the NGINX parameter configuration, the cluster parameter configuration, the unlimited period configuration for resource update, the second-level cache enabling status, the SQL execution period limit, the cell quantity limit per template, the cell quantity limit during Excel import, the row quantity limit per dataset, the load alert enabling, and the dirty data detection.
The Health Inspection function is only applicable to usable projects. Otherwise, it prompts “Abnormal project status. Use this project after restoring it or view other projects.”
Health Inspection supprots manual inspection and automatic inspection.
Log in to FineOps as the admin, and click the project to be inpected.
Choose Health Inspection > System Inspection, and click Start Inspection to begin the inspection, as shown in the following figure.
FineOps inspects the port, the network service, the storage service, the environment configuration, and the business configuration of applications. Any exception will be displayed on the page.
After you fix/modify the configuration, you can click the Re-inspect button. FineOps will re-inspect the target application and output the latest results.
1. For details about the inspection items, see System Inspection Content.
2. The node IP address of the non-FineOps deployed standalone project may be displayed as 127.0.0.1.
Health Inspection can start automatically after being triggered.
Log in to FineOps as the admin, and click the project for which automatic inspection is required. Choose Health Inspection > System Inspection, and click the Inspection Setting button.
You can enable Automatic System Inspection. The system automatically conducts inspection at 11 AM every Sunday by default. You can also configure the execution time as needed, as shown in the following figure. /
The inspection content and the result items to be displayed are the same as those of the manual inspection.
Some exceptions can be fixed through Quick Fix.
Click Quick Fix as the admin, select the inspection items that need configuring, and click Apply Configuration to configure the values of the exception items with one click.
After successful configuration, it prompts “The configuration is applied successfully and takes effect after server restart.” After you restart the server, all the exceptions are successfully configured.
1. If you have no file read/write permission or cannot modify the configuration file, it will prompt "Failed to apply configurations as no read/write permission was granted to the configuration file." Click OK to exit the modification.
2. Some memory-related configuration items are associated and cannot be modified separately only partially. Therefore, the checkboxes before Exception Item are grayed out (ticked by default).
3. If no configuration items are available for Quick Fix, the button will be greyed out and cannot be clicked.
For details about the setting of inspection items, see System Inspection Content.
Inspection reports are generated based on the health inspection results. You can download/preview/batch download the reports.
The inspection report displays only the abnormal inspection items by default. You can switch to view all the inspection items of different nodes, as shown in the following figure.