Log file storage method and device

Abstract

The invention relates to the technical field of computers, in particular to a log file storage method and device. The method comprises the following steps: determining a storage path corresponding toeach pod when Kurbernetes start each pod; obtaining each host path of the host machine, and setting a corresponding relationship between the storage path and the host path, so that the storage path ismounted under the host path; and storing the log file generated by each pod into the storage path, and synchronously storing the log files in the storage path into the host machine according to the corresponding relationship between the storage path and the host machine path, so that a user can search the log files through the host machine. By applying the method provided by the invention, the log file generated by the pod can be stored in the host machine, and the user can quickly find the required log file according to the host path in the host machine, so that the process of querying the log file by the user is simplified, and the query experience of the user is improved.

Description

technical field [0001] The invention relates to the technical field of computers, in particular to a method and device for saving log files. Background technique [0002] In the container cluster management system (Kurbernetes, K8S), there are multiple resource type group pods, and each pod corresponds to a main process. Users can query the log files corresponding to each pod in Kubernetes to understand the execution status of the main process corresponding to each pod, so as to meet the needs of users to manage and monitor each pod in Kubernetes. [0003] In the kubernetes of the prior art, the log collection system fluentd is generally used to output the log files generated by each pod, and to persist each output log file. However, fluentd is a relatively large log plug-in, and its deployment is complicated. It is not suitable for some simple back-end system development. In the process of saving the log files corresponding to each pod, it is impossible to transfer the log...

AI Technical Summary

Problems solved by technology

However, fluentd is a relatively large log plug-in, and its deployment is complicated. It is not suitable for some simple back-end system development. In the process of saving the log files corresponding to each pod, it is impossible to transfer the log files between each pod. Log file names are differentiated

And when the user needs to query the log files corresponding to each pod in Kubernetes, he needs to enter Kubernetes and enter a series of query commands to obtain the log files required by the user, and since each log file has not been differentiated, In the process of obtaining log files, users usually need to search and compare one by one, which brings a bad experience to users

Images