Overview
Enterprises often encounter some pain points and challenges when managing FanRuan applications (FineReport and FineBI):
1. Inefficient O&M process: App admins are inexperienced in O&M experience, and professional O&M personnel cannot solve app problems in depth. The traditional O&M process is time-consuming and labor-intensive, resulting in low enterprise O&M efficiency and affecting the normal operation of the business.
2. Insufficient monitoring methods: O&M personnel may not be able to monitor the performance and availability of the project accurately, and lack the necessary tools and technologies in the O&M process.
3. Chaotic multi-project management: An enterprise may have multiple projects running, and these projects are managed by different departments or teams, resulting in inconsistent versions and different deployment environments, making it difficult to conduct unified O&M management.
Therefore, FanRuan launched the FineOps O&M platform to help enterprises better solve the above issues.
Function Positioning
The O&M platform is a tool that ensures the stable operation and comprehensive management of FanRuan applications.
By leveraging automation, centralization, and visualization, it enhances system stability and availability, reduces project management costs, accelerates fault diagnosis and problem resolution, and provides enterprises with all-around O&M solutions.
Navigation | Description |
|---|---|
FineOps Help Document | You can go to FineOps Help Document to learn more about the application scenarios and relevant documents of FineOps. |
Download and Installation | You can contact the technical support personnel to obtain the installation package of FineOps, then install and try it locally. For installation steps, see FineOps Deployment. |
Demo | You can contact the technical support personnel to obtain a demo. For contact methods, see Technical Support Channel Introduction. |
Problem Feedback | If there is any problem in the process of using FineOps, paid users can contact the technical support personnel. You can send an email to international@fanruan.com or click |
Functional Structure
FineOps is a monitoring and management system based on a variety of open-source tools and components, including prometheus, skywalking, and grafana, which cooperate to help the O&M personnel easily monitor, manage, and optimize FanRuan applications.
O&M Matrix:
Technical Structure:
Key Features
Feature | Introduction |
|---|---|
Automatic Application Deployment and Connection | Support rapid deployment of standalone FineReport/FineBI/FineDataLink projects, cluster projects, and required components. Configure the internal storage, CPU, environment variables, and environment parameters based on the deployment environment to ensure that the project is in the optimum state after deployment. |
Centralized Project Health Management | The system performance indicators of the project are comprehensively measured, and the system performance status is measured by the internationally accepted Apdex standardized indicators, so as to accurately display the actual user experience in the form of data. |
Quick Troubleshooting of Problems | When the project is unusable and has no response, FineOps can be used to quickly investigate the reasons and restore the system in time. Realize the closed loop of crash processing based on the prevention before the crash, the acquisition during the crash, the recovery after the acquisition, and the analysis after the recovery. |
Fast Identification of Performance Problems | When business personnel encounter problems such as delays or slowness when viewing reports or dashboards, they can use FineOps to quickly identify problems. |
Visualized Operation Management | Provide interfaces for modifying configuration files and managing start/stop operations of containerized projects and components, reducing the occurrence of human operation errors, so as to make the project run more healthily and stably. |
Scenario Advantages
FineOps Deployment: click this link for details
Containerized Deployment of FR/BI/FDL
Note: All the scenarios listed in the table below are for FanRuan applications deployed on Linux systems.
FanRuan recommends users use Linux system servers to deploy formal projects.
Project Life Cycle | Non-O&M Platform Deployment | O&M Platform + Non-O&M Platform Deployment | O&M Platform + O&M Platform Deployment | |
|---|---|---|---|---|
Deployment Phase | Environment Preparation | ✖ The deployment environment is not detected. The multi-engineering environment is not isolated. | ✖ The deployment environment is not detected. The multi-engineering environment is not isolated. | ✔ The deployment environment is strongly detected. The component environment is completely isolated. |
Project Deployment | ✖ Cluster components need to be deployed by yourself. The configuration databases need to be prepared by yourself. The project needs to be manually deployed in the background. The cluster and configuration components need to be connected by yourself. The engineering configuration needs to be optimized by yourself. | ✖ Cluster components need to be deployed by yourself. The configuration databases need to be prepared by yourself. The project needs to be manually deployed in the background. The cluster and configuration components need to be connected by yourself. The engineering configuration needs to be optimized by yourself. | ✔ One-click deployment of projects + configuration databases + cluster components + O&M components. Support connection with self-provided high-availability components. Support interfacial adjustment of port configuration. Optimize configurations such as component memory automatically. | |
Registration Authorization | ✔ Judge and choose the registration method according to the environment. Some registration methods need operations in the background of the server. | ✔ Judge and choose the registration method according to the environment. Some registration methods need operations in the background of the server. | ✔ Single registration method, all-around adaptation. Upload and register on the interface, no O&M technology is required. | |
Operation Monitoring | Resource Monitoring | ✖ Not supported | ✔ Support monitoring Linux servers Disk Networking CPU Memory ✖ Monitoring Windows is not supported | ✔ Support monitoring servers Disk Networking CPU Memory |
Application Monitoring | ✔ Disk Networking CPU Memory Load Monitoring time is short and backtracking is not supported | ✔ Disk Networking CPU Memory Load Thread pool GC status BI resource monitoring Support backtracking of historical resource status | ✔ Disk Networking CPU Memory Load Thread pool GC status BI resource monitoring Support backtracking of historical resource status | |
Component Monitoring | ✖ Not supported | ✔ Monitor MySQL configuration database Monitor ES log service Monitor Nginx inner gateway Monitor Redis status service Monitor MinIO file service Monitor BI accelerator Monitor Kafka pipeline service | ✔ Monitor MySQL configuration database Monitor ES log service Monitor Nginx inner gateway Monitor Redis status service Monitor MinIO file service Monitor BI accelerator Monitor Kafka pipeline service | |
| System Inspection | ✔ Inspection plugin | ✔ Inspection | ✔ Inspection Containerized standard environment (finish automatic optimization during updates when environmental requirements change in new versions) | |
Exception Handling | Performance Positioning | ✖ Need to passively wait for users to give feedback on problems. Inability to measure and locate problems. You need to analyze logs by yourself. | ✔ The system health observation mechanism will proactively detect the slow status of the system. Further locate problems through tracing, which can be specific to network fluctuations, database performance, configuration databases, complex resources, and insufficient resources. | ✔ The system health observation mechanism will proactively detect the slow status of the system. Further locate problems through tracing, which can be specific to network fluctuations, database performance, configuration databases, complex resources, and insufficient resources. |
| Exception Alert | ✔ Early warning of abnormal load Early warning of disk space | ✔ Early warning of abnormal load Early warning of disk space Early warning of crash reminder Early warning of abnormal cluster component status Early warning of thread blocking Early warning of too many opened files Customized early warnings | ✔ Early warning of abnormal load Early warning of disk space Early warning of crash reminder Early warning of abnormal cluster component status Early warning of thread blocking Early warning of too many opened files Customized early warnings | |
| Fault Handling | ✔ Support automatic recovery from crash. The coverage area related to automatic recovery after process disappearance takes precedence. | ✔ Linux Support automatic recovery from crash. The coverage area related to automatic recovery after process disappearance takes precedence. ✖ Windows Do not support the automatic recovery of project crashes in Windows server through the O&M platform. But can rely on the engineering data decision-making system's automatic crash recovery function. | ✔ Support automatic recovery from crash. Support automatic recovery after process disappearance. | |
| Fault Analysis | ✖ Need to obtain logs and analyze manually. | ✔ Support automatic analysis of stack and gc logs. | ✔ Support automatic analysis of stack and gc logs. | |
| Log Download | ✖ Require operations in the background of the server. | ✔ Download logs by date or type on the front end. Trigger and generate logs such as stack on the front end. | ✔ Download logs by date or type on the front end. Trigger and generate logs such as stack on the front end. | |
| Terminal Connection | ✖ Require operations in the background of the server. | ✖ Require operations in the background of the server. | ✔ Support front-end webshell to execute commands in the container. | |
Project O&M | Project Start/Stop | ✖ Require operations in the background of the server. | ✖ Require operations in the background of the server. | ✔ Perform interface operations on the front end of the O&M platform. Support starting/stopping applications and cluster components. |
| Update/Upgrade | ✔ Operate in the background of the server to replace JAR | ✔ Operate in the background of the server to replace JAR | ✔ One-click update/upgrade on the O&M platform remotely. Co-update/upgrade other components of the project. | |
| Backup/Restoration | ✖ Require manual remote backup. The platform can backup some key contents of the project. Require manual restoration. | ✔ Projects can be backed up to the machine where the O&M platform is located. Backup of cluster components is not supported. Require manual restoration. | ✔ Projects can be backed up to the machine where the O&M platform is located. Support the backup of containerized deployed cluster components. Support the entire restoration of backup content on the front end. | |
| File Management | ✖ Require operations in the background of the server. | ✔ Perform interface operations on the front end of the O&M platform. Support uploading, downloading, or viewing files. | ✔ Perform interface operations on the front end of the O&M platform. Support uploading, downloading, or viewing files. | |
| SSL Configuration | ✖ Require operations in the background of the server. | ✖ Require operations in the background of the server. | ✔ Upload on the front-end interface of the O&M platform | |
| Cluster Expansion | ✖ Require operations in the background of the server. | ✖ Require operations in the background of the server. | ✔ Add nodes on the front-end interface of the O&M platform | |
| Business Management | Resource Isolation | ✖ Not supported | ✔ Different nodes in the cluster serve different users. Different nodes in the cluster serve different business templates. | ✔ Different nodes in the cluster serve different users. Different nodes in the cluster serve different business templates. |
| Resource Priority | ✖ Not supported | ✔ Support the definition of high-priority resources, and prioritize them when resources are scarce | ✔ Support the definition of high-priority resources, and prioritize them when resources are scarce. | |
