CN111176987A - Method and device for uniformly outputting front-end log, computer equipment and storage medium - Google Patents
Method and device for uniformly outputting front-end log, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111176987A CN111176987A CN201911315388.3A CN201911315388A CN111176987A CN 111176987 A CN111176987 A CN 111176987A CN 201911315388 A CN201911315388 A CN 201911315388A CN 111176987 A CN111176987 A CN 111176987A
- Authority
- CN
- China
- Prior art keywords
- log
- logs
- request
- outputting
- label
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Prevention of errors by analysis, debugging or testing of software
- G06F11/362—Debugging of software
- G06F11/3636—Debugging of software by tracing the execution of the program
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
- G06F11/3068—Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data format conversion
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1805—Append-only file systems, e.g. using logs or journals to store data
- G06F16/1815—Journaling file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Computer Hardware Design (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention relates to a method and a device for uniformly outputting front-end logs, computer equipment and a storage medium, wherein the method comprises the following steps: monitoring and acquiring a front-end request in the development and debugging process; generating a log file in an htm format correspondingly according to a front-end request, wherein the log file comprises a front-end log of a front-end request event; and adding corresponding labels to different front-end logs and outputting log files. According to the invention, the front-end request is monitored and acquired in the development and debugging process, the htm-format log file is correspondingly generated according to the front-end request, corresponding labels are added to different front-end logs after the front-end log is generated, and the front-end logs are uniformly managed through the different labels, so that the high-efficiency management of the front-end logs can be realized, and the project development efficiency is further improved.
Description
Technical Field
The present invention relates to front-end log management, and more particularly, to a method, an apparatus, a computer device, and a storage medium for uniformly outputting front-end logs.
Background
In programming, the log is a good thing, so that the running condition of the code is often tracked, and the log recording is helpful for maintaining and managing the current project. Logs are generally divided into two categories: service logs and exception logs, the use of logs can achieve the following goals: recording and monitoring the program running condition; the operating state inside the program can be understood in detail as necessary.
In the project development process, in order to facilitate better development, the problem occurrence point can be found by checking the front-end log and checking what the output data is, but the output of the current front-end log is messy, the query of a developer is laborious, the development efficiency is influenced, and the problem cannot be solved quickly.
Disclosure of Invention
The invention aims to overcome the defects of the prior art and provides a method, a device, computer equipment and a storage medium for uniformly outputting front-end logs so as to uniformly and efficiently manage the front-end logs.
In a first aspect, the present invention provides a method for uniformly outputting front-end logs, including the following steps:
monitoring and acquiring a front-end request in the development and debugging process;
generating a log file in an htm format correspondingly according to a front-end request, wherein the log file comprises a front-end log of a front-end request event;
and adding corresponding labels to different front-end logs and outputting log files.
In a second aspect, the present invention further provides a device for uniformly outputting front-end logs, including:
the request acquisition unit is used for monitoring and acquiring a front-end request in the development and debugging process;
the log generating unit is used for correspondingly generating a log file in an htm format according to the front-end request, wherein the log file comprises a front-end log of a front-end request event;
and the label output unit is used for adding corresponding labels to different front-end logs and outputting log files.
In a third aspect, the present invention further provides a computer device, where the computer device includes a memory and a processor, where the memory stores a computer program, and the processor implements the method for unified output of front-end logs as described above when executing the computer program.
In a fourth aspect, the present invention further provides a storage medium storing a computer program, which when executed by a processor can implement the method for unified output of front-end logs as described above.
Compared with the prior art, the invention has the beneficial effects that: according to the invention, the front-end request is monitored and acquired in the development and debugging process, the htm-format log file is correspondingly generated according to the front-end request, corresponding labels are added to different front-end logs after the front-end log is generated, and the front-end logs are uniformly managed through the different labels, so that the high-efficiency management of the front-end logs can be realized, and the project development efficiency is further improved.
The invention is further described below with reference to the accompanying drawings and specific embodiments.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic view of an application scenario of a method for uniformly outputting a front-end log according to an embodiment of the present invention;
fig. 2 is a flowchart illustrating a method for uniformly outputting a front-end log according to an embodiment of the present invention;
FIG. 3 is a schematic block diagram of an apparatus for unified output of front-end logs according to an embodiment of the present invention;
fig. 4 is a schematic block diagram of a log generating unit of an apparatus for uniformly outputting front-end logs according to an embodiment of the present invention;
fig. 5 is a schematic block diagram of a tag output unit of an apparatus for uniformly outputting a front-end log according to an embodiment of the present invention;
FIG. 6 is a schematic block diagram of a computer device provided by 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 some, not all, embodiments of the present invention. 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.
It will be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It is also to be understood that the terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the specification of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
It should be further understood that the term "and/or" as used in this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
Referring to fig. 1 and fig. 2, fig. 1 is a schematic view of an application scenario of a method for uniformly outputting a front-end log according to an embodiment of the present invention. Fig. 2 is a schematic flowchart of a method for uniformly outputting a front-end log according to an embodiment of the present invention. The method for uniformly outputting the front-end logs is applied to a server, the server and a terminal perform data interaction to obtain a front-end request of the terminal, log files in an htm format are correspondingly generated according to the front-end request, corresponding labels are added to different front-end logs, and the log files are output, so that the front-end logs are uniformly managed.
Fig. 2 is a flowchart illustrating a method for uniformly outputting a front-end log according to an embodiment of the present invention. As shown in fig. 2, the method includes the following steps S110 to S130.
And S110, monitoring and acquiring a front-end request in the development and debugging process.
In this embodiment, in the project development process, development and debugging are indispensable processes, and in this process, if a front-end request is received, a front-end request event is triggered, so as to trigger generation of a corresponding front-end log. Therefore, the front-end request is monitored, and when the front-end request is monitored, the specific information of the front-end request is acquired.
And S120, generating a log file in an htm format correspondingly according to the front-end request, wherein the log file comprises a front-end log of the front-end request event.
In the present embodiment, an Html (Hyper Text Markup Language) file is a hypertext Markup Language file. The Html file structure includes a header (Head), a Body section (Body). The Head label is the webpage information, and the Body label is the specific content to be displayed on the webpage. The HTML tag/label can have different attribute items for controlling the content in the label to display different effects.
The Html-format log file refers to a log file of a specific text format, which is given a suffix of Html, and resembles a txt file. After the front-end request is obtained, an interface is called according to the front-end request to call a local notebook or a Notepad editor (text editor) to generate a corresponding log file in an Html format, similar to the text input into the text editor, the log file in the Html format comprises front-end logs of all front-end request events, and when data is requested from a server according to the front-end request, the front-end log of the current request event can be dynamically generated.
In one embodiment, step S120 includes step S121.
And S121, calling a local text editor according to the front-end request to generate a log file.
In this embodiment, the text editor may be notebook software already installed locally or a Notepad editor, and generates a log file in the Html format by inputting corresponding information into the text editor.
And S130, adding corresponding labels for different front-end logs, and outputting log files.
In this embodiment, the log file includes all front-end logs, and the present invention adds tags to different front-end logs, where a tag is a tag of a front-end log, for example, an < hr > title </hr > is a title tag, and can play a role of thickening a title, and a < p > paragraph </p > is a paragraph tag, and a line is monopolized in a browser.
In one embodiment, step S130 includes step S131.
S131, obtaining the importance degree information of the front end log, and adding importance degree labels for identifying different importance degrees to the corresponding front end log.
In this embodiment, the importance degree of the front-end log is divided into the following four levels: important, abnormal, erroneous, normal. Specifically, for the front-end log with the importance degree of error, red is used as an importance degree label to mark the corresponding front-end log; for the front-end log with abnormal importance degree, marking the corresponding front-end log by using blue as an importance degree label; for the front-end logs with important degrees, green is used as an importance degree label to mark the corresponding front-end logs; for the front-end logs with common importance degrees, black is used as an importance degree label to mark the corresponding front-end logs.
For example, the importance level of a request event of data requested by an interface is important, and at this time, a corresponding importance level tag needs to be added to the request data and a front-end log, the data and the log after the request is successful are marked by green, and the front-end log output by page console.
Further, for the front-end log with high importance, a label with high (obvious) recognition degree is added, for example, the label is set to be a red font or background color emphasis, and the like.
In another embodiment, step S130 includes step S132.
S132, acquiring the actual output time of the front-end log, and adding an output time tag for identifying the actual output time into the corresponding front-end log.
In this embodiment, the front-end log may have an actual output time point when being output, the actual output time information of the front-end log is added to the tag as an output time tag, the output time tag includes the actual output time information of the front-end log, the specific output time of the front-end log can be known according to the output time tag, and synchronization can be performed in time according to the output time tag.
In another embodiment, step S130 includes step S133.
S133, front-end logs thrown by the same abnormal events are obtained, and the front-end logs are merged and added with the same abnormal event labels.
In this embodiment, front end logs that the same abnormal event needs to be thrown are merged, where the so-called abnormality includes no response of the interface or no call of the interface, the corresponding front end logs are put together uniformly, and further merged and output, and then an abnormal event tag is added to the merged front end logs, so as to implement uniform management of the abnormal time.
The label can be an hr label, the hr label is a title label, the titles of all front-end logs can be replaced by interfaces, and the title can be named by what interface when the request is made, for example, if the interface defined by the back-end is userlist, the log label can be < hr > userlist: </hr >, so that query in the future is facilitated.
In another embodiment, step S130 includes any combination of at least two of the above steps S131 to S133, and specifically, steps S131 to S133 may be included at the same time, and the description about steps S131 to S133 is not repeated here.
According to the invention, the front-end request is monitored and acquired in the development and debugging process, the htm-format log file is correspondingly generated according to the front-end request, corresponding labels are added to different front-end logs after the front-end log is generated, and the front-end logs are uniformly managed through the different labels, so that the high-efficiency management of the front-end logs can be realized, and the project development efficiency is further improved.
Fig. 3 is a schematic block diagram of an apparatus for uniformly outputting a front-end log according to an embodiment of the present invention. As shown in fig. 3, the present invention also provides a device for uniformly outputting front-end logs, corresponding to the above method for uniformly outputting front-end logs. The device for unified output of the front-end log comprises a unit for executing the method for unified output of the front-end log, and can be configured in a desktop computer, a tablet computer, a portable computer, and the like. Specifically, referring to fig. 3, the apparatus for uniformly outputting the front-end log includes a request obtaining unit 10, a log generating unit 20, and a tag outputting unit 30.
And the request acquisition unit 10 is used for monitoring and acquiring the front-end request in the development and debugging process.
In this embodiment, in the project development process, development and debugging are indispensable processes, and in this process, if a front-end request is received, a front-end request event is triggered, so as to trigger generation of a corresponding front-end log. Therefore, the front-end request is monitored, and when the front-end request is monitored, the specific information of the front-end request is acquired.
And the log generating unit 20 is configured to generate a log file in an htm format according to the front-end request, where the log file includes a front-end log of the front-end request event.
In the present embodiment, an Html (Hyper Text Markup Language) file is a hypertext Markup Language file. The Html file structure includes a header (Head), a Body section (Body). The Head label is the webpage information, and the Body label is the specific content to be displayed on the webpage. The HTML tag/label can have different attribute items for controlling the content in the label to display different effects.
The Html-format log file refers to a log file of a specific text format, which is given a suffix of Html, and resembles a txt file. After the front-end request is obtained, an interface is called according to the front-end request to call a local notebook or a Notepad editor (text editor) to generate a corresponding log file in an Html format, similar to the text input into the text editor, the log file in the Html format comprises front-end logs of all front-end request events, and when data is requested from a server according to the front-end request, the front-end log of the current request event can be dynamically generated.
In an embodiment, as shown in fig. 4, the log generating unit 20 includes a log generating module 21. The log generating module 21 is configured to invoke a local text editor according to the front-end request, and generate a log file.
In this embodiment, the text editor may be notebook software already installed locally or a Notepad editor, and generates a log file in the Html format by inputting corresponding information into the text editor.
And the label output unit 30 is used for adding corresponding labels to different front-end logs and outputting log files.
In this embodiment, the log file includes all front-end logs, and the present invention adds tags to different front-end logs, where a tag is a tag of a front-end log, for example, an < hr > title </hr > is a title tag, and can play a role of thickening a title, and a < p > paragraph </p > is a paragraph tag, and a line is monopolized in a browser.
In one embodiment, as shown in fig. 5, the tag output unit 30 includes a first tag module 31, a second tag module 32, and a third tag module 33.
The first label module 31 is configured to obtain importance information of the front end log, and add importance labels for identifying different importance levels to the corresponding front end log.
In this embodiment, the importance degree of the front-end log is divided into the following four levels: important, abnormal, erroneous, normal. Specifically, for the front-end log with the importance degree of error, red is used as an importance degree label to mark the corresponding front-end log; for the front-end log with abnormal importance degree, marking the corresponding front-end log by using blue as an importance degree label; for the front-end logs with important degrees, green is used as an importance degree label to mark the corresponding front-end logs; for the front-end logs with common importance degrees, black is used as an importance degree label to mark the corresponding front-end logs.
For example, the importance level of a request event of data requested by an interface is important, and at this time, a corresponding importance level tag needs to be added to the request data and a front-end log, the data and the log after the request is successful are marked by green, and the front-end log output by page console.
Further, for the front-end log with high importance, a label with high (obvious) recognition degree is added, for example, the label is set to be a red font or background color emphasis, and the like.
The second tag module 32 is configured to obtain an actual output time of the front-end log, and add an output time tag for identifying the actual output time to the corresponding front-end log.
In this embodiment, the front-end log may have an actual output time point when being output, the actual output time information of the front-end log is added to the tag as an output time tag, the output time tag includes the actual output time information of the front-end log, the specific output time of the front-end log can be known according to the output time tag, and synchronization can be performed in time according to the output time tag.
The third tag module 33 is configured to obtain front-end logs thrown by the same abnormal event, merge the front-end logs, and add the same abnormal event tag.
In this embodiment, front end logs that the same abnormal event needs to be thrown are merged, where the so-called abnormality includes no response of the interface or no call of the interface, the corresponding front end logs are put together uniformly, and further merged and output, and then an abnormal event tag is added to the merged front end logs, so as to implement uniform management of the abnormal time.
The label can be an hr label, the hr label is a title label, the titles of all front-end logs can be replaced by interfaces, and the title can be named by what interface when the request is made, for example, if the interface defined by the back-end is userlist, the log label can be < hr > userlist: </hr >, so that query in the future is facilitated.
According to the invention, the front-end request is monitored and acquired in the development and debugging process, the htm-format log file is correspondingly generated according to the front-end request, corresponding labels are added to different front-end logs after the front-end log is generated, and the front-end logs are uniformly managed through the different labels, so that the high-efficiency management of the front-end logs can be realized, and the project development efficiency is further improved.
It should be noted that, as can be clearly understood by those skilled in the art, the specific implementation process of the apparatus for uniformly outputting the front end log and each unit may refer to the corresponding description in the foregoing method embodiment, and for convenience and brevity of description, no further description is provided herein.
Referring to fig. 6, fig. 6 is a schematic block diagram of a computer device according to an embodiment of the present application. The computer device 500 may be a terminal or a server, where the terminal may be an electronic device with a communication function, such as a smart phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant, and a wearable device. The server may be an independent server or a server cluster composed of a plurality of servers.
Referring to fig. 6, the computer device 500 includes a processor 502, memory, and a network interface 505 connected by a system bus 501, where the memory may include a non-volatile storage medium 503 and an internal memory 504.
The non-volatile storage medium 503 may store an operating system 5031 and a computer program 5032. The computer programs 5032 include program instructions that, when executed, cause the processor 502 to perform a method for unified output of front end logs.
The processor 502 is used to provide computing and control capabilities to support the operation of the overall computer device 500.
The internal memory 504 provides an environment for the operation of the computer program 5032 in the non-volatile storage medium 503, and when the computer program 5032 is executed by the processor 502, the processor 502 can be enabled to execute a method for unified output of the front-end log.
The network interface 505 is used for network communication with other devices. Those skilled in the art will appreciate that the configuration shown in fig. 6 is a block diagram of only a portion of the configuration associated with the present application and does not constitute a limitation of the computer device 500 to which the present application may be applied, and that a particular computer device 500 may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
Wherein the processor 502 is adapted to run a computer program 5032 stored in the memory.
It should be understood that, in the embodiment of the present Application, the Processor 502 may be a Central Processing Unit (CPU), and the Processor 502 may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field-Programmable Gate arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. Wherein a general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
It will be understood by those skilled in the art that all or part of the flow of the method implementing the above embodiments may be implemented by a computer program instructing associated hardware. The computer program includes program instructions, and the computer program may be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the flow steps of the embodiments of the method described above.
Accordingly, the present invention also provides a storage medium. The storage medium may be a computer-readable storage medium.
The storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a magnetic disk, or an optical disk, which can store various computer readable storage media.
Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the 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 invention.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative. For example, the division of each unit is only one logic function division, and there may be another division manner in actual implementation. For example, various elements or components may be combined or may be integrated into another system, or some features may be omitted, or not implemented.
The steps in the method of the embodiment of the invention can be sequentially adjusted, combined and deleted according to actual needs. The units in the device of the embodiment of the invention can be merged, divided and deleted according to actual needs. In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a storage medium. Based on such understanding, the technical solution of the present invention essentially or partially contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a terminal, or a network device) to execute all or part of the steps of the method according to the embodiments of the present invention.
While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art within the technical scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.
Claims (10)
1. A method for uniformly outputting front-end logs is characterized by comprising the following steps:
monitoring and acquiring a front-end request in the development and debugging process;
generating a log file in an htm format correspondingly according to a front-end request, wherein the log file comprises a front-end log of a front-end request event;
and adding corresponding labels to different front-end logs and outputting log files.
2. The method for uniformly outputting front-end logs according to claim 1, wherein the step of correspondingly generating the html-format log file according to the front-end request comprises:
and calling a local text editor according to the front-end request to generate a log file.
3. The method for uniformly outputting front-end logs according to claim 1, wherein the step of adding corresponding labels to different front-end logs and outputting log files comprises:
and acquiring the importance degree information of the front-end log, and adding importance degree labels for identifying different importance degrees to the corresponding front-end log.
4. The method for uniformly outputting front-end logs according to claim 1, wherein the step of adding corresponding labels to different front-end logs and outputting log files comprises:
and acquiring the actual output time of the front-end log, and adding an output time tag for identifying the actual output time into the corresponding front-end log.
5. The method for uniformly outputting front-end logs according to claim 1, wherein the step of adding corresponding labels to different front-end logs and outputting log files comprises:
and acquiring front-end logs thrown by the same abnormal event, merging the front-end logs, and adding the same abnormal event label.
6. A device for uniformly outputting front-end logs is characterized by comprising:
the request acquisition unit is used for monitoring and acquiring a front-end request in the development and debugging process;
the log generating unit is used for correspondingly generating a log file in an htm format according to the front-end request, wherein the log file comprises a front-end log of a front-end request event;
and the label output unit is used for adding corresponding labels to different front-end logs and outputting log files.
7. The apparatus for unified output of front-end log according to claim 6, wherein the log generating unit comprises a log generating module, configured to invoke a local text editor according to a front-end request to generate a log file.
8. The apparatus for unified output of front-end log according to claim 6, wherein the tag output unit comprises a first tag module, a second tag module and a third tag module;
the first label module is used for acquiring importance degree information of the front-end log and adding importance degree labels for identifying different importance degrees to the corresponding front-end log;
the second label module is used for acquiring the actual output time of the front-end log and adding an output time label for marking the actual output time into the corresponding front-end log;
and the third label module is used for acquiring the front-end logs thrown by the same abnormal event, merging the front-end logs and adding the same abnormal event label.
9. A computer device, characterized in that the computer device comprises a memory on which a computer program is stored and a processor which, when executing the computer program, implements the method for front-end log unified output according to any of claims 1 to 5.
10. A storage medium, characterized in that the storage medium stores a computer program which, when executed by a processor, can implement the method for unified output of front-end logs according to any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911315388.3A CN111176987A (en) | 2019-12-18 | 2019-12-18 | Method and device for uniformly outputting front-end log, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911315388.3A CN111176987A (en) | 2019-12-18 | 2019-12-18 | Method and device for uniformly outputting front-end log, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111176987A true CN111176987A (en) | 2020-05-19 |
Family
ID=70653940
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911315388.3A Pending CN111176987A (en) | 2019-12-18 | 2019-12-18 | Method and device for uniformly outputting front-end log, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111176987A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113190399A (en) * | 2021-03-30 | 2021-07-30 | 深圳市广和通无线股份有限公司 | Log storage method and device, computer equipment and storage medium |
| CN114650236A (en) * | 2020-12-17 | 2022-06-21 | 中移(苏州)软件技术有限公司 | Log processing method and device and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2001101036A (en) * | 1999-09-30 | 2001-04-13 | Hitachi Software Eng Co Ltd | Method for storing and using log information |
| US9251013B1 (en) * | 2014-09-30 | 2016-02-02 | Bertram Capital Management, Llc | Social log file collaboration and annotation |
| CN107678933A (en) * | 2017-09-28 | 2018-02-09 | 中国平安人寿保险股份有限公司 | Daily record generation management method, device, equipment and computer-readable recording medium |
| CN109062762A (en) * | 2018-07-26 | 2018-12-21 | 浙江数链科技有限公司 | Formatted log method for pushing and device |
| CN110427299A (en) * | 2019-07-19 | 2019-11-08 | 腾讯科技（深圳）有限公司 | Log processing method, relevant device and the system of micro services system application |
-
2019
- 2019-12-18 CN CN201911315388.3A patent/CN111176987A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2001101036A (en) * | 1999-09-30 | 2001-04-13 | Hitachi Software Eng Co Ltd | Method for storing and using log information |
| US9251013B1 (en) * | 2014-09-30 | 2016-02-02 | Bertram Capital Management, Llc | Social log file collaboration and annotation |
| CN107678933A (en) * | 2017-09-28 | 2018-02-09 | 中国平安人寿保险股份有限公司 | Daily record generation management method, device, equipment and computer-readable recording medium |
| CN109062762A (en) * | 2018-07-26 | 2018-12-21 | 浙江数链科技有限公司 | Formatted log method for pushing and device |
| CN110427299A (en) * | 2019-07-19 | 2019-11-08 | 腾讯科技（深圳）有限公司 | Log processing method, relevant device and the system of micro services system application |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114650236A (en) * | 2020-12-17 | 2022-06-21 | 中移(苏州)软件技术有限公司 | Log processing method and device and storage medium |
| CN113190399A (en) * | 2021-03-30 | 2021-07-30 | 深圳市广和通无线股份有限公司 | Log storage method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11783114B2 (en) | Techniques for view capture and storage for mobile applications | |
| US8468391B2 (en) | Utilizing log event ontology to deliver user role specific solutions for problem determination | |
| CN107562556B (en) | Failure recovery method, recovery device and storage medium | |
| CN112527414B (en) | Front-end-based data processing method, device, equipment and storage medium | |
| US20090106594A1 (en) | Method and Device for Log Events Processing | |
| WO2019127844A1 (en) | Method and device for generating electronic report, computer equipment, and storage medium | |
| MX2008011058A (en) | Rss data-processing object. | |
| CN111078717A (en) | Database and cache consistency synchronization method and device, computer equipment and storage medium | |
| US10951509B1 (en) | Methods, systems, and computer readable media for providing intent-driven microapps for execution on communications network testing devices | |
| CN110489310B (en) | Method and device for recording user operation, storage medium and computer equipment | |
| CN110995539A (en) | Business system monitoring method and device and computer equipment | |
| CN112130944A (en) | Page abnormity detection method, device, equipment and storage medium | |
| CN107277019A (en) | Data clear text acquisition methods, device, electric terminal and readable storage medium storing program for executing | |
| WO2019109519A1 (en) | Service rule management method, apparatus and device, and computer-readable storage medium | |
| CN112817831A (en) | Application performance monitoring method, device, computer system and readable storage medium | |
| CN111176987A (en) | Method and device for uniformly outputting front-end log, computer equipment and storage medium | |
| CN113419738A (en) | Interface document generation method and device and interface management equipment | |
| CN111444453B (en) | Page return data processing method and device | |
| CN112817922A (en) | Log dynamic printing method and device, computer equipment and storage medium | |
| CN114253593A (en) | Application program information feedback method, device, terminal device and storage medium | |
| US9542182B2 (en) | Standardization of variable names in an integrated development environment | |
| CN111061613A (en) | Front-end abnormity monitoring method and device and computer equipment | |
| CN111176944A (en) | Block chain intelligent contract calling record analysis method, device, terminal and storage medium | |
| CN113064807A (en) | Log diagnosis method and device | |
| CN115543807B (en) | An automated regression testing method, apparatus, computer equipment, and storage medium |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200519 |