Actions64
- 定时任务 Actions
- 订阅管理 Actions
- 环境变量 Actions
- 配置文件 Actions
- 脚本管理 Actions
- 依赖管理 Actions
- 日志管理 Actions
- 系统设置 Actions
Overview
This node integrates with the QingLong Panel API to manage various resources including logs, crontabs, subscriptions, environments, configurations, scripts, dependencies, and system information. Specifically, for the "日志管理" (Log Management) resource and the "获取日志详情" (Get Log Details) operation, it fetches detailed log content from a specified log path and file.
Typical use cases include:
- Retrieving specific log details for troubleshooting or auditing purposes.
- Automating log retrieval as part of a monitoring or alerting workflow.
- Integrating QingLong logs into broader operational dashboards or reports.
For example, you can configure this node to get the content of a particular log file located at a given path on the QingLong server, enabling automated analysis or archival.
Properties
| Name | Meaning |
|---|---|
| 日志路径 (logPath) | The directory path where the log file is located. This is required to specify the exact location of the log. |
| 文件名 (logFile) | The name of the log file to retrieve details from. This is required to identify which log file's content to fetch. |
Output
The node outputs JSON data under the json.result field containing the detailed content of the requested log file. The structure depends on the QingLong API response but generally includes the log text or structured log entries.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the QingLong Panel API.
- The node makes HTTP requests to QingLong’s REST API endpoints.
- Proper network access to the QingLong server is necessary.
- No additional environment variables are explicitly required beyond the API authentication.
Troubleshooting
Common issues:
- Incorrect
logPathorlogFilevalues will result in errors or empty responses because the API cannot locate the specified log. - Authentication failures if the API key credential is missing or invalid.
- Network connectivity problems between n8n and the QingLong server.
- Incorrect
Error messages:
- If the operation is not implemented or parameters are incorrect, the node throws an error indicating the operation is not supported.
- API errors returned by QingLong will be surfaced as node errors; check the message for details such as "file not found" or "unauthorized".
Resolutions:
- Verify the correctness of the log path and filename.
- Ensure the API key credential is configured correctly and has sufficient permissions.
- Confirm network connectivity and firewall settings allow access to the QingLong API endpoint.
Links and References
- QingLong Panel API documentation: https://qinglong.online/api/
- n8n Documentation: https://docs.n8n.io/
- QingLong GitHub repository (for source and further info): https://github.com/whyour/qinglong