CN116991689A - Front-end error monitoring method, device, equipment and storage medium - Google Patents
Front-end error monitoring method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN116991689A CN116991689A CN202311010344.6A CN202311010344A CN116991689A CN 116991689 A CN116991689 A CN 116991689A CN 202311010344 A CN202311010344 A CN 202311010344A CN 116991689 A CN116991689 A CN 116991689A
- Authority
- CN
- China
- Prior art keywords
- log data
- error log
- error
- data set
- invalid
- 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
- 238000012544 monitoring process Methods 0.000 title claims abstract description 59
- 238000000034 method Methods 0.000 title claims abstract description 35
- 238000000586 desensitisation Methods 0.000 claims abstract description 36
- 238000013075 data extraction Methods 0.000 claims abstract description 16
- 238000012217 deletion Methods 0.000 claims abstract description 15
- 230000037430 deletion Effects 0.000 claims abstract description 15
- 238000012545 processing Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 12
- 238000012216 screening Methods 0.000 claims description 3
- 238000005516 engineering process Methods 0.000 abstract description 6
- 238000012806 monitoring device Methods 0.000 abstract description 3
- 238000007726 management method Methods 0.000 description 15
- 230000006870 function Effects 0.000 description 11
- 238000004891 communication Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 238000013473 artificial intelligence Methods 0.000 description 3
- 238000013136 deep learning model Methods 0.000 description 2
- 238000003745 diagnosis Methods 0.000 description 2
- 239000004973 liquid crystal related substance Substances 0.000 description 2
- 238000010606 normalization Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000004378 air conditioning Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/0766—Error or fault reporting or storing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9537—Spatial or temporal dependent retrieval, e.g. spatiotemporal queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application relates to the field of monitoring technology and digital medical treatment, and discloses a front-end error monitoring method, which comprises the steps of performing error capturing on a target front-end page to obtain an error log data set; performing invalid error log data deletion and valid data extraction on the error log data set to obtain a standard error log data set; desensitizing each piece of standard error log data in the standard error log data set to obtain desensitized error log data; and acquiring the recording time of each piece of desensitization error log data, and reporting all the desensitization error log data based on the sequence of the recording time so as to perform error monitoring on the target front-end page. The application also provides a front-end error monitoring device, equipment and medium, which can be used in the medical field, and improves the efficiency of front-end error monitoring of medical application such as a medical management system.
Description
Technical Field
The present application relates to monitoring technologies, and in particular, to a method and apparatus for monitoring a front-end error, an electronic device, and a storage medium.
Background
In the medical science and technology field, in order to ensure the stable running of the medical application running in the browser, front-end error monitoring needs to be performed on the front-end page of the medical application (for example, the medical application is a medical management system application, which is a front-end application for managing medical institutions such as hospitals, clinics, pharmacies and the like, and can provide functions such as registration, appointment, diagnosis, prescription, payment and the like), and in order to ensure the normal running of the application, front-end error monitoring needs to be performed on the front-end page of the medical management system application.
However, the existing front-end error monitoring method directly reports all error information, so that effective front-end errors cannot be timely monitored, and the efficiency of front-end error monitoring of medical applications such as a medical management system is low.
Disclosure of Invention
The application provides a front-end error monitoring method, a front-end error monitoring device, electronic equipment and a storage medium, and mainly aims to improve the front-end error monitoring efficiency of medical applications such as a medical management system.
Performing error capturing on the target front-end page to obtain an error log data set;
performing invalid error log data deletion and valid data extraction on the error log data set to obtain a standard error log data set;
desensitizing each piece of standard error log data in the standard error log data set to obtain desensitized error log data;
and acquiring the recording time of each piece of desensitization error log data, and reporting all the desensitization error log data based on the sequence of the recording time so as to perform error monitoring on the target front-end page.
Optionally, the performing error capturing on the target front end page to obtain an error log data set includes:
capturing each piece of error information of a preset error type generated by the target front-end page to obtain corresponding error log data, wherein the preset error type comprises the following steps: global errors, resource loading errors, asynchronous errors;
and summarizing all the error log data to obtain the error log data set.
Optionally, the performing error capturing on the target front end page to obtain an error log data set includes:
constructing a time interval based on a preset time length and a current time;
capturing each piece of error information of a preset error type generated by the target front-end page, and screening error information of all captured error information, wherein error occurrence time of the error information is within the time interval, so as to obtain error log data;
and summarizing all the error log data to obtain the error log data set.
Optionally, the performing invalid error log data deletion and valid data extraction on the error log data set to obtain a standard error log data set includes:
removing error log data containing preset invalid keywords in the error log data set to obtain a target error log data set;
extracting effective data of each error log data in the target error log data set to obtain corresponding standard error log data;
and summarizing all the standard error log data to obtain the standard error log data set.
Optionally, the performing invalid error log data deletion and valid data extraction on the error log data set to obtain a standard error log data set includes:
identifying error log data which contains preset invalid keywords in the error log data set to obtain first invalid log data;
the error log data are concentrated in error log data with repeated occurrence times exceeding a preset error threshold value in a preset time period, and the second invalid log data are determined;
deleting the first invalid log data and the second invalid log data in the error log data set to obtain the target error log data set;
extracting effective data of each error log data in the target error log data set to obtain corresponding standard error log data;
and summarizing all the standard error log data to obtain the standard error log data set.
Optionally, the desensitizing processing is performed on each piece of standard error log data in the standard error log data set to obtain desensitized error log data, including:
and identifying sensitive data in the standard error log data by using a preset desensitization rule, and carrying out desensitization processing on the identified sensitive data to obtain the desensitized error log data.
In order to solve the above problems, the present application further provides a front-end error monitoring apparatus, the apparatus comprising:
the error capturing module is used for capturing errors of the target front-end page to obtain an error log data set;
the data standardization module is used for deleting the invalid error log data and extracting the valid data from the error log data set to obtain a standard error log data set; desensitizing each piece of standard error log data in the standard error log data set to obtain desensitized error log data;
and the error reporting monitoring module is used for acquiring the recording time of each piece of desensitized error log data, and reporting all pieces of desensitized error log data based on the sequence of the recording time so as to perform error monitoring on the target front-end page.
Optionally, the performing invalid error log data deletion and valid data extraction on the error log data set to obtain a standard error log data set includes:
identifying error log data which contains preset invalid keywords in the error log data set to obtain first invalid log data;
the error log data are concentrated in error log data with repeated occurrence times exceeding a preset error threshold value in a preset time period, and the second invalid log data are determined;
deleting the first invalid log data and the second invalid log data in the error log data set to obtain the target error log data set;
extracting effective data of each error log data in the target error log data set to obtain corresponding standard error log data;
and summarizing all the standard error log data to obtain the standard error log data set.
In order to solve the above-mentioned problems, the present application also provides an electronic apparatus including:
a memory storing at least one computer program; a kind of electronic device with high-pressure air-conditioning system
And the processor executes the computer program stored in the memory to realize the front-end error monitoring method.
In order to solve the above-mentioned problems, the present application also provides a computer-readable storage medium having stored therein at least one computer program that is executed by a processor in an electronic device to implement the front-end error monitoring method described above.
According to the embodiment of the application, invalid error log data deletion and valid data extraction are carried out on the error log data set, so that a standard error log data set is obtained; desensitizing each piece of standard error log data in the standard error log data set to obtain desensitized error log data; and acquiring the recording time of each piece of desensitization error log data, and reporting all the desensitization error log data based on the sequence of the recording time so as to perform error monitoring on the target front-end page. Invalid error information is timely deleted and data are standardized to reduce invalid data in the data, so that the probability of error reporting in the reported desensitized error log data is reduced, and the front-end error monitoring efficiency of medical applications such as a medical management system is improved. Therefore, the front-end error monitoring method, the device, the electronic equipment and the readable storage medium provided by the embodiment of the application improve the efficiency of front-end error monitoring of medical application such as a medical management system.
Drawings
FIG. 1 is a flowchart illustrating a front-end error monitoring method according to an embodiment of the present application;
FIG. 2 is a schematic block diagram of a front-end error monitoring device according to an embodiment of the present application;
FIG. 3 is a schematic diagram illustrating an internal structure of an electronic device for implementing a front-end error monitoring method according to an embodiment of the present application;
the achievement of the objects, functional features and advantages of the present application will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
The embodiment of the application provides a front-end error monitoring method. The execution body of the front-end error monitoring method includes, but is not limited to, at least one of a server, a terminal, and the like, which can be configured to execute the method provided by the embodiment of the application. In other words, the front-end error monitoring method may be performed by software or hardware installed in a terminal device or a server device, and the software may be a blockchain platform. The service end includes but is not limited to: the server can be an independent server, or can be a cloud server for providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDNs), basic cloud computing services such as big data and artificial intelligent platforms, and the like.
Referring to fig. 1, which is a schematic flow chart of a front-end error monitoring method according to an embodiment of the present application, in an embodiment of the present application, the front-end error monitoring method includes the following steps:
s1, performing error capturing on a target front-end page to obtain an error log data set;
the target front page in the embodiment of the application is a front page of a medical application running in a front browser, such as a front page of a medical management system, and is a front page for managing medical institutions such as hospitals, clinics, pharmacies and the like, and can provide functions such as registration, appointment, diagnosis, prescription, payment and the like. And in order to perform error monitoring on the target front-end page, performing error capturing on the target front-end page to obtain an error log data set.
In detail, in the embodiment of the present application, performing error capturing on a target front-end page to obtain an error log data set includes:
capturing each piece of error information of a preset error type generated by the target front-end page to obtain corresponding error log data, wherein the preset error type comprises the following steps: global errors, resource loading errors, asynchronous errors;
and summarizing all the error log data to obtain the error log data set.
In detail, in the embodiment of the application, the window. Onerror is utilized to capture the log data corresponding to the global error, the window. AddEventListener ('error', callback) is utilized to capture the log data corresponding to the resource loading error, and the try-catch is utilized to capture the log data corresponding to the asynchronous error.
Further, in order to ensure validity of the captured error log data, in the embodiment of the present application, the performing error capturing on the target front-end page to obtain an error log data set includes:
constructing a time interval based on a preset time length and a current time;
capturing each piece of error information of a preset error type generated by the target front-end page, and screening error information of all captured error information, wherein error occurrence time of the error information is within the time interval, so as to obtain error log data;
and summarizing all the error log data to obtain the error log data set.
In detail, in the embodiment of the present application, the time interval is constructed based on the preset time length and the current time, including:
and determining the time length as an interval length, determining the current time as an interval right endpoint, and constructing an interval to obtain the time interval.
Optionally, the error message in the embodiment of the present application includes: error type, error information, error stack, time at which the error occurred, page URL, etc.
S2, deleting invalid error log data and extracting valid data from the error log data set to obtain a standard error log data set;
in the embodiment of the application, invalid log data in the error log data set is removed, invalid error log data deletion and valid data extraction are performed on the error log data set, and a standard error log data set is obtained.
In detail, in the embodiment of the present application, performing invalid error log data deletion and valid data extraction on the error log data set to obtain a standard error log data set includes:
removing error log data containing preset invalid keywords in the error log data set to obtain a target error log data set;
extracting effective data of each error log data in the target error log data set to obtain corresponding standard error log data;
and summarizing all the standard error log data to obtain the standard error log data set.
Further, in the embodiment of the present application, performing invalid error log data deletion and valid data extraction on the error log data set to obtain a standard error log data set includes:
identifying error log data which contains preset invalid keywords in the error log data set to obtain first invalid log data;
the error log data are concentrated in error log data with repeated occurrence times exceeding a preset error threshold value in a preset time period, and the second invalid log data are determined;
deleting the first invalid log data and the second invalid log data in the error log data set to obtain the target error log data set;
extracting effective data of each error log data in the target error log data set to obtain corresponding standard error log data;
and summarizing all the standard error log data to obtain the standard error log data set.
It should be explained that, in the embodiment of the present application, the preset invalid keyword is a browser plug-in or advertisement interceptor of the front end (for example, the preset invalid keyword is chrome-extension "or" adblock "), the network is unstable or the server is overtime (for example, the preset invalid keyword is" network error "or" TimeoutError "), and the error log data is a flag keyword contained in the error log data, and the error log data caused by the fact that the browser plug-in or advertisement interceptor, the network is unstable or the server overtime is not the error log data generated by the execution of the front end itself is invalid, so that the error log data containing the preset invalid keyword is deleted; in addition, if an error occurs frequently in a short time, it may be caused by some temporary reasons, such as network fluctuations, server load, user operation, etc., and the error may not need urgent processing nor have serious influence on the system, and thus, it is also an error that does not need reporting, so that this type of error log data, i.e., the second invalid log data, is also deleted.
In the embodiment of the application, since all information in the error log data does not need to be reported and only the information of the related key needs to be reported, each error log data in the target error log data set is subjected to effective data extraction to obtain the corresponding standard error log data.
In detail, in the embodiment of the present application, extracting valid data from each error log data in the target error log data set to obtain corresponding standard error log data includes:
and extracting data corresponding to preset attributes in each error log data in the target error log data set to obtain the corresponding standard error log data.
Optionally, in the embodiment of the present application, the preset attribute includes, but is not limited to: error information, error stack, time at which the error occurred, page URL.
S3, desensitizing each piece of standard error log data in the standard error log data set to obtain desensitized error log data;
in the embodiment of the application, because sensitive information of a user may exist in the standard error log data set, in order to protect the privacy of the user, desensitizing treatment is performed on each piece of standard error log data in the standard error log data set to obtain desensitized error log data.
In detail, in the embodiment of the present application, the desensitizing processing is performed on each piece of standard error log data in the standard error log data set to obtain desensitized error log data, including:
and identifying sensitive data in the standard error log data by using a preset desensitization rule, and carrying out desensitization processing on the identified sensitive data to obtain the desensitized error log data.
Further, in the embodiment of the present application, the identifying sensitive data in the standard error log data by using a preset desensitization rule, and performing desensitization processing on the identified sensitive data to obtain the desensitized error log data includes:
extracting the type of the desensitization field in the preset desensitization rule;
optionally, the desensitization rule in the embodiment of the present application is a pre-constructed data desensitization rule, and includes a sensitive field type, a desensitization rule, etc. that need to be desensitized, where the sensitive field type may include a field type such as a phone number, an identification card number, an address, etc.
Identifying fields of the same type as the desensitization fields in the standard error log data to obtain sensitive data;
optionally, the embodiment of the present application may identify a field of the same type as the desensitized field type in the standard error log data by using a deep learning model to obtain sensitive data, where the deep learning model may be a bert model.
And carrying out character replacement on each sensitive data in the standard error log data to obtain the desensitized error log data.
Specifically, in the embodiment of the present application, a preset sequence of characters in each sensitive field in the standard error log data is replaced with a preset desensitization symbol, so as to obtain the desensitization error log data.
The form of the desensitization symbol is not limited in the embodiment of the application.
Further, in the embodiment of the present application, the identifying sensitive data in the standard error log data by using a preset desensitization rule, and performing desensitization processing on the identified sensitive data to obtain the desensitized error log data includes:
extracting the type of the desensitization field in the preset desensitization rule;
identifying fields of the same type as the desensitization fields in the standard error log data to obtain sensitive data;
calculating the sensitive data by using a preset mask code generation algorithm to obtain mask data;
and replacing the corresponding sensitive data in the standard error log data by using the covering data to obtain the desensitized error log data.
S4, acquiring the recording time of each piece of desensitization error log data, and reporting all the desensitization error log data based on the sequence of the recording time so as to perform error monitoring on the target front-end page.
In the embodiment of the application, the recording time is the error generation time of the error information corresponding to the desensitized error log data.
In the embodiment of the application, the data structures such as an array or a queue are used at the front end to store the desensitized error log data, an upper limit value or a timeout value is set to control the reporting time of the sensitized error log data, and the reported desensitized error log data is processed at the rear end by using the technologies such as batch processing or distributed processing, so that the burden of the front end is reduced, and meanwhile, the error monitoring on the front page of the target front end is realized.
For example: when the target front-end page is a medical front-end page, such as a front-end page of a medical management system, the operation fault of the front-end page of the medical management system can be timely found to repair through error monitoring, so that the operation stability of the medical management system is improved
FIG. 2 is a functional block diagram of the front-end error monitoring apparatus of the present application.
The front-end error monitoring apparatus 100 of the present application may be installed in an electronic device. Depending on the implemented functions, the front-end error monitoring apparatus may include an error capture module 101, a data normalization module 102, and an error reporting monitoring module 103, which may also be referred to as a unit, refers to a series of computer program segments that can be executed by a processor of an electronic device and that can perform a fixed function, and are stored in a memory of the electronic device.
In the present embodiment, the functions concerning the respective modules/units are as follows:
the error capturing module 101 is configured to perform error capturing on a target front end page to obtain an error log data set;
the data normalization module 102 is configured to delete invalid error log data and extract valid data from the error log data set to obtain a standard error log data set; desensitizing each piece of standard error log data in the standard error log data set to obtain desensitized error log data;
the error report monitoring module 103 is configured to obtain a recording time of each piece of desensitized error log data, and report all pieces of desensitized error log data based on the sequence of the recording time, so as to perform error monitoring on the target front-end page.
In detail, each module of the front-end error monitoring apparatus 100 in the embodiment of the present application adopts the same technical means as the front-end error monitoring method described in fig. 1, and can produce the same technical effects, which are not repeated here.
Fig. 3 is a schematic structural diagram of an electronic device for implementing the front-end error monitoring method according to the present application.
The electronic device may comprise a processor 10, a memory 11, a communication bus 12 and a communication interface 13, and may further comprise a computer program, such as a front end error monitoring program, stored in the memory 11 and executable on the processor 10.
The memory 11 includes at least one type of readable storage medium, including flash memory, a mobile hard disk, a multimedia card, a card memory (e.g., SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, etc. The memory 11 may in some embodiments be an internal storage unit of the electronic device, such as a mobile hard disk of the electronic device. The memory 11 may in other embodiments also be an external storage device of the electronic device, such as a plug-in mobile hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the electronic device. Further, the memory 11 may also include both an internal storage unit and an external storage device of the electronic device. The memory 11 may be used not only for storing application software installed in an electronic device and various types of data, such as codes of a front-end error monitoring program, but also for temporarily storing data that has been output or is to be output.
The processor 10 may be comprised of integrated circuits in some embodiments, for example, a single packaged integrated circuit, or may be comprised of multiple integrated circuits packaged with the same or different functions, including one or more central processing units (Central Processing Unit, CPU), microprocessors, digital processing chips, graphics processors, combinations of various control chips, and the like. The processor 10 is a Control Unit (Control Unit) of the electronic device, connects various components of the entire electronic device using various interfaces and lines, and executes various functions of the electronic device and processes data by running or executing programs or modules (e.g., a front-end error monitoring program, etc.) stored in the memory 11, and calling data stored in the memory 11.
The communication bus 12 may be a peripheral component interconnect standard (PerIPheralComponent Interconnect, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The bus may be classified as an address bus, a data bus, a control bus, etc. The communication bus 12 is arranged to enable a connection communication between the memory 11 and at least one processor 10 etc. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.
Fig. 3 shows only an electronic device with components, and it will be understood by those skilled in the art that the structure shown in fig. 3 is not limiting of the electronic device and may include fewer or more components than shown, or may combine certain components, or a different arrangement of components.
For example, although not shown, the electronic device may further include a power source (such as a battery) for supplying power to the respective components, and preferably, the power source may be logically connected to the at least one processor 10 through a power management device, so that functions of charge management, discharge management, power consumption management, and the like are implemented through the power management device. The power supply may also include one or more of any of a direct current or alternating current power supply, recharging device, power failure classification circuit, power converter or inverter, power status indicator, etc. The electronic device may further include various sensors, bluetooth modules, wi-Fi modules, etc., which are not described herein.
Optionally, the communication interface 13 may comprise a wired interface and/or a wireless interface (e.g., WI-FI interface, bluetooth interface, etc.), typically used to establish a communication connection between the electronic device and other electronic devices.
Optionally, the communication interface 13 may further comprise a user interface, which may be a Display, an input unit, such as a Keyboard (Keyboard), or a standard wired interface, a wireless interface. Alternatively, in some embodiments, the display may be an LED display, a liquid crystal display, a touch-sensitive liquid crystal display, an OLED (Organic Light-Emitting Diode) touch, or the like. The display may also be referred to as a display screen or display unit, as appropriate, for displaying information processed in the electronic device and for displaying a visual user interface.
It should be understood that the embodiments described are for illustrative purposes only and are not limited to this configuration in the scope of the patent application.
The front-end error monitoring program stored in the memory 11 of the electronic device is a combination of a plurality of computer programs, which, when run in the processor 10, can implement:
performing error capturing on the target front-end page to obtain an error log data set;
performing invalid error log data deletion and valid data extraction on the error log data set to obtain a standard error log data set;
desensitizing each piece of standard error log data in the standard error log data set to obtain desensitized error log data;
and acquiring the recording time of each piece of desensitization error log data, and reporting all the desensitization error log data based on the sequence of the recording time so as to perform error monitoring on the target front-end page.
In particular, the specific implementation method of the processor 10 on the computer program may refer to the description of the relevant steps in the corresponding embodiment of fig. 1, which is not repeated herein.
Further, the electronic device integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. The computer readable medium may be non-volatile or volatile. The computer readable medium may include: any entity or device capable of carrying the computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM).
Embodiments of the present application may also provide a computer readable storage medium storing a computer program which, when executed by a processor of an electronic device, may implement:
performing error capturing on the target front-end page to obtain an error log data set;
performing invalid error log data deletion and valid data extraction on the error log data set to obtain a standard error log data set;
desensitizing each piece of standard error log data in the standard error log data set to obtain desensitized error log data;
and acquiring the recording time of each piece of desensitization error log data, and reporting all the desensitization error log data based on the sequence of the recording time so as to perform error monitoring on the target front-end page.
Further, the computer-usable storage medium may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created from the use of blockchain nodes, and the like.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus, device and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be other manners of division when actually implemented.
The modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
The embodiment of the application can acquire and process the related data based on the artificial intelligence technology. Among these, artificial intelligence (Artificial Intelligence, AI) is the theory, method, technique and application system that uses a digital computer or a digital computer-controlled machine to simulate, extend and extend human intelligence, sense the environment, acquire knowledge and use knowledge to obtain optimal results.
In addition, each functional module in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units can be realized in a form of hardware or a form of hardware and a form of software functional modules.
It will be evident to those skilled in the art that the application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential characteristics thereof.
The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference signs in the claims shall not be construed as limiting the claim concerned.
The blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, consensus mechanism, encryption algorithm and the like. The Blockchain (Blockchain), which is essentially a decentralised database, is a string of data blocks that are generated by cryptographic means in association, each data block containing a batch of information of network transactions for verifying the validity of the information (anti-counterfeiting) and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, an application services layer, and the like.
Furthermore, it is evident that the word "comprising" does not exclude other elements or steps, and that the singular does not exclude a plurality. A plurality of units or means recited in the system claims can also be implemented by means of software or hardware by means of one unit or means. The terms second, etc. are used to denote a name, but not any particular order.
Finally, it should be noted that the above-mentioned embodiments are merely for illustrating the technical solution of the present application and not for limiting the same, and although the present application has been described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications and equivalents may be made to the technical solution of the present application without departing from the spirit and scope of the technical solution of the present application.
Claims (10)
1. A method for front-end error monitoring, the method comprising:
performing error capturing on the target front-end page to obtain an error log data set;
performing invalid error log data deletion and valid data extraction on the error log data set to obtain a standard error log data set;
desensitizing each piece of standard error log data in the standard error log data set to obtain desensitized error log data;
and acquiring the recording time of each piece of desensitization error log data, and reporting all the desensitization error log data based on the sequence of the recording time so as to perform error monitoring on the target front-end page.
2. The method for monitoring a front-end error as claimed in claim 1, wherein said performing error capture on the target front-end page to obtain an error log data set includes:
capturing each piece of error information of a preset error type generated by the target front-end page to obtain corresponding error log data, wherein the preset error type comprises the following steps: global errors, resource loading errors, asynchronous errors;
and summarizing all the error log data to obtain the error log data set.
3. The method for monitoring a front-end error as claimed in claim 1, wherein said performing error capture on the target front-end page to obtain an error log data set includes:
constructing a time interval based on a preset time length and a current time;
capturing each piece of error information of a preset error type generated by the target front-end page, and screening error information of all captured error information, wherein error occurrence time of the error information is within the time interval, so as to obtain error log data;
and summarizing all the error log data to obtain the error log data set.
4. The method for monitoring front-end errors according to claim 1, wherein said performing invalid error log data deletion and valid data extraction on said error log data set to obtain a standard error log data set comprises:
removing error log data containing preset invalid keywords in the error log data set to obtain a target error log data set;
extracting effective data of each error log data in the target error log data set to obtain corresponding standard error log data;
and summarizing all the standard error log data to obtain the standard error log data set.
5. The method for monitoring front-end errors according to claim 1, wherein said performing invalid error log data deletion and valid data extraction on said error log data set to obtain a standard error log data set comprises:
identifying error log data which contains preset invalid keywords in the error log data set to obtain first invalid log data;
the error log data are concentrated in error log data with repeated occurrence times exceeding a preset error threshold value in a preset time period, and the second invalid log data are determined;
deleting the first invalid log data and the second invalid log data in the error log data set to obtain the target error log data set;
extracting effective data of each error log data in the target error log data set to obtain corresponding standard error log data;
and summarizing all the standard error log data to obtain the standard error log data set.
6. The front-end error monitoring method according to any one of claims 1 to 5, wherein said desensitizing each of the standard error log data in the standard error log data set to obtain desensitized error log data comprises:
and identifying sensitive data in the standard error log data by using a preset desensitization rule, and carrying out desensitization processing on the identified sensitive data to obtain the desensitized error log data.
7. A front-end error monitoring apparatus, comprising:
the error capturing module is used for capturing errors of the target front-end page to obtain an error log data set;
the data standardization module is used for deleting the invalid error log data and extracting the valid data from the error log data set to obtain a standard error log data set; desensitizing each piece of standard error log data in the standard error log data set to obtain desensitized error log data;
and the error reporting monitoring module is used for acquiring the recording time of each piece of desensitized error log data, and reporting all pieces of desensitized error log data based on the sequence of the recording time so as to perform error monitoring on the target front-end page.
8. The front-end error monitoring apparatus of claim 7, wherein said performing invalid error log data deletion and valid data extraction on said error log data set to obtain a standard error log data set comprises:
identifying error log data which contains preset invalid keywords in the error log data set to obtain first invalid log data;
the error log data are concentrated in error log data with repeated occurrence times exceeding a preset error threshold value in a preset time period, and the second invalid log data are determined;
deleting the first invalid log data and the second invalid log data in the error log data set to obtain the target error log data set;
extracting effective data of each error log data in the target error log data set to obtain corresponding standard error log data;
and summarizing all the standard error log data to obtain the standard error log data set.
9. An electronic device, the electronic device comprising:
at least one processor; the method comprises the steps of,
a memory communicatively coupled to the at least one processor;
wherein the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the front end error monitoring method of any one of claims 1 to 6.
10. A computer readable storage medium storing a computer program, wherein the computer program when executed by a processor implements the front-end error monitoring method according to any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311010344.6A CN116991689A (en) | 2023-08-10 | 2023-08-10 | Front-end error monitoring method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311010344.6A CN116991689A (en) | 2023-08-10 | 2023-08-10 | Front-end error monitoring method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116991689A true CN116991689A (en) | 2023-11-03 |
Family
ID=88531869
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311010344.6A Pending CN116991689A (en) | 2023-08-10 | 2023-08-10 | Front-end error monitoring method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116991689A (en) |
-
2023
- 2023-08-10 CN CN202311010344.6A patent/CN116991689A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113032403B (en) | Data insight method, device, electronic equipment and storage medium | |
| CN112702228B (en) | Service flow limit response method, device, electronic equipment and readable storage medium | |
| CN114491047A (en) | Multi-label text classification method and device, electronic equipment and storage medium | |
| CN113868529A (en) | Knowledge recommendation method and device, electronic equipment and readable storage medium | |
| CN112733531A (en) | Virtual resource allocation method and device, electronic equipment and computer storage medium | |
| CN113434542A (en) | Data relation identification method and device, electronic equipment and storage medium | |
| CN113468175A (en) | Data compression method and device, electronic equipment and storage medium | |
| CN113051224A (en) | File transmission method and device, electronic equipment and computer readable storage medium | |
| CN111985194A (en) | Data storage method and device, electronic equipment and storage medium | |
| CN114841165B (en) | User data analysis and display method and device, electronic equipment and storage medium | |
| CN116991689A (en) | Front-end error monitoring method, device, equipment and storage medium | |
| CN114911479A (en) | Interface generation method, device, equipment and storage medium based on configuration | |
| CN115203364A (en) | Software fault feedback processing method, device, equipment and readable storage medium | |
| CN113987206A (en) | Abnormal user identification method, device, equipment and storage medium | |
| CN113419718A (en) | Data transmission method, device, equipment and medium | |
| CN111339063A (en) | Intelligent management method and device for hypothesis data and computer readable storage medium | |
| CN113360505B (en) | Time sequence data-based data processing method and device, electronic equipment and readable storage medium | |
| CN113448933B (en) | Service data processing method, device, electronic equipment and medium | |
| CN112328960B (en) | Optimization method and device for data operation, electronic equipment and storage medium | |
| CN113704109B (en) | Front-end and back-end data interaction method and device, electronic equipment and storage medium | |
| CN113434365B (en) | Data characteristic monitoring method and device, electronic equipment and storage medium | |
| CN114598624B (en) | Cluster monitoring method and device, electronic equipment and readable storage medium | |
| CN116386831B (en) | Data visual display method and system based on intelligent hospital management platform | |
| CN112214556B (en) | Label generation method, label generation device, electronic equipment and computer readable storage medium | |
| CN113361244A (en) | Wind control analysis report generation method and device, electronic 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 |