Overview
Version
FineOps Version | Functional Change |
---|---|
V2.0.0 | / |
V2.1.0 | Limited the number and type of projects that could be connected to or deployed via FineOps Basic Edition to prevent exceptions caused by insufficient resources. |
V2.11.0 | FineOps Basic Edition supported the deployment of FineBI6.1 Basic Edition only. |
Application Scenario
Some users' servers are short of resources and cannot support the deployment of FineOps Standard Edition.
FanRuan has launched FineOps Basic Edition to address the O&M demands extensively.

This article details the differences between FineOps Basic Edition and FineOps Standard Edition.
Function Difference
Limitations on Project Deployment and Connection
FineOps Basic Edition is usually deployed on a server with insufficient resources.
Therefore, FineOps limits the number and type of projects that can be connected to or deployed via FineOps to prevent project crashes due to insufficient resources.
Function | Description |
---|---|
FineBI 6.1 deployment | When you deploy a FineBI 6.1 project via FineOps Basic Edition, note that:
|
FineReport/FineDataLink deployment | When you deploy a FineReport/FineDataLink project via FineOps Basic Edition, note that:
|
Cluster deployment | FineOps Basic Edition does not support the deployment of clusters. |
Project connection | FineOps Basic Edition supports the connection of one project only. |
Unavailable Tracing-Related Functions
By default, FineOps Basic Edition does not include the elasticsearch and skywalking_oap components, which renders some functions unavailable. These functions are detailed in the following table.
Function | Description |
---|---|
Health Monitoring | You can observe the stability status and performance of the system as well as the efficiency of O&M personnel. You can locate the object (such as dashboards and templates) where a problematic request resides through observation. |
Traffic Monitoring | You can understand the request traffic between projects and components, which helps troubleshoot issues of performance, connectivity, node balancing, and others. |
Template Performance | The performance of each template in the project is summarized and displayed for easier performance management. |
Tracing | The admin can help users collect and analyze the link details in the query request in case of dashboard/report lagging without passively waiting for the users' feedback. It allows for filtering requests by ID, time, etc., to facilitate further analysis and pinpointing of slow requests and precise identification of issues such as network fluctuations, database performance, abnormal configuration database, complex resources, and resource shortages. |
Resource Difference
The requirement on the FineOps server configuration is different, as shown in the following table.
Resource Requirement | FineOps Standard Edition | FineOps Basic Edition |
---|---|---|
Free physical memory size | At least 12 GB | At least 4 GB |
Free disk space | At least 100 GB | At least 50 GB |
Notes
Converting FineOps Basic Edition to FineOps Standard Edition cannot be achieved via upgrades or other methods and requires a reinstallation. Determine which edition to be installed carefully before deployment.