Overview
Version
| FineOps Version | Functional Change |
|---|---|
| V1.5.6 | Supported the downloading of FineOps logs. |
| V1.13.0 | Supported the downloading of O&M component logs |
| V2.0.0 | 1. Added the deploy_error.log file to record the container startup errors that may arise in deploying O&M projects. 2. Optimized the interaction by adjusting the function entry location. |
Function Description
If FineOps malfunctions, you can troubleshoot the issue with the FineOps log and O&M component logs. However, some companies have strict control over the computer room, the application process for entering the computer room is complicated, and the log acquisition is time-consuming and laborious.
Log Introduction
You can download FineOps and O&M component logs on FineOps, which are described in the following table.
Log | Description |
|---|---|
dockerLogs.log | Log file of the following containers inside Docker: ops nginx alertmanager grafana prometheus pushgateway registry ops_agent elasticSearch skywalking_oap |
| access.log | Access log of FineOps nginx, recording the request information of users' accesses to FineOps, such as access time, IP address, request method, access path, and HTTP status code. |
| error.log | Log file recording unexpected errors of FineOps. |
| fanruan.log | FineOps operation log. |
| agent.log | Log file of the ops-agent component. |
| deploy_error.log | Log file recording container startup errors that may arise in deploying O&M projects. |
FineOps Log Downloading
1. Log in to FineOps as the admin and choose Platform Management > Platform Log.
2. Set the operation time range.
You can select any time range, but if it extends beyond the log file coverage, the downloaded file will only contain logs within the existing range.
The operation time range defaults to the previous day to the current day.
3. Click Download to generate the FineOps log file and save it to your local computer.
The log cannot be exported if the file size exceeds 5 GB. A prompt will appear saying "The size of the following log(s) exceeds the upper limit (5 GB) and the download failed: Log name."
The log file will be compressed when downloaded, which may take a while.
After decompression, the downloaded log files are stored in different folders by component type.
Previous：FineOps Monitoring