Log time-sharing management method and device, equipment and storage medium

Abstract

The invention provides a log time-sharing management method and device, equipment and a storage medium, firstly, service logs are uniformly collected and managed in a time fragmentation mode, then the whole request link log is associated through traceId, and single services are distinguished through service identifiers, so that the efficiency in problem positioning is greatly improved, and the time-sharing management efficiency is greatly improved. And meanwhile, powerful data support can be provided for system optimization by collecting and analyzing the whole call chain log. All service calling link logs are stored in a log file in a time-sharing service log collection mode, the whole calling link process is connected in series through unique traceId, and log details including calling of services, calling duration, whether asynchronization exists or not can be quickly inquired.

Description

technical field [0001] The present invention relates to the field of computer software, more specifically, to a log time-sharing management method, device, equipment and storage medium. Background technique [0002] Log collection and storage is an essential part of the service link life cycle. Logs are not only used to locate abnormal problems, but also provide effective data reference for analyzing server status and user behavior. Logs are usually numerous and miscellaneous. If the logs cannot be collected and organized well, it may take a long time to collect effective information, and even draw wrong conclusions. In terms of log management methods, the current common implementation method Each service maintains its own log, and only manages the log of this service. Although there are full-link implementation cases, it still does not get rid of the log isolation between services. Therefore, the current log management method has obvious log isolation between services, whi...

AI Technical Summary

Problems solved by technology

Logs are usually numerous and miscellaneous. If the logs cannot be collected and organized well, it may take a long time to collect effective information, and even draw wrong conclusions. In terms of log management methods, the current common implementation method Each service maintains its own log, and only manages the log of this service. Although there are full-link implementation cases, it still does not get rid of the log isolation between services

Therefore, the current log management method has obvious log isolation between services, which takes a long time and is not conducive to operations such as data query, abnormal location, and data analysis.

Images