The Rainbond platform displays component logs in the form of real-time push, which is convenient for users to quickly query logs and locate software faults.You can also query the history log by querying the history log file.
Component operation log
After the component runs, the log output to standard output (stdout) standard error output (stderr)will be captured by Rainbond and stored in aggregate.The way Rainbond handles component operation logs is to aggregate the logs of multiple instances to the component level, push them to the browser for real-time display, and store them on disk at the same time.
- Running log output interface
- Pause push：Pause log push, easy to pause analysis when key information is seen
- History log download：Rainbond will collect the logs in the last 7 days and save them. Users can click
History log downloadin the log interface to download the logs of the last 7 days to the local machine for analysis.
- The last 1000 logs：The last 1000 logs output
In the log display box, users can select
container IDto query only the running log of an instance; we try to push the log to the console in real time, but there will be a certain delay due to intermediate processing.
We recommend users to separate component running logs into access logs and program debug logs. Access logs generally want to be analyzed statistically, so more processing is required.It is recommended to output it to a persistent file, and then connect to other log analysis components for log analysis. The program Debug log is directly output, and it is quickly presented to developers to find and locate problems in time.
We can also only view the logs of the specified instance container, and the real-time performance of the container log will be relatively high. By default, it is refreshed every 5 seconds.
In Rainbond, log collection can also be connected to log analysis systems such as
ELASTICSEARCH, and the logs can be directly transmitted to the analysis system for analysis; for details, see Logs connected to ELK system.