Understanding FineOps Editions

  • Last update: 2024-04-28
  • Overview  

    Version 

    FineOps Version
    Functional Change
    V2.0.0/
    V2.1.0To prevent exceptions caused by insufficient resources, the number and type of projects that can be loaded into or deployed on FineOps Basic Edition are limited.

    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.

    FineOps Basic Edition can be deployed the same way as FineOps Standard Edition, and you just need to change the ./finekey statement to .finekey --lite.

    This article details the differences between FineOps Basic Edition and FineOps Standard Edition.

    Function Difference 

    Limitations on Project Deployment and Loading  

    FineOps Basic Edition is usually deployed on servers with insufficient resources.

    Therefore, it is necessary to limit the number and type of projects that can be loaded into or deployed on FineOps to prevent project crashes due to insufficient resources.

    Function
    Description
    Cluster deployment

    FineOps Basic Edition does not support the deployment of new clustered projects.

    Project loading

    FineOps Basic Edition supports the loading of only one non-containerized project.

    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

    Observes the stability and performance of the system as well as the efficiency of O&M personnel.

    Locates the object (dashboard, template, etc.) where a problematic request resides through observation.

    Traffic Monitoring

    Understands the request traffic between projects and components to troubleshoot issues of performance, connectivity, node balancing, etc.

    Template Performance

    Summarizes and displays the performance of each template in the project for easier performance management.

    Tracing

    (Admin) Helps 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 

     

    Resource Requirement
    FineOps Standard EditionFineOps Basic Edition
    Remaining free physical memoryAt least 12 GBAt least 4 GB
    Remaining free disk spaceAt least 100 GBAt 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 before deployment.


    Attachment List


    Theme: FineOps Deployment
    Previous
    Next
    • Helpful
    • Not helpful
    • Only read