CN110008103B - Log collection method, system, device and storage medium for third-party application program - Google Patents
Log collection method, system, device and storage medium for third-party application program Download PDFInfo
- Publication number
- CN110008103B CN110008103B CN201910286400.6A CN201910286400A CN110008103B CN 110008103 B CN110008103 B CN 110008103B CN 201910286400 A CN201910286400 A CN 201910286400A CN 110008103 B CN110008103 B CN 110008103B
- Authority
- CN
- China
- Prior art keywords
- log
- log information
- party application
- sys
- write
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 80
- 230000006870 function Effects 0.000 claims description 35
- 238000001914 filtration Methods 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 11
- 101100537665 Trypanosoma cruzi TOR gene Proteins 0.000 claims description 6
- 230000000694 effects Effects 0.000 abstract description 7
- 238000012986 modification Methods 0.000 abstract description 7
- 230000004048 modification Effects 0.000 abstract description 7
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
- G06F11/3476—Data logging
Abstract
The application discloses a log collection method of a third-party application program, which comprises the following steps: calling a sys _ write () function obtained after modifying the system kernel, and copying the log information of each process to a buffer area; and reading the log information of the buffer area, and writing the log information into a corresponding log file according to a distribution rule. According to the method and the system, log information is copied by using the sys _ write () function, the sys _ write () function is called and realized by modifying the system kernel, and the source code of the third-party application program is not required to be modified, so that the realization mode of the third-party application program log module is not concerned, the modification mode is simple, the effect is convenient, and the method and the system have quite high practical value. Correspondingly, the application also discloses a log collection system, a log collection device and a storage medium of the third-party application program.
Description
Technical Field
The present invention relates to the field of system operation and maintenance, and in particular, to a method, a system, an apparatus, and a storage medium for collecting logs of a third-party application.
Background
A set of qualified systems must have maintainability, log management is used as a part for supporting the maintainability, plays an important role in monitoring the systems and problem positioning in the operating environment, and is an important means for finding problems, analyzing the problems and solving the problems.
Linux distribution (such as a CentOS) generally integrates a series of open-source third-party application programs, developers of the application programs are different, log modules are different in implementation modes, program logs are directly printed to standard output, some program logs are printed to certain files, and in order to ensure that the logs are not lost and the problem of quick positioning through log combing is ensured, logs of the third-party application programs need to be collected for the second time and managed in a unified mode.
In the prior art, a syslog is generally adopted to collect logs, a third-party application program calls an interface function syslog () of the syslog to send the logs to a syslog daemon, the syslog determines whether log information of different sources and different levels needs to be stored according to configuration in a configuration file, and if the log information needs to be stored, a configuration item determines the storage position of the log information. If a third-party application program does not call the syslog () interface and directly uses printf () to print the log to the standard output, the log of the application program cannot be collected, and the log is lost.
Therefore, how to provide a solution to the above technical problems is a problem to be solved by those skilled in the art.
Disclosure of Invention
In view of the above, the present invention provides a method, a system, a device and a storage medium for collecting logs of third-party applications, so as to record logs of all third-party applications reliably in time. The specific scheme is as follows:
a log collection method for a third party application, comprising:
calling a sys _ write () function obtained after modifying the system kernel, and copying the log information of each process to a buffer area;
and reading the log information of the buffer area, and writing the log information into a corresponding log file according to a distribution rule.
Preferably, the distribution rule includes a message level and a message origin.
Preferably, the message level includes:
EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO, DEBUG.
Preferably, the message sources include:
program name and process number pid.
Preferably, the calling a function of sys _ write () obtained after modifying the system kernel and copying the log information of each process to the buffer further includes:
and calling the sys _ write () function to copy the log information passing through the filtering rule to the buffer.
Preferably, the filtering rule is specifically:
and filtering the log information meeting a preset program name, a preset process number or a preset file name.
Preferably, the process of reading the log information in the buffer and writing the log information into a corresponding log file according to a distribution rule specifically includes:
and reading the log information of the buffer area in cooperation with the frequency of copying the log information of each process to the buffer area, and writing the log information into a corresponding log file according to a distribution rule.
Correspondingly, the invention also discloses a log collection system of the third-party application program, which comprises the following steps:
the reading module is used for calling a sys _ write () function obtained after modifying the system kernel and copying the log information of each process to the buffer area;
and the distribution module is used for reading the log information of the buffer area and writing the log information into a corresponding log file according to a distribution rule.
Correspondingly, the invention also discloses a log collecting device of the third-party application program, which comprises the following steps:
a memory for storing a computer program;
a processor for implementing the steps of the log collection method of the third party application as claimed in any one of the above when executing the computer program.
Correspondingly, the invention also discloses a storage medium, wherein the storage medium stores a computer program, and the computer program realizes the steps of the log collection method of the third-party application program when being executed by a processor.
The invention discloses a log collection method of a third-party application program, which comprises the following steps: calling a sys _ write () function obtained after modifying the system kernel, and copying the log information of each process to a buffer area; and reading the log information of the buffer area, and writing the log information into a corresponding log file according to a distribution rule. The invention utilizes the sys _ write () function to copy the log information, the sys _ write () function is realized by modifying the system kernel call, and the source code of the third-party application program is not required to be modified, so the realization mode of the third-party application program log module is not concerned, the modification mode is simple, the effect is convenient, and the practical value is quite high.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a flowchart illustrating a log collection method for a third-party application according to an embodiment of the present invention;
FIG. 2 is a schematic diagram of a buffer of a log collection method of a third-party application according to an embodiment of the present invention;
FIG. 3 is a structural distribution diagram of a log collection system of a third-party application according to an embodiment of the present invention;
fig. 4 is a structural distribution diagram of a log collection device of a third-party application according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the prior art, a syslog is generally adopted to collect logs, a third-party application program calls an interface function syslog () of the syslog to send the logs to a syslog daemon, the syslog determines whether log information of different sources and different levels needs to be stored according to configuration in a configuration file, and if the log information needs to be stored, a configuration item determines the storage position of the log information. If a third-party application program does not call the syslog () interface and directly uses printf () to print the log to the standard output, the log of the application program cannot be collected, and the log is lost. The invention utilizes the sys _ write () function to copy the log information, the sys _ write () function is realized by modifying the system kernel call, and the source code of the third-party application program is not required to be modified, so the realization mode of the third-party application program log module is not concerned, the modification mode is simple, the effect is convenient, and the practical value is quite high.
The embodiment of the invention discloses a log collection method of a third-party application program, which is shown in figure 1 and comprises the following steps:
s1: calling a sys _ write () function obtained after modifying the system kernel, and copying the log information of each process to a buffer area;
after the system kernel is modified in the system kernel space, the sys _ write () function can be called to copy one copy of log information written by each process, and the log information is recorded in the buffer. The buffer is typically recycled and when space is scarce, old log information is discarded.
The log information is short for message, and comprises two parts of a message header and a message body, wherein the message header comprises the total length of the message and the length of the message body, and the message body comprises the source process name, the source process pid and the print content in the sys _ write () function.
The structure of the buffer area for recording messages is shown in fig. 2, where the first message is marked by "message start position", the current writing position is marked by "next message writing position", and when "message start position" is equal to "next message writing position", either the buffer area is empty or the buffer area is full; if the buffer area is full, pushing the message starting position backwards, and discarding the old message one by one until the new message can be accommodated; when the space from the "next message writing position" to the "buffer ending position" is not enough to store a message body and a message header, the "next message writing position" is moved to the "buffer starting position", a message header is stored in the "buffer ending position", and all members of the message header are 0, which indicates that the buffer has wrapped around. Since the buffer is used circularly, the absolute position alone cannot accurately represent the "first message" and the "last message", and therefore the "first message number" and the "next message number" are used to represent the "first message" and the "next message to be written" in the buffer.
Specifically, the log information of the buffer is read from the device node/proc/log _ record, and the format of the log information is generally: process name [ process number ]: the message content.
S2: and reading the log information of the buffer area, and writing the log information into a corresponding log file according to a distribution rule.
And matching the distribution rule according to the process name and the process number of the log information, writing a corresponding target file, namely the log file, if the matching is successful, and discarding the log information if the distribution rule cannot be matched.
Specifically, the frequency of copying the log information of each process to the buffer is matched, the log information of the buffer is read, and the log information is written into the corresponding log file according to the distribution rule.
It can be understood that when the buffer is recycled, new log information will soon overwrite previous log information, and therefore the corresponding log file is written before the log information is not overwritten, and therefore the frequency of the log information writing operation into the log file must be matched with the frequency of the log information copying operation into the buffer.
The invention discloses a log collection method of a third-party application program, which comprises the following steps: calling a sys _ write () function obtained after modifying the system kernel, and copying the log information of each process to a buffer area; and reading the log information of the buffer area, and writing the log information into a corresponding log file according to a distribution rule. The invention utilizes the sys _ write () function to copy the log information, the sys _ write () function is realized by modifying the system kernel call, and the source code of the third-party application program is not required to be modified, so the realization mode of the third-party application program log module is not concerned, the modification mode is simple, the effect is convenient, and the practical value is quite high.
The embodiment of the invention discloses a specific log collection method for a third-party application program, and compared with the previous embodiment, the embodiment further explains and optimizes the technical scheme.
Specifically, the step S1 is a process of calling a sys _ write () function obtained after modifying a system kernel and copying log information of each process to a buffer, and the process further includes:
and calling the sys _ write () function to copy the log information passing through the filtering rule to the buffer.
Wherein the filtering rule is specifically: and filtering the log information meeting a preset program name, a preset process number or a preset file name.
It is understood that the filter rule means a blacklist, in which multiple filter conditions of log information are set, for example, a certain filter condition is in a format of "comm [ pid ]: filename [ fd ]", which means that all log information with program name comm or process number pid filtered out, and output to filename or file descriptor fd is filtered out. The blacklist can be dynamically configured by the user side, so that maintenance personnel can conveniently filter out unnecessary log information at any time, and the workload of analyzing the irrelevant log information is reduced.
In step S2, the distribution rule is generated by reading the configuration file/etc/log _ dispatch _ rules, whose configuration file format is: rule 1, rule 2 target file. The distribution rules include message level and message origin.
Wherein the message levels include: EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO, DEBUG.
It is to be understood that any plurality herein is at least any two.
Wherein the message source comprises a program name and a process number pid.
Correspondingly, the present invention also discloses a log collection system of a third-party application program, as shown in fig. 3, including:
the reading module 01 is used for calling a sys _ write () function obtained after modifying a system kernel and copying log information of each process to a buffer area;
and the distribution module 02 is used for reading the log information of the buffer area and writing the log information into a corresponding log file according to a distribution rule.
The invention utilizes the sys _ write () function to copy the log information, the sys _ write () function is realized by modifying the system kernel call, and the source code of the third-party application program is not required to be modified, so the realization mode of the third-party application program log module is not concerned, the modification mode is simple, the effect is convenient, and the practical value is quite high.
In some specific embodiments, the distribution rules include a message level and a message origin.
In some specific embodiments, the message levels include:
EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO, DEBUG.
In some specific embodiments, the message sources include: program name and process number pid.
In some specific embodiments, the reading module 01 is specifically configured to call the sys _ write () function to copy the log information passing through the filtering rule to the buffer.
In some specific embodiments, the filtering rule is specifically:
and filtering the log information meeting a preset program name, a preset process number or a preset file name.
In some specific embodiments, the distributing module 02 is specifically configured to, in cooperation with the frequency of copying the log information of each process to a buffer, read the log information of the buffer, and write the log information into a corresponding log file according to a distribution rule.
Correspondingly, the invention also discloses a log collection device of the third-party application program, which is shown in fig. 4 and comprises a processor 11 and a memory 12; wherein, the processor 11 implements the following steps when executing the computer program stored in the memory 12:
calling a sys _ write () function obtained after modifying the system kernel, and copying the log information of each process to a buffer area;
and reading the log information of the buffer area, and writing the log information into a corresponding log file according to a distribution rule.
The invention utilizes the sys _ write () function to copy the log information, the sys _ write () function is realized by modifying the system kernel call, and the source code of the third-party application program is not required to be modified, so the realization mode of the third-party application program log module is not concerned, the modification mode is simple, the effect is convenient, and the practical value is quite high.
In some specific embodiments, the distribution rules include a message level and a message origin.
In some specific embodiments, the message levels include:
EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO, DEBUG.
In some specific embodiments, the message sources include: program name and process number pid.
In some specific embodiments, when the processor 11 executes the computer subprogram stored in the memory 12, the following steps may be specifically implemented: and calling the sys _ write () function to copy the log information passing through the filtering rule to the buffer.
In some specific embodiments, the filtering rule is specifically:
and filtering the log information meeting a preset program name, a preset process number or a preset file name.
In some specific embodiments, when the processor 11 executes the computer subprogram stored in the memory 12, the following steps may be specifically implemented: and reading the log information of the buffer area in cooperation with the frequency of copying the log information of each process to the buffer area, and writing the log information into a corresponding log file according to a distribution rule.
Further, the log collecting device in this embodiment may further include:
the input interface 13 is configured to obtain a computer program imported from the outside, store the obtained computer program in the memory 12, and also be configured to obtain various instructions and parameters transmitted by an external terminal device, and transmit the instructions and parameters to the processor 11, so that the processor 11 performs corresponding processing by using the instructions and parameters. In this embodiment, the input interface 13 may specifically include, but is not limited to, a USB interface, a serial interface, a voice input interface, a fingerprint input interface, a hard disk reading interface, and the like.
And an output interface 14, configured to output various data generated by the processor 11 to a terminal device connected thereto, so that other terminal devices connected to the output interface 14 can acquire various data generated by the processor 11. In this embodiment, the output interface 14 may specifically include, but is not limited to, a USB interface, a serial interface, and the like.
A communication unit 15 for establishing a remote communication connection between the log collection device and the external server so that the log collection device can mount the image file into the external server. In this embodiment, the communication unit 15 may specifically include, but is not limited to, a remote communication unit based on a wireless communication technology or a wired communication technology.
And the keyboard 16 is used for acquiring various parameter data or instructions input by a user through real-time key cap knocking.
And the display 17 is used for displaying relevant information of the log collection process in real time so that a user can know the collection condition of the current log information in time.
The mouse 18 may be used to assist the user in entering data and to simplify the user's operation.
Further, embodiments of the present application also disclose a computer storage medium, where the computer storage medium includes Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable hard disk, CD-ROM, or any other form of storage medium known in the art. A computer storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:
calling a sys _ write () function obtained after modifying the system kernel, and copying the log information of each process to a buffer area;
and reading the log information of the buffer area, and writing the log information into a corresponding log file according to a distribution rule.
The invention utilizes the sys _ write () function to copy the log information, the sys _ write () function is realized by modifying the system kernel call, and the source code of the third-party application program is not required to be modified, so the realization mode of the third-party application program log module is not concerned, the modification mode is simple, the effect is convenient, and the practical value is quite high.
In some specific embodiments, the distribution rules include a message level and a message origin.
In some specific embodiments, the message levels include:
EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO, DEBUG.
In some specific embodiments, the message sources include: program name and process number pid.
In some specific embodiments, the computer subprogram stored in the computer storage medium, when executed by the processor, may specifically implement the following steps: and calling the sys _ write () function to copy the log information passing through the filtering rule to the buffer.
In some specific embodiments, the filtering rule is specifically:
and filtering the log information meeting a preset program name, a preset process number or a preset file name.
In some specific embodiments, the computer subprogram stored in the computer storage medium, when executed by the processor, may specifically implement the following steps: and reading the log information of the buffer area in cooperation with the frequency of copying the log information of each process to the buffer area, and writing the log information into a corresponding log file according to a distribution rule.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The method, the system, the device and the storage medium for collecting the log of the third-party application provided by the invention are described in detail, and a specific example is applied in the text to explain the principle and the implementation of the invention, and the description of the embodiment is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.
Claims (9)
1. A log collection method for a third-party application program is characterized by comprising the following steps:
calling a sys _ write () function obtained after modifying the system kernel to copy the log information of each process to a buffer area;
and reading the log information of the buffer area in cooperation with the frequency of copying the log information of each process to the buffer area, and writing the log information into a corresponding log file according to a distribution rule.
2. The log collection method of claim 1, wherein the distribution rules include message level and message origin.
3. The log collection method of claim 2, wherein the message level comprises:
EMERG, ALERT, CRIT, ERR, WARNING, NOTICE, INFO, DEBUG.
4. The log collection method of claim 2, wherein the message source comprises:
program name and process number pid.
5. The log collection method of claim 1, wherein the calling a sys _ write () function obtained after modifying a system kernel copies log information of each process to the buffer, further comprising:
and calling the sys _ write () function to copy the log information passing through the filtering rule to the buffer.
6. The log collection method according to claim 5, wherein the filtering rule is specifically:
and filtering the log information meeting a preset program name, a preset process number or a preset file name.
7. A log collection system for a third party application, comprising:
the reading module is used for calling a sys _ write () function obtained after the system kernel is modified so as to copy the log information of each process to the buffer area;
and the distribution module is used for reading the log information of the buffer area in cooperation with the frequency of copying the log information of each process to the buffer area, and writing the log information into a corresponding log file according to a distribution rule.
8. A log collection apparatus for a third party application, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the log collection method of the third party application as claimed in any one of claims 1 to 6 when executing the computer program.
9. A storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps of the log collection method of a third party application according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910286400.6A CN110008103B (en) | 2019-04-10 | 2019-04-10 | Log collection method, system, device and storage medium for third-party application program |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910286400.6A CN110008103B (en) | 2019-04-10 | 2019-04-10 | Log collection method, system, device and storage medium for third-party application program |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110008103A CN110008103A (en) | 2019-07-12 |
| CN110008103B true CN110008103B (en) | 2020-11-10 |
Family
ID=67170878
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910286400.6A Active CN110008103B (en) | 2019-04-10 | 2019-04-10 | Log collection method, system, device and storage medium for third-party application program |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110008103B (en) |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106326355B (en) * | 2016-08-09 | 2019-10-18 | 武汉深之度科技有限公司 | Log processing method and device in a kind of LFS system |
| CN109347899B (en) * | 2018-08-22 | 2022-03-25 | 北京百度网讯科技有限公司 | Method for writing log data in distributed storage system |
| CN109388538B (en) * | 2018-09-13 | 2020-12-08 | 西安交通大学 | Kernel-based file operation behavior monitoring method and device |
| CN109344034A (en) * | 2018-09-29 | 2019-02-15 | 郑州云海信息技术有限公司 | A kind of method and apparatus for managing log |
-
2019
- 2019-04-10 CN CN201910286400.6A patent/CN110008103B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN110008103A (en) | 2019-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110661659B (en) | Alarm method, device and system and electronic equipment | |
| CN109739727B (en) | Service monitoring method and device in micro-service architecture | |
| CN107704360B (en) | Monitoring data processing method, equipment, server and storage medium | |
| KR101743191B1 (en) | Application program management method and apparatus, server, terminal device, program, and recording medium | |
| CN112311617A (en) | Configured data monitoring and alarming method and system | |
| CN112256542B (en) | eBPF-based micro-service system performance detection method, device and system | |
| CN110019239B (en) | Storage method and device of reported data, electronic equipment and storage medium | |
| CN113553310B (en) | Data acquisition method and device, storage medium and electronic equipment | |
| CN113704790A (en) | Abnormal log information summarizing method and computer equipment | |
| CN111367760A (en) | Log collection method and device, computer equipment and storage medium | |
| CN111782728A (en) | Data synchronization method, device, electronic equipment and medium | |
| CN110134538B (en) | Method, device, medium and electronic equipment for quickly positioning problem log | |
| CN110941632A (en) | Database auditing method, device and equipment | |
| CN110008103B (en) | Log collection method, system, device and storage medium for third-party application program | |
| CN111782431A (en) | Exception processing method, exception processing device, terminal and storage medium | |
| KR20170122874A (en) | Apparatus for managing log of application based on data distribution service | |
| CN115509790A (en) | Method and device for acquiring abnormal information, storage medium and electronic device | |
| CN116028479A (en) | Data reconciliation system, method, equipment and storage medium | |
| CN115455059A (en) | Method, device and related medium for analyzing user behavior based on underlying data | |
| CN112650613B (en) | Error information processing method and device, electronic equipment and storage medium | |
| CN112685370B (en) | Log collection method, device, equipment and medium | |
| CN113392005A (en) | Large file processing test method and system | |
| CN114020565A (en) | Intelligent log collection processing method and device, electronic equipment and storage medium | |
| CN113407415A (en) | Log management method and device of intelligent terminal | |
| CN108829563B (en) | Alarm method and alarm device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |