CN114443424A - Front-end log processing method, device and system - Google Patents
Front-end log processing method, device and system Download PDFInfo
- Publication number
- CN114443424A CN114443424A CN202111680689.3A CN202111680689A CN114443424A CN 114443424 A CN114443424 A CN 114443424A CN 202111680689 A CN202111680689 A CN 202111680689A CN 114443424 A CN114443424 A CN 114443424A
- Authority
- CN
- China
- Prior art keywords
- end log
- database
- log
- computer
- web application
- 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; CALCULATING OR 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/17—Details of further file system functions
- G06F16/172—Caching, prefetching or hoarding of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR 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
Abstract
The application discloses a method, a device and a system for processing a front-end log, which are used for improving the processing efficiency of the front-end log and saving system resources. The method comprises the following steps: monitoring the running state of a web application program of a webpage in real time, and generating a front-end log according to the running state; the front end log is used for representing problems occurring in the running process of the web application program; storing the front end log in a database; the front end log is sent to an application server of the web application.
Description
Technical Field
The present application relates to the field of computer front-end development technologies, and in particular, to a method, an apparatus, and a system for processing a front-end log.
Background
In the development of current web page (web) applications, most of log monitoring is mainly applied to backend services. With the continuous improvement of the front-end service, the performance and experience requirements of the website are continuously improved, and the log monitoring of the front-end service becomes more and more important in order to ensure the use experience of the user. And generating a front-end log which can be used for timely fault analysis and troubleshooting and solving of problems by operation and maintenance personnel so as to continuously optimize the front-end service of the web application program and improve the use experience of users. Therefore, how to generate, store and transmit the front-end log becomes important.
Disclosure of Invention
The exemplary embodiments of the present application provide a method, an apparatus, and a system for processing a front-end log, so as to improve the processing efficiency of the front-end log.
In a first aspect, an embodiment of the present application provides a method for processing a front-end log, including:
monitoring the running state of a web application program of a webpage in real time, and generating a front-end log according to the running state; the front end log is used for representing problems occurring in the running process of the web application program;
storing the front end log in a database;
sending the front end log to an application server of the web application.
Based on the scheme, the client device generates and stores the front-end log in a real-time monitoring mode of the web application program so as to ensure the integrity of the front-end log. In addition, the client can send the stored front-end log to the application server, so that operation and maintenance personnel can conveniently check the front-end log, and the processing efficiency of the front-end log is improved.
In some embodiments, the front end log comprises at least one of:
a timestamp of an occurrence of a problem during the running of the web application, an identifier for identifying the problem, a rating of the problem, or descriptive information of the problem.
In some embodiments, the generating a front-end log according to the operating state includes:
when the running of the web application program is detected to have an error, generating the front-end log; alternatively, the first and second electrodes may be,
and responding to the operation of generating the front-end log triggered by a user, and generating the front-end log.
In some embodiments, the method further comprises:
deleting the front end log stored in the database after a first set time length.
In some embodiments, said storing said front end log in a database comprises:
after generating a second set duration of the front-end log, storing the front-end log in a database; the database is an IndexDB database.
In some embodiments, the sending the front end log to an application server of the web application includes:
and sending the front end log stored in the database in the set period to the application server at set intervals.
In a second aspect, an embodiment of the present application provides another method for processing a terminal log, including:
receiving a front-end log from a client device, and storing the front-end log according to a problem indicated by the front-end log.
In some embodiments, the front end log comprises at least one of:
a timestamp of an occurrence of a problem during the running of the web application, an identifier for identifying the problem, a rating of the problem, or descriptive information of the problem.
In a third aspect, an embodiment of the present application provides a front-end log processing apparatus, including:
the processing unit is used for monitoring the running state of the web application program of the webpage in real time and generating a front-end log according to the running state; the front end log is used for representing problems occurring in the running process of the web application program;
the processing unit is further used for storing the front-end log into a database;
and the communication unit is used for sending the front-end log to an application server of the web application program.
In some embodiments, the front end log comprises at least one of:
a timestamp of an occurrence of a problem during the running of the web application, an identifier for identifying the problem, a rating of the problem, or descriptive information of the problem.
In some embodiments, the processing unit is specifically configured to:
when the running of the web application program is detected to have an error, generating the front-end log; alternatively, the first and second electrodes may be,
and responding to the operation of generating the front-end log triggered by a user, and generating the front-end log.
In some embodiments, the processing unit is further configured to:
deleting the front end log stored in the database after a first set time length.
In some embodiments, the processing unit is specifically configured to:
after generating a second set duration of the front-end log, storing the front-end log in a database; the database is an IndexDB database.
In some embodiments, the communication unit is specifically configured to:
and sending the front end log stored in the database in the set period to the application server at set intervals.
In a fourth aspect, an embodiment of the present application provides another front-end log processing apparatus, including:
a communication unit for receiving a front-end log from a client device;
and the processing unit is used for storing the front end log according to the problem indicated by the front end log.
In some embodiments, the front end log comprises at least one of:
a timestamp of an occurrence of a problem during the running of the web application, an identifier for identifying the problem, a rating of the problem, or descriptive information of the problem.
In a fifth aspect, an embodiment of the present application provides a front-end log processing system, including:
the client device is used for monitoring the running state of the web application program of the webpage in real time and generating a front-end log according to the running state; the front end log is used for representing problems occurring in the running process of the web application program;
the client device is further used for storing the front-end log into a database;
the client device is further used for sending the front-end log to an application server of the web application program;
and the application server is used for receiving the front end log and storing the front end log according to the problem indicated by the front end log.
In some embodiments, the front end log comprises at least one of:
a timestamp of an occurrence of a problem during the running of the web application, an identifier for identifying the problem, a rating of the problem, or descriptive information of the problem.
In some embodiments, when the client device generates the front-end log according to the operating state, the client device is specifically configured to:
when the running of the web application program is detected to have an error, generating the front-end log; alternatively, the first and second electrodes may be,
and responding to the operation of generating the front-end log triggered by a user, and generating the front-end log.
In some embodiments, the client device is further configured to:
deleting the front end log stored in the database after a first set time length.
In some embodiments, the client device, when storing the front end log in the database, is specifically configured to:
after generating a second set duration of the front-end log, storing the front-end log in a database; the database is an IndexDB database.
In some embodiments, the client device, when sending the front end log to the application server of the web application, is specifically configured to:
and sending the front end log stored in the database in the set period to the application server at set intervals.
In a sixth aspect, embodiments of the present application provide an electronic device, which includes a controller and a memory. The memory is used for storing computer-executable instructions, and the controller executes the computer-executable instructions in the memory to perform the operation steps of the method of any one of the possible implementations of the first aspect to the second aspect by using hardware resources in the controller.
In a seventh aspect, the present application provides a computer-readable storage medium having stored therein instructions, which when run on a computer, cause the computer to perform the method of the above-described aspects.
In an eighth aspect, the present application provides a computer program product, which includes computer program code, when executed by a computer, causes the computer to execute the method of the above aspects.
In addition, the beneficial effects of the second aspect to the eighth aspect can be referred to as the beneficial effects of the first aspect, and are not described herein again.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application.
Fig. 1 is a schematic diagram of a front-end log processing system according to an embodiment of the present disclosure;
fig. 2 is a flowchart of a front-end log processing method according to an embodiment of the present disclosure;
fig. 3 is a schematic diagram of an architecture of a Flog according to an embodiment of the present disclosure;
fig. 4 is a flowchart of another front-end log processing method according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a front-end log processing apparatus according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments, but not all embodiments, of the technical solutions of the present application. All other embodiments obtained by a person skilled in the art without any inventive step based on the embodiments described in the present application are within the scope of the protection of the present application.
The terms "first" and "second" in the description and claims of the present application and the above-described drawings are used for distinguishing between different objects and not for describing a particular order. Furthermore, the term "comprises" and any variations thereof, which are intended to cover non-exclusive protection. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements listed, but may alternatively include other steps or elements not listed, or inherent to such process, method, article, or apparatus. The "plurality" in the present application may mean at least two, for example, two, three or more, and the embodiments of the present application are not limited.
In addition, the term "and/or" herein is only one kind of association relationship describing an associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this document generally indicates that the preceding and following related objects are in an "or" relationship unless otherwise specified.
In order to facilitate understanding of the solutions proposed in the present application, first, technical terms related to the embodiments of the present application are briefly described:
(1) the web application program: the web application program is an application program which can be accessed through a webpage, and the application program has the greatest advantages that a user can access the application program only by installing a browser without installing other software, so that the method is very convenient and fast.
(2) Front-end log: the method is used for recording some data in the running process of the web application program, so that operation and maintenance personnel can lock the problem quickly.
(3) IndexEDDB database: is a local database provided by the browser and can be created and operated by web scripts. Allowing storage of large amounts of data, providing a lookup interface, and also enabling the creation of indexes. The IndexedDB database has the following characteristic points:
and storing the key value pair: the IndexEDDB database stores data using an object repository. All types of data can be stored directly in an object repository, and the data is stored in a key-value pair mode.
Asynchronous storage: the IndexDB database does not lock the browser during operation, and the user can still use the browser to perform other operations, which is in contrast to the LocalStorage and other databases, the operation of which is synchronous. Asynchronous storage is designed to prevent the problem of reading and writing a large amount of data and slowing down the display of a web page.
Supporting the transaction: the IndexDB database supports transactions (transactions), that is, in a series of operation steps, if one step fails, the whole transaction is cancelled, and the database rolls back to the state before the transaction occurs, so that the situation that only a part of data is rewritten does not exist.
Homologous restriction: IndexEDDB databases are subject to isogeny constraints, i.e., each database corresponds to the domain name that it was created for. Any web page can only access the database under the own domain name, but can not access the database across domains.
The storage space is big: the storage space of IndexEDDB database is much larger than that of LocalStorage database, generally not less than 250MB, and has no upper limit.
Support for binary storage: the IndexedDB database may store not only character strings but also binary data.
(4) Front-end visualization (echart): an open source visual library realized by JavaScript can run in any terminal equipment and is compatible with most browsers. The echart bottom layer relies on the vector database ZRender and can provide intuitive, interactive rich and customizable data visualization icons. echart may provide conventional line graphs, histograms, scatter plots, pie charts, and K-line graphs, etc., and may also provide box plots for statistics, maps, thermodynamic diagrams, or line graphs, etc., for visualization of geographic data.
(5) Flog: a log generator, which can also be called a log generating architecture, can generate various types of logs according to the user-defined configuration of a user.
In order to facilitate understanding of the method for processing the front-end log proposed in the present application, a network architecture related to the present application is first introduced below. For example, referring to fig. 1, a front-end log processing architecture provided for an embodiment of the present application includes a client device and an application server.
The client device shown in fig. 1, which is also referred to as a Terminal device, a Mobile Station (MS), a Mobile Terminal (MT), etc., is a device for providing voice and/or data connectivity to a user, such as a handheld device with a wireless connection function, a vehicle-mounted device, etc. Currently, some examples of terminals are: a Mobile phone (Mobile phone), a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), a wearable Device, a Virtual Reality (VR) Device, an Augmented Reality (AR) Device, a wireless terminal in Industrial Control (Industrial Control), a wireless terminal in unmanned driving (self driving), a wireless terminal in remote surgery (remote medical supply), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety, a wireless terminal in city (smart city), a wireless terminal in smart home (smart home), and the like.
The application server is a background server of the web application program provided by the embodiment of the application. Wherein the web application is installed in the client device. It should be noted that the functions of the application server may be implemented by one server or by a server cluster, which is not limited in the present application, and the functions of the application server are implemented by only one server in fig. 1. The application server may include a processor, a hard disk, a memory, a system bus, etc. for responding to a request from the client device and providing corresponding services. The application server may also be configured to receive a front-end log from the client device.
Optionally, the application server may further be connected to a display device, and is configured to display the received front-end log, so that the operation and maintenance staff can conveniently check the front-end log. Alternatively, the application server may employ echart to display the front-end log.
In the related art, when generating a front-end log, a method generally adopted is as follows: the client device displays a control for generating the log in the display interface, generates the log in response to the operation of the user, and then transmits the generated log to the application server of the web application. In the method, the efficiency of generating the log is low, and the log needs to be stored by frequently calling the API. The embodiment of the application provides a processing method of a front-end log, wherein client equipment monitors the running state of a web application program in real time, generates the front-end log, automatically stores the generated front-end log and sends the front-end log to an application server of the web application program. Therefore, the processing efficiency of the front-end log is improved, and the resources of the client device and the application server are saved.
First, in order to facilitate understanding of the method for processing the front-end log provided in the embodiment of the present application, referring to fig. 2, a flowchart of the method for processing the front-end log provided in the embodiment of the present application specifically includes:
the client device monitors the running state of the web application program in real time and generates a front-end log 201.
The front-end log is generated according to the running state of the web application program and is used for recording problems occurring in the running process of the web application program.
Optionally, the front end log may include one or more of: and (4) timestamp of the problem during the running process of the web application, namely the time when the problem occurs. Issue identifiers, wherein different issue types correspond to different identifiers. For example, the question identifier may include a version. Problem ratings, such as info, warning, error, critical, etc., are used to characterize the level of a problem. Problem description information, since the problem level and the problem identifier cannot represent detailed problem information, a simple description of the problem is required to facilitate the locking of the operation and maintenance personnel and the problem solving.
The client device stores 202 the front end log in a database.
Alternatively, the client device may employ an IndexedDB database. For example, an IndexedDB database may be encapsulated and deployed in a client device. The client device may implement asynchronous storage of the front-end log based on the IndexedDB database. That is, the client device may store the generated front-end log in the IndexedDB database after a set time for generating the front-end log.
The client device sends 203 the front end log to an application server of the web application.
As an alternative, the client may send, to the application server, a front-end log stored in the IndexedDB database every set period.
As another alternative, the client may also send the front-end log stored in the IndexedDB database to the application server in real time.
And 204, the application server receives the front-end log and stores the front-end log according to the problem indicated by the front-end log.
Alternatively, the application server may classify the front end log by a question level or a question identifier included in the front end log, and may store different types of front end logs in different storage spaces.
Based on the scheme, the client device generates and stores the front-end log in a mode of monitoring the web application program in real time so as to ensure the integrity of the front-end log. In addition, the client can send the stored front-end log to the application server, so that operation and maintenance personnel can conveniently check the front-end log, and the processing efficiency of the front-end log is improved.
In some embodiments, the client device may further display a control for generating the front-end log in the display screen when the web application is run, and generate the front-end log in response to a user selecting the control. Or the birthday can be used for recording the problem front-end log when the web application program runs and has a problem. Further, the client device may store the generated front-end log in a database after a set duration of time for generating the front-end log. For example, the client device may employ an IndexDB database to enable asynchronous storage of the front-end log. Therefore, the problem that the client device runs the web application program to delay due to the fact that the front end log is stored to occupy resources of the client device is avoided.
In some embodiments, the client device may further encrypt the front-end log using a pre-configured key and store the encrypted front-end log in a database. Alternatively, the client device may employ the homologously restricted functionality of the indexedDB database to create different domain names for indexedDB databases corresponding to different web applications, thereby ensuring that the web applications cannot access the front-end logs of other web applications across domains. Optionally, in order to save the storage resources of the database, the client device may also delete the front-end log stored in the database at intervals.
Further, after storing the front-end log in the IndexedDB database, the client device may send the front-end log stored in the IndexedDB database for the period of time to the application server at every set period. Or the client device may also send the front-end log stored in the IndexedDB database to the application server in real-time.
As an example, the above method may be implemented by a preconfigured Flog architecture. As an example, the Flog architecture adopted in the present application can refer to the architecture diagram shown in fig. 3. In fig. 3, it is shown that, with the Flog architecture, various parameters in the architecture may be configured and initialized first, and further, an encapsulated IndexedDB database may be deployed in the architecture. The IndexEDDB database may include functions such as front-end log storage, reading, deleting, error monitoring, asynchronous storage, log encryption, and the like. Still further, in the Flog architecture, the front end log stored in the IndexedDB database may be transmitted to the application server. Optionally, the application server may further perform statistical analysis on the received front-end log, and display the front-end log on the display screen in an echart or line graph manner, so as to realize visualization of the front-end log, which is convenient for operation and maintenance personnel to perform problem analysis.
Hereinafter, for convenience of understanding, a process of introducing the Flog architecture and initializing the configuration is described with one specific example.
The method comprises the following steps: the Flog architecture was introduced.
As an alternative, the code source repository may be downloaded and then packed in an npm run built manner. A bundle. js file is generated under the dist folder, and then the downloaded code is introduced through a script tag. As an example, the address of the code source repository may be: https:// gitlab.ctyuncdn.cn/ctyun/flog.
As another alternative, the message may be loaded into the system via an npm install flow, and then used by import.
Step two: initialization is performed and global variables are set.
As an example, the configuration of the attributes may be made in the following manner:
step three: the reading and writing operations of the data are realized by means of an external display API, for example: storage method flog. savelog ():
let obj＝{
content:“Event Source Element:<img src＝http://www.baixx.com/aaa.jpg>”
username:’smile’，
email:’smile@123.com’
}
alternatively, the reading method may be: get al Log () flog get Log ById (1).
Step four: when a user reports an error, the locally stored log can be viewed according to a time range and then uploaded to the application server. The Json format can be seen as follows:
{
comment 22 is added in the formula,
content: "this is bar 2",
createTime：“2021-01-07 17:01:59”，
deviceId：“”，
email：“smile@123.com”，
environment：“Mozilla/5.0(Windows NT 10.0；Win64；x64)”
localtionUrl:“file:///D:/demo/test/index.html”，
logType:“error”，
username：“smile”，
webSource：“Chrome”，
}
next, in order to further understand the solution provided by the embodiment of the present application, referring to fig. 4, a specific flow chart of a front-end log processing method is provided for the embodiment of the present application, which specifically includes:
401, the client device monitors the running state of the web application in real time and generates a front-end log.
Alternatively, the client device may generate the front-end log when monitoring that the web application runs in error. Or the client device can also generate a front-end log for recording the problem in response to a user-triggered operation of generating the log.
402, after the client device generates the set duration of the front-end log, the front-end log is stored in the indexedDB database.
And 403, the client device sends the front-end log stored in the indexedDB database in the period to the application server at set intervals.
And 404, the application server receives the front-end logs, performs statistical classification on the front-end logs, and displays the front-end logs after statistical classification by using echart.
Specifically, the application server can display the trend and the rule of the front-end log by using echart, so that operation and maintenance personnel can conveniently analyze the problems.
Based on the same concept as the method described above, referring to fig. 5, a processing apparatus 500 for front-end logs is provided for the embodiment of the present application. The apparatus 500 is configured to perform the steps of the method, and therefore, in order to avoid repetition, the detailed description is omitted here. The apparatus 500 comprises: a processing unit 501 and a communication unit 502.
In one possible scenario:
the processing unit 501 is configured to monitor an operation state of a web application of a web page in real time, and generate a front-end log according to the operation state; the front end log is used for representing problems occurring in the running process of the web application program;
the processing unit 501 is further configured to store the front-end log in a database;
a communication unit 502, configured to send the front-end log to an application server of the web application.
In some embodiments, the front end log comprises at least one of:
a timestamp of an occurrence of a problem during the running of the web application, an identifier for identifying the problem, a rating of the problem, or descriptive information of the problem.
In some embodiments, the processing unit 501 is specifically configured to:
when the running of the web application program is detected to have an error, generating the front-end log; alternatively, the first and second electrodes may be,
and responding to the operation of generating the front-end log triggered by a user, and generating the front-end log.
In some embodiments, the processing unit 501 is further configured to:
deleting the front end log stored in the database after a first set time length.
In some embodiments, the processing unit 501 is specifically configured to:
after generating a second set duration of the front-end log, storing the front-end log in a database; the database is an IndexDB database.
In some embodiments, the communication unit 502 is specifically configured to:
and sending the front end log stored in the database in the set period to the application server at set intervals.
In another possible scenario:
a communication unit 502 for receiving a front-end log from a client device;
a processing unit 501, configured to store the front end log according to the problem indicated by the front end log.
In some embodiments, the front end log comprises at least one of:
a timestamp of an occurrence of a problem during the running of the web application, an identifier for identifying the problem, a rating of the problem, or descriptive information of the problem.
Fig. 6 shows a schematic structural diagram of an electronic device 600 provided in an embodiment of the present application. The electronic device 600 in this embodiment of the application may further include a communication interface 603, where the communication interface 603 is, for example, a network port, and the electronic device may transmit data through the communication interface 603, for example, the communication interface 603 may implement the function of the communication unit 502 in fig. 5.
In the embodiment of the present application, the memory 602 stores instructions executable by the at least one controller 601, and the at least one controller 601 may be configured to execute the steps in the method described above by executing the instructions stored in the memory 602, for example, the controller 601 may implement the functions of the processing unit 501 in fig. 5 described above.
The controller 601 is a control center of the electronic device, and may connect various parts of the whole electronic device by using various interfaces and lines, by executing or executing instructions stored in the memory 602 and calling data stored in the memory 602. Alternatively, the controller 601 may include one or more processing units, and the controller 601 may integrate an application controller and a modem controller, wherein the application controller mainly handles an operating system, application programs, and the like, and the modem controller mainly handles wireless communication. It will be appreciated that the modem controller described above may not be integrated into the controller 601. In some embodiments, the controller 601 and the memory 602 may be implemented on the same chip, or in some embodiments, they may be implemented separately on separate chips.
The controller 601 may be a general-purpose controller, such as a Central Processing Unit (CPU), digital signal controller, application specific integrated circuit, field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, and may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. The general controller may be a microcontroller or any conventional controller or the like. The steps executed by the data statistics platform disclosed in the embodiments of the present application may be directly executed by a hardware controller, or may be executed by a combination of hardware and software modules in the controller.
The memory 602, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 602 may include at least one type of storage medium, and may include, for example, a flash Memory, a hard disk, a multimedia card, a card-type Memory, a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Programmable Read Only Memory (PROM), a Read Only Memory (ROM), a charge Erasable Programmable Read Only Memory (EEPROM), a magnetic Memory, a magnetic disk, an optical disk, and so on. The memory 602 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 602 in the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.
By programming the controller 601, for example, the code corresponding to the training method of the neural network model described in the foregoing embodiment may be fixed in the chip, so that the chip can execute the steps of the training method of the neural network model when running.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a controller of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the controller of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While the preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all alterations and modifications as fall within the scope of the application.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (10)
1. A method for processing a front-end log, comprising:
monitoring the running state of a web application program of a webpage in real time, and generating a front-end log according to the running state; the front end log is used for representing problems occurring in the running process of the web application program;
storing the front end log in a database;
sending the front end log to an application server of the web application.
2. The method of claim 1, wherein the front end log comprises at least one of:
a timestamp of an occurrence of a problem during the running of the web application, an identifier for identifying the problem, a rating of the problem, or descriptive information of the problem.
3. The method of claim 1 or 2, wherein generating a front-end log according to the operational state comprises:
when the running of the web application program is detected to have an error, generating the front-end log; or responding to the operation of generating the front-end log triggered by a user, and generating the front-end log.
4. The method of claim 1 or 2, wherein the method further comprises:
deleting the front end log stored in the database after a first set time length.
5. The method of claim 1 or 2, wherein said storing the front end log in a database comprises:
after generating a second set duration of the front-end log, storing the front-end log in a database; the database is an IndexDB database.
6. The method of claim 1 or 2, wherein the sending the front end log to an application server of the web application comprises:
and sending the front end log stored in the database in the set period to the application server at set intervals.
7. A method for processing a front-end log, comprising:
receiving a front-end log from a client device, and storing the front-end log according to a problem indicated by the front-end log.
8. An electronic device, comprising:
a memory for storing computer instructions;
a processor coupled to the memory for executing the computer instructions in the memory and when executing the computer instructions implementing the method of any of claims 1-7.
9. A computer-readable storage medium, comprising:
the computer readable storage medium stores computer instructions which, when executed on a computer, cause the computer to perform the method of any of claims 1-7.
10. A computer program product, comprising:
the computer program product comprising computer program code which, when executed by a computer, causes the computer to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111680689.3A CN114443424A (en) | 2021-12-27 | 2021-12-27 | Front-end log processing method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111680689.3A CN114443424A (en) | 2021-12-27 | 2021-12-27 | Front-end log processing method, device and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114443424A true CN114443424A (en) | 2022-05-06 |
Family
ID=81365389
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111680689.3A Pending CN114443424A (en) | 2021-12-27 | 2021-12-27 | Front-end log processing method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114443424A (en) |
-
2021
- 2021-12-27 CN CN202111680689.3A patent/CN114443424A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11588922B2 (en) | Capturing and replaying application sessions using resource files | |
| WO2018120722A1 (en) | Asynchronous interface testing method, terminal, device, system, and storage medium | |
| CN112148674B (en) | Log data processing method, device, computer equipment and storage medium | |
| CN111901192B (en) | Statistical method and device for page access data | |
| CN113987074A (en) | Distributed service full-link monitoring method and device, electronic equipment and storage medium | |
| US20100145978A1 (en) | Techniques to provide unified logging services | |
| CN112394908A (en) | Method and device for automatically generating embedded point page, computer equipment and storage medium | |
| CN112631924A (en) | Automatic testing method and device, computer equipment and storage medium | |
| US20140052851A1 (en) | Systems and methods for discovering sources of online content | |
| CN110807050B (en) | Performance analysis method, device, computer equipment and storage medium | |
| CN112817831A (en) | Application performance monitoring method, device, computer system and readable storage medium | |
| CN114443424A (en) | Front-end log processing method, device and system | |
| CN113535565B (en) | Interface use case generation method, device, equipment and medium | |
| CN110554892A (en) | Information acquisition method and device | |
| CN116450465B (en) | Data processing method, device, equipment and medium | |
| KR102202923B1 (en) | Module specific tracing in a shared module environment | |
| CN117331804A (en) | Front-end page monitoring method and device, computer equipment and storage medium | |
| CN112559278B (en) | Method and device for acquiring operation data | |
| CN116467145A (en) | Page performance data acquisition method and device, computer equipment and storage medium | |
| CN116263679A (en) | Data processing method, device, computer equipment and storage medium | |
| CN114328096A (en) | Index monitoring method, device, equipment and medium | |
| CN112116374A (en) | Advertisement resource access method, device, readable storage medium and terminal equipment | |
| CN113535153A (en) | Method, device, equipment and medium for encoding custom label | |
| CN116431149A (en) | Page typesetting method, device, computer equipment and storage medium | |
| CN117370695A (en) | Page display method, device, equipment, medium and product |
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 |