Cloud platform full-automatic management log collection method and terminal

Abstract

The invention provides a full-automatic management log collection method for a cloud platform. The method comprises the following steps of judging whether Filebeat is started or not, reading a SideCar configuration file, updating log collection configuration according to heartbeat interval time during operation, adding a configuration file to be newly added to a file beat configuration file directory, and closing a module. According to the cloud platform full-automatic management log collection method and the terminal, the collection configuration is automatically pulled from the server side, the latest configuration file is dynamically loaded, and restarting is not needed in the period. Meanwhile, the log collection terminal sends the operation state to the server side, and whether the log collection terminal operates normally or not can be found in a state monitoring mode. The new version of the terminal is automatically detected and collected, and is automatically downloaded, updated and restarted, and the process does not need manual intervention of a user.

Description

technical field [0001] The invention relates to the technical field of log collection terminal systems, in particular to a cloud platform automatic management log collection method and terminal. Background technique [0002] With the development of cloud platforms, more and more service products provide software services to users through cloud platforms as media, including databases, bastion machines, etc. that everyone usually uses. [0003] In the prior art, the above-mentioned service products generate a large number of various logs during operation. The logs record the running status and behavior of the service products. The cloud platform needs to collect, store, and analyze these logs to understand the service. Whether the product has stability, performance and other issues. [0004] However, in the process of service product evolution, some log files that do not need to be collected need to be collected. The original one log corresponding to one line is changed to mu...

AI Technical Summary

Problems solved by technology

[0004] However, during the evolution of service products, some log files that do not need to be collected originally need to be collected. Originally, one log corresponds to one line and changed to multi-line printing, and the original multi-line matching rules are no longer applicable. If the terminal is affected, its collection configuration needs to be reset, and then mirrored to provide services for service product log collection

At the same time, during the operation of the collection terminal, it is unavoidable that some factors that cannot be pitted will cause it to stop running or have problems, resulting in the failure to collect logs normally or the logs cannot be sent to the back-end storage system normally after collection.

Fix the problems found during the operation of the log collection component. After the new version is released, it cannot be upgraded uniformly, and the user needs to upgrade by himself or invade the user's virtual machine to upgrade

Images