Understanding Roles of FineOps Components- FineOps Help Document

Last update: 2025-02-20

Overview

FineOps Version	Functional Change
V2.0.0	/

FineOps consists of multiple O&M components in the red area in the following figure. This document details the role of each O&M component.

FanRuan has conducted custom development on these components to align with the product's functional requirements.

Therefore, you cannot use self-prepared components except for the self-prepared image repository.

Type	Component	Component Description
FineOps-related component	ops	It is a FineOps container that allows you to operate and maintain FanRuan projects.
	FanRuan internal gateway	Functioning as a centralized control point, it manages and routes all service access and usage requests.
	ops_agent	1. It allows you to manage and upgrade FineOps components. Each physical node should be equipped with an ops_agent component. 2. It collects the indicator information of the FineOps server and the nginx and elasticsearch components.
Monitoring and alerting	pushgateway	It temporarily stores the indicator data collected by ops_agent for prometheus to obtain it.
	prometheus	It uses pushgateway to obtain the indicator data collected by ops_agent and outputs it to the monitoring dashboard.
	grafana	It provides a monitoring dashboard.
	alertmanager	It is an alert container that allows you to modify the alert rule and the alert triggering condition.
Tracing	elasticsearch	It collects requests from FineReport, FineBI, external databases, business databases, and other external components in O&M projects.
Tracing	skywalking_oap	It is used to display tracing data, allowing you to manage and analyze the data.
Image repository	registry	It is a repository storing docker images.

中文（繁體）中文（简体）

English