1. Supported single-time log download from multiple cluster nodes.
2. Supported log selection by specified service type.
1. Added Basic Log Information in O&M Log.
2. Supported log type selection during O&M log download.
Some companies have strict controls over equipment rooms. The process of entering an equipment room is complicated, and obtaining logs is time-consuming and labor-intensive. With FineOps, you can quickly and easily locate and download debug logs of O&M projects on the page.
For projects with heavy usage, logs grow quickly and may easily fill up the disk. In FineOps, you can set Data Retention Days in Log Management to control the log size.
In FineOps, you can view log storage locations and download the following types of logs.
You can view the log storage location and set the data retention days of logs in Log Management.
You can view the O&M log storage location of each project node.
Applicable Scope
This function applies only to projects that do not use the Elasticsearch component to store logs.
If the Elasticsearch component is installed for log storage, the Storage Location field displays Elasticsearch Log Service instead of a specific path.
Procedure
1. Log in to FineOps as the admin, select an O&M project, and choose Log > O&M Log.
2. In Log Management, click View next to Storage Location to view the O&M log storage location of each project node.
Notes
If a certain type of log does not exist, the storage location of that log is not displayed.
For heavily used projects, logs grow quickly and may easily fill up the disk. In FineOps, you can customize data retention days to control log storage usage.
This function applies only to projects that use the Elasticsearch component to store logs.
2. In Log Management, click Edit next to Data Retention Days.
3. Set the data retention days in the Rule Adjustment dialog box. The default retention period is 7 days.
4. Click Save. The configuration takes effect immediately.
1. Logs older than the retention period are automatically cleared. Do not set this value too small to avoid losing historical logs you require.
2. FineOps does not provide a direct log cleanup entry. To reduce disk space occupied by historical logs, you can shorten data retention days.
1. For projects that use Elasticsearch to store logs, two modes are available:
Download by Exact Time: It covers logs within the retention period and allows a time span of up to 2 days. The default precise-time range is from 2 hours before the current time to the current time.
Download by Daily: It has no date range limit and defaults to the current day.
2. Projects that use the Swift engine to store logs support Download by Day only, which defaults to the current day.
Supported types: fr, fdl, bi-web, bi-engine-worker, and bi-engine-master.
Selectable range: You can select service types that exist within the selected time period. All service types are selected by default.
Notes:
1. Service type selection is unavailable for projects not deployed via FineOps.
2. If no service type exists, this option is not displayed.
For supported types, see the table in the "Log Introduction" section of this document.
If a certain type of log does not exist, that type of log cannot be downloaded.
1. If the file size exceeds 5 GB, it cannot be exported, and the following prompt is displayed: "The size of the following log(s) exceeds the upper limit (5 GB), and the download failed: Log type"
2. If this type of log file does not exist, the log cannot be exported, and the following prompt is displayed: "The following log does not exist: Log type."
3. Logs are compressed during download. If the wait is too long, click Cancel Download to stop the download.
4. After decompression, the log files are organized by service type, date, and node address.
Problem Description
During log download, the "compress FanruanLog error" error occurs.
Cause Analysis
This is caused by insufficient disk space.
Solution
Expand the disk corresponding to the mounting directory of the O&M project to ensure sufficient space for compressed files.
After you (the admin) log in to FineOps, select an O&M project, and choose Log > O&M Log, the following error message is displayed: "Failed to connect the System O&M subprocess."
Troubleshooting:
1. Log in to the FanRuan application as the admin, choose System Management > Intelligent O&M > Crash Handling, and confirm that Auto Memory Stack Export is enabled.
2. Use the curl command to ensure network connectivity between FineOps and the project server.
3. If SSL is configured for both FineOps and the project, ensure that the certificates on both sides have not expired.
4. Disable and then re-enable the System O&M plugin, and reconnect FineOps and the O&M project.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy