Overview
Version
FineOps Version | Functional Change |
|---|---|
| V1.5.5 | - |
| V1.5.7 | 1) Support single-time download of logs from multiple nodes in the cluster. 2) Support selection of logs for specified service types. |
| V1.5.9 | 1)O&M Log supports to check the Basic Log Information. 2) When downloading O&M Log, support to select the type of logs to download. |
| V1.13.0 | Platform Log download supports to download more logs related to operation components. |
| V2.0.0 | Optimize interaction and adjust the location of the function entry point |
| V2.1.0 | O&M Log downloading is still supported when the project is not available. |
| V2.3.0 | Add support for exporting two types of logs. 1) exporter.log: Indicator Collection Log 2) FineOperation. log: Log of Downtime Self-service Processing Tool |
Application Scenario
Some companies have strict control over the data center and cubersome application process for entrance, making log retrieval laborious.
FineOps supports rapid frontend identification and downloading of debug logs of operation project.
Log Introduction
Some companies have strict control over the data center and cubersome application process for entrance, making log retrieval laborious.
FineOps supports to view the storage location of operation log and enables downloading of operation log, including the following types of debug logs:
| Log | Description |
|---|---|
fanruan.log | FanRuan Application Runtime Log |
| standard.log | Only FineBI project supports to view and download this log. FineBI cluster log information is typically stored by default in the log/cluster directory. |
| eventlog | Only FineBI project supports to view and download this log. Record the specific information about dataset updates computed in the spark engine, which are useful for analyzing slow spark execution. |
| BIEvent.log | Only FineBI project supports to view and download this log. Record FineBI Configuration Operation. |
| polars.log | Only FineBI project supports to view and download this log. Calculation log involved in dashboard and dataset editing |
| operator_calculate.log | Only FineBI project supports to view and download this log. Calculation log involved in dashboard and dataset editing |
| access.log | The access log file of Nginx, which is used to record information about your requests to access a website, such as access, time, IP address, request method, access path, HTTP status code, and so on. |
| catalina.out | All ouput directed to the standard output and standard error of Tomcat will enter the catalina.out including logs generated by Tomcat itself during its operation, as well as logs outputted to the console by applications. |
| catalina.log | Some logs runned by Tomcat itself mainly record the activities of Tomcat during startup and shutdown. |
| localhost_access_log.txt | The request access log of Tomcat records details such as the request time, request type, requested resource, and the returned status code. |
| messages.txt | System log file in Linux system is used to record various events and error messages that occur within the system, such as startup, shutdown, hardware failure, software crash, and so on. This information can help administrators promptly identify and resolve system issues, ensuring the stable operation of the system. |
agent.log | ops-agent Component Log |
| exporter.log | Refer to index collection log recording information related to the collection of project index. |
| FineOperation.log | Downtime self-service tool log records information and execution details related to the scheduled tasks for downtime self-service handling. |
Check Basic Log Information
Operation Procedure:
1) Log in to FineOps as the admin, select the operation project, and choose Log > Operation Log.
2) In the Storage Location, click the View button to check the storage location of operational logs for each engineering node in the operation project.
Notes:
1) For the operation project of containerized deployment, such as installing the elasticsearch component for log storage, the storage location may not be displayed here, but prompt elasticsearch Log Service.
2) If there is no log of a certain type, the storage location of the log is not displayed.
Download Operation Log
| Number | Procedure | Notes |
|---|---|---|
| 1 | Log in to FineOps as the admin, select the operation project, and choose Log > Operation Log. | |
| 2 | Select Time Range | Selectable Range: 15 days ago ~ current date. The selected time span cannot exceed 2 days. Default Time: Today |
| 3 | Select Service Type | Supported Types: BI, FR Selectable Range: All service types that exist within the selected time. All options are selected by default. Notes: 1) Non-containerized operation project does not support selecting service type. 2) If none of the types exist, the option will not appear. |
| 4 | Select Node | Selectable Range: All nodes in the selected operation project. All options selected by default. |
| 5 | Select Logs to Download | Supported Type: Refer to Table 1.3 for details. Notes: 1) If a certain type of log does not exist, downloading log of that type is not supported. 2) In the operation project deployed through containerization, if the elasticsearch component is installed for log storage, the option to select this component will not be displayed. Logs will be downloaded in full directly. |
| 6 | Click the Download to generate operation log files and save them to your local computer. | 1) If the file size exceeds 5GB, the log cannot be exported, and a prompt will appear: The following log exceeds the size limit (5GB) and xxx cannot be downloaded. 2) If the log file of this type does not exist, the log cannot be exported, and a prompt will appear: The following log does not exist: xxx. 3) When downloading logs, files need to be compressed. If the waiting time is too long, users can click the Cancel Download button to stop the download. 4) After the downloaded files are decompressed, they are stored according to the structure: Node-Date-Service Type-Log Type. |
