Project Management

  • Last update: 2026-01-28
  • Overview

    Version

    FineOps VersionFunctional Change
    V2.0.0Shifted the perspective from function‑based to project‑based. Except for some global settings, administrators could now perform all configuration within a single project.
    V2.8.0Added support for viewing the cause and manually refreshing the status when a project was in the Unusable state.
    V2.12.0

    Optimized global settings:

    1. Removed the original invalid Timeout Duration setting item.

    2. Added timeout check items, including:

    • SSH Connection Timeout

    • Startup Timeout

    • Client Container O&M Timeout

    • App Check Timeout

    • O&M Agent Process Check Timeout

    3. Added advanced settings:

    • Abort Deployment Upon Startup Failure

    • Certificate Domain Verification

    V2.24.0Displayed product versions and App IDs on the Project Management page.

    Function Description

    FineOps serves as an O&M tool for managing FineReport, FineBI, and other FanRuan applications.

    You (the admin) can either connect existing projects to FineOps or deploy new projects via FineOps.

    You can manage both the projects in FineOps and their components.

    Project Adding

    To use FineOps for project O&M, you need to connect these application projects to FineOps first.

    Function IndexFunction Description
    New Project Deployment

    It applies to scenarios where you have not deployed FineReport, FineBI, or FineDataLink projects.

    You can quickly deploy these projects via FineOps.

    Connecting to Existing ProjectsIt applies to scenarios where you want to connect already deployed FineReport, FineBI, or FineDataLink projects to FineOps.

    Project Overview

    The Project Management page displays all connected projects and related information. Two view modes are supported.

    1. Card view

    Key project information is displayed in cards, including the project name, status, deployment method, and active node count.

    InformationDescription
    Environment

    The deployment environment is categorized into Formal Environment and Trial Environment.

    • Formal Environment: It includes FineOps-deployed projects and projects not deployed via FineOps but later connected.

    • Trial Environment: It includes trial projects deployed via FineOps. For details, see Understanding Test and Formal O&M Projects.

    Project NameIt displays the project name set when the project is added.
    State
    • A normal project will be labelled Normal.

    • Projects labelled Unauthorized are registered, but have the O&M Platform/Intelligent O&M function point unregistered. Contact FanRuan sales for confirmation.

    • For projects labelled Unusable, you can hover over the status to view the reason for unavailability for further analysis. You can click the refresh button to update the project status.

    Deployment Information

    1. Deployment Method: It includes FineOps Deployment and Non-FineOps Deployment.

    It indicates the project deployment method.

    2. Active Node Count

    It refers to the number of active nodes in the project.

    Product VersionIt displays the main application type and version number of the project.
    App ID

    It is the unique identifier of the project, typically used for authentication purposes.

    Alert/Access URL

    Project alerts (if any) are displayed with priority.

    If there are no alerts, the project URL is shown and can be clicked to open in a new window.

    Supported Operation
    • Clicking a blank area of the card redirects you to the management page of the project.

    • You can click the  icon in the top-right corner of the card and perform the following operations: Component ManagementEditAdd Node, and Delete.

    2. List view

    Key project information is displayed in a detail table format, including the project name, status, and type, as shown in the following figure.

    InformationDescription
    Environment

    The deployment environment is categorized into Formal Environment and Trial Environment.

    • Formal Environment: It includes FineOps-deployed projects and projects not deployed via FineOps but later connected.

    • Trial Environment: It includes trial projects deployed via FineOps. For details, see Understanding Test and Formal O&M Projects.

    Project NameIt displays the project name set when the project is added.
    State
    • A normal project will be labelled Normal.

    • Projects labelled Unauthorized are registered, but have the O&M Platform/Intelligent O&M function point unregistered. Contact FanRuan sales for confirmation.

    • For projects labelled Unusable, you can hover over the status to view the reason for unavailability for further analysis. You can click the refresh button to update the project status.

    Active Node CountIt refers to the number of active nodes in the project.
    Deployment Method

    It includes FineOps Deployment and Non-FineOps Deployment.

    It indicates the project deployment method.

    Access AddressIt displays the URLs of the connected FineReport, FineBI, and FineDataLink projects.
    Operation
    • Clicking a project row redirects you to the Project Overview tab page.

    • You can click the following buttons: Detail, Component ManagementEditAdd Node, and Delete.

    Common Operation

    All operations in this section are illustrated in the default card view.

    Entering the Project-Specific Management Page

    Click any blank area of a project card to enter the dedicated management page of the project.

    • You can switch projects, navigate to other projects, edit or delete projects, compare projects, and return to the card view at the top of the page.

    • You can use various functions on different tab pages to manage the O&M project.

    Entering the Component Management Tab Page

    You can click  and Component Management to quickly access the Component Management tab page of the project.

    Adding a Node

    With the increase in business data volume and user visits, the originally deployed cluster may not meet the requirements and require more nodes for higher performance and scalability.

    You (the admin) can use the Add Node function to connect server nodes to the O&M project.

    For details, see Cluster O&M Project Scaling.

    Renaming a Project

    You can rename the projects in FineOps.

    Click Edit, set Project Name, and click OK.

    • The project name must not be empty or duplicated.

    • Only Chinese characters, English letters (upper and lower cases), and numbers are supported.

    • The project name length cannot exceed 12 characters.

    Modifying the Project URL

    Application Scenario

    FineOps generates a default URL for the project based on the IP address detected during project connection.

    However, you may later configure a domain name or assign different IP addresses for access purposes (such as exposing a public IP address for external users). These changes can render the generated URL invalid and inaccessible.

    In such cases, you must update the URL to the actual address used to access the project.

    Procedure

    1. Click the  icon and then the Edit button in the menu.

    2. Enter the correct access address. Click OK to confirm the modification.

    Deleting a Project

    You can disconnect a project from FineOps by removing it from the management list.

    iconNote:

    1. Deleting a project here only severs its connection with FineOps. The project itself will not be deleted and will continue to operate normally.

    2. If you encounter a project deletion failure prompt, upgrade FineOps to the latest version and try again.


    Global Setting

    Timeout Check

    Functions such as Maintenance, Business Tool, and Log depend on underlying connections. The timeout during the connection check will render the function unavailable.

    You can configure the timeout check settings on the Project Management page. These settings apply to all projects within FineOps.

    Setting ItemDefault ValueDescription
    SSH Connection Timeout60 s

    It refers to the SSH connection timeout duration for node adding during new project deployment or existing project scaling.

    If the duration is exceeded, the connection to the server will be considered abnormal, and the node adding will fail.

    Startup Timeout10 min

    It refers to the component startup timeout duration during new project deployment.

    If the duration is exceeded, the component startup will be considered failed, causing a deployment failure and rollback.

    Client Container O&M Timeout20 s

    It refers to the RPC timeout duration of ops_agent.

    If the duration is exceeded, the connection between FineOps and the ops_agent container will be considered failed, causing FineOps to be unable to monitor the O&M project properly.

    App Check Timeout20 s

    It refers to the RPC timeout duration between the application and FineOps.

    If the duration is exceeded, the O&M project will be considered unavailable.

    O&M Agent Process Check Timeout20 s

    It refers to the RPC timeout duration between the O&M agent process and FineOps.

    If the duration is exceeded, no stack dump files will be generated.

    Backup Setting

    Since backups consume server storage, you need to limit the number of backups and the disk space they occupy.

    Log in to FineOps as the admin, set the limits under Setting > Backup Setting, and click Save.

    These settings apply to all projects within FineOps.

    For details, see Project Backup.

    Tracing

    Before officially using the Tracing-related functions, configure the related parameters in the global settings first. These settings apply to all O&M projects in FineOps.

    Log in to FineOps as the admin, choose Setting > Tracing, configure these parameters, and click Save.

    For details, see Prerequisites for Using Tracing.

    Advanced Setting

    Setting ItemDescription
    Abort Deployment Upon Startup Failure
    • Enabled:

    The deployment will be aborted with a rollback if a component fails to start during the new project deployment.

    • Disabled:

    To facilitate troubleshooting and identifying the cause of deployment failures, it may be necessary to preserve the failed deployment state.

    Therefore, you are not advised to disable this function. Consider disabling it only when FanRuan technical support personnel are assisting in troubleshooting project deployment issues.

    Certificate Domain Verification
    • Enabled:

    The system verifies the domain name in the uploaded SSL certificate strictly to ensure consistency with the actual server domain name.

    If FineOps detects a domain name mismatch, the SSL configuration will fail.

    • Disabled:

    Due to the wide variety of certificate types, FineOps may occasionally fail to parse domain names correctly.

    If you are absolutely certain the certificate matches the server domain name but the verification in FineOps fails, you can disable this function and configure SSL again.

    Note that if this function is disabled, SSL can be configured even if the certificate does not match the server domain name, which will prevent normal access to the project. Disable it with caution.

    Restart Exception DaemonIf a component is stopped due to an exception and the maximum number of restart attempts is reached, the daemon will attempt to start the component.

    Attachment List


    Theme: Project Management
    Previous
    Next
    • Helpful
    • Not helpful
    • Only read

    滑鼠選中內容,快速回饋問題

    滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。

    不再提示

    10s後關閉

    Get
    Help
    Online Support
    Professional technical support is provided to quickly help you solve problems.
    Online support is available from 9:00-12:00 and 13:30-17:30 on weekdays.
    Page Feedback
    You can provide suggestions and feedback for the current web page.
    Pre-Sales Consultation
    Business Consultation
    Business: international@fanruan.com
    Support: support@fanruan.com
    Page Feedback
    *Problem Type
    Cannot be empty
    Problem Description
    0/1000
    Cannot be empty

    Submitted successfully

    Network busy