CN112054915A - Processing method, device and system for client abnormity early warning and computing equipment - Google Patents
Processing method, device and system for client abnormity early warning and computing equipment Download PDFInfo
- Publication number
- CN112054915A CN112054915A CN201910492629.5A CN201910492629A CN112054915A CN 112054915 A CN112054915 A CN 112054915A CN 201910492629 A CN201910492629 A CN 201910492629A CN 112054915 A CN112054915 A CN 112054915A
- Authority
- CN
- China
- Prior art keywords
- page
- abnormal
- early warning
- log
- time period
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention discloses a processing method for client abnormity early warning, which comprises the following steps: acquiring log information reported by a client, wherein the log information comprises an abnormal log and a service object corresponding to the abnormal log; counting the number of abnormal logs of a page corresponding to the business object in a preset time period based on the log information; and judging whether to send out early warning or not based on the number of the abnormal logs and the access amount of the page corresponding to the business object in a preset time period. The embodiment of the invention also discloses a corresponding processing device, a system and a computing device for client abnormity early warning.
Description
Technical Field
The invention relates to the technical field of data processing, in particular to a processing method, a device and a system for client abnormity early warning and computing equipment.
Background
With the rapid development of the internet and the wide use of mobile terminals, users are more and more accustomed to handling daily affairs through various clients. In the face of a large number of users, the client abnormality is monitored and early warned, and the client is very necessary to be maintained to be stable and usable.
A common client exception early warning processing method is to perform log embedding on a code logical link to be monitored, so as to collect and record a log corresponding to success or failure of each step, and monitor and early warn the exception of the client based on the log. However, in this way, information such as a module or a page corresponding to the log is often required to be added when the log is collected. That is, any link that is logged requires additional input of such information, and this additional added code is more intrusive to the link logic. In addition, most of the common client exception early warning processing modes are early warning for pages, and early warning for special service objects is lacked.
Therefore, it is desirable to provide a more advanced client exception warning processing scheme for monitoring the client.
Disclosure of Invention
To this end, embodiments of the present invention provide a method, an apparatus, a system, and a computing device for handling client anomaly early warning, so as to attempt to solve or at least alleviate at least one of the above problems.
According to an aspect of an embodiment of the present invention, a method for processing client exception early warning is provided, including: acquiring log information reported by a client, wherein the log information comprises an abnormal log and a service object corresponding to the abnormal log; counting the number of abnormal logs of a page corresponding to the business object in a preset time period based on the log information; and judging whether to send out early warning or not based on the number of the abnormal logs and the access amount of the page corresponding to the business object in a preset time period.
Optionally, in the method according to the embodiment of the present invention, the method further includes: determining a page corresponding to the business object according to the page corresponding to the abnormal log; and counting the access amount of the page corresponding to the business object in a preset time period.
According to another aspect of the embodiments of the present invention, a method for processing client exception early warning is provided, including: acquiring log information reported by a client, wherein the log information comprises an abnormal log; counting the number of abnormal logs of the page in a preset time period based on the log information; and judging whether to send out early warning or not based on the number of the abnormal logs of the page and the access amount of the page in a preset time period.
According to another aspect of the embodiments of the present invention, there is provided a processing apparatus for client exception warning, including: the log obtaining unit is suitable for obtaining log information reported by the client, and the log information comprises an abnormal log and a service object corresponding to the abnormal log; the data counting unit is suitable for counting the number of abnormal logs of the page corresponding to the business object in a preset time period based on the log information; and the early warning judgment unit is suitable for judging whether to send out early warning or not based on the number of the abnormal logs and the access quantity of the page corresponding to the business object in a preset time period.
According to another aspect of the embodiments of the present invention, there is provided a processing apparatus for client exception warning, including: the log obtaining unit is suitable for obtaining log information reported by the client, and the log information comprises an abnormal log; the data counting unit is suitable for counting the number of abnormal logs of the page in a preset time period based on the log information; and the early warning judgment unit is suitable for judging whether to send out early warning or not based on the number of the abnormal logs of the page and the access amount of the page in a preset time period.
According to another aspect of the embodiments of the present invention, a processing system for client exception warning is provided, which includes a client and a server, where the server resides in a processing apparatus for client exception warning according to the embodiments of the present invention, where the client is adapted to provide a page; the method is also suitable for acquiring an abnormal log and establishing a corresponding relation between the abnormal log and the current page of the client; the method is also suitable for sending log information to the server, wherein the log information comprises an abnormal log, a service object corresponding to the abnormal log and a page corresponding to the abnormal log.
According to another aspect of embodiments of the present invention, there is provided a computing device including: one or more processors; and a memory; one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs including instructions for performing a method for handling client anomaly alerts according to an embodiment of the present invention
According to a further aspect of embodiments of the present invention, there is provided a computer-readable storage medium storing one or more programs, the one or more programs including instructions, which when executed by a computing device, cause the computing device to perform a method for handling client anomaly early warning according to embodiments of the present invention.
According to the processing scheme of the client abnormity early warning, the abnormity log corresponds to the page, so that the invasion to the link logic of the client is greatly reduced. And the client monitoring and early warning on the service object dimension are realized through the abnormal log corresponding to the service object. In addition, monitoring and early warning can be performed on page dimensions. Therefore, the service object dimension and the page dimension can be mutually adjudicated and combined, and the early warning accuracy and reliability are obviously improved.
By monitoring the abnormal rate instead of the change of the abnormal quantity, the inaccuracy of judgment from the quantity change is avoided, and the accuracy and the reliability of early warning are further improved.
Drawings
To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings, which are indicative of various ways in which the principles disclosed herein may be practiced, and all aspects and equivalents thereof are intended to be within the scope of the claimed subject matter. The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description read in conjunction with the accompanying drawings. Throughout this disclosure, like reference numerals generally refer to like parts or elements.
FIG. 1 shows a schematic diagram of a client exception warning handling system 100, according to one embodiment of the invention;
FIG. 2 shows a schematic diagram of a computing device 200, according to one embodiment of the invention;
FIG. 3 illustrates a flow diagram of a method 300 for handling client exception early warning, according to one embodiment of the invention;
fig. 4 is a block diagram illustrating a processing apparatus 400 for client exception warning according to an embodiment of the present invention;
FIG. 5 illustrates a flow diagram of a method 500 for handling client exception early warning, according to one embodiment of the invention; and
fig. 6 shows a block diagram of a processing apparatus 600 for client anomaly early warning according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Fig. 1 shows a schematic diagram of a client exception warning processing system 100 according to one embodiment of the present invention. As shown in fig. 1, the abnormality warning system 100 includes a client 110 and a server 120. The client 110 typically resides in a mobile terminal and may provide pages for a user to browse and operate. Generally, in order to monitor the performance of the client 110, a logging site can be performed on a logical link of the code to be monitored so as to collect a corresponding log.
Conventionally, when collecting a log, it is often necessary to obtain module or page information and the like corresponding to the log so as to record the module or page information in the log. Therefore, any link for collecting the log needs to be provided with a service code for additionally acquiring the information, and the service code has certain invasiveness to the link logic.
According to the embodiment of the present invention, the client 110 may collect the exception log, and establish a corresponding relationship between the exception log and the current page of the client 110 (i.e., the page currently accessed by the user). Namely, the service code for acquiring the page information does not need to be added when the log is embedded, and the intrusiveness on the link logic of the client is greatly reduced. Where the exception log may generally indicate the occurrence of an exception event. For example, the exception log may have an exception identification (tag) that identifies the type of exception event. Therefore, the page corresponding to the abnormal log can be used for determining that the page has the abnormal event indicated by the abnormal log.
In one embodiment, client 110 may maintain a page access list based on the appearance and disappearance of pages accessed by the user via client 110. The page access list records each page to be accessed and the access sequence of each page. Wherein, the current page defaults to the latest record in the page access list.
For example, if a user visits page a, page B, and page C in sequence, the maintained page access list may be as follows:
| page identification |
| C |
| B |
| A |
The top layer is the current page recorded last, that is, the page C currently accessed by the user. The bottom layer is page A which the user originally visits.
Therefore, when the abnormal log is collected, the corresponding relation between the abnormal log and the current page can be established, and the current page is indicated to have an abnormal event. The method has the advantages that the page information is obtained almost seamlessly while the page information is prevented from being added into the log, and the invasion to the link logic of the client side is greatly reduced.
In addition, in addition to paying attention to the exception of a specific certain page, according to the embodiment of the invention, the exception of some business objects (for example, some special business items) is also paid attention to. These business objects typically relate to multiple pages, for example, a favorite business item may relate to a favorite page of merchandise, a favorite page of a store, a favorite page of an order, and so forth. Special monitoring and early warning of these business objects is required.
Therefore, in the embodiment of the present invention, when the client 110 collects the abnormal log, it may further obtain the business object corresponding to the abnormal log, so that monitoring and early warning of the business object may be implemented. The business object corresponding to the abnormal log can be directly configured when the log is subjected to point burying. Note that the configuration of the business object is not intrusive to the client link logic.
After collecting the abnormal log, the client 110 may send the log information to the server 120, so that the server 120 monitors and warns the client 110 based on the log information. It can be understood that the log information includes an exception log, a service object corresponding to the exception log, and a page corresponding to the exception log.
Specifically, the server 120 has a client anomaly pre-warning processing device 400 resident therein, and may communicate with the clients 110 over one or more networks 130, such as a Local Area Network (LAN) or a Wide Area Network (WAN). According to an embodiment of the present invention, the processing apparatus 400 for client anomaly early warning may be implemented by the computing device 200 as described below.
FIG. 2 shows a schematic diagram of a computing device 200, according to one embodiment of the invention. As shown in FIG. 2, in a basic configuration 202, a computing device 200 typically includes a system memory 206 and one or more processors 204. A memory bus 208 may be used for communication between the processor 204 and the system memory 206.
Depending on the desired configuration, the processor 204 may be any type of processing, including but not limited to: a microprocessor (μ P), a microcontroller (μ C), a Digital Signal Processor (DSP), or any combination thereof. The processor 204 may include one or more levels of cache, such as a level one cache 210 and a level two cache 212, a processor core 214, and registers 216. Example processor cores 214 may include Arithmetic Logic Units (ALUs), Floating Point Units (FPUs), digital signal processing cores (DSP cores), or any combination thereof. The example memory controller 218 may be used with the processor 204, or in some implementations the memory controller 218 may be an internal part of the processor 204.
Depending on the desired configuration, system memory 206 may be any type of memory, including but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. System memory 206 may include an operating system 220, one or more applications 222, and program data 224. In some implementations, the application 222 can be arranged to execute instructions on the operating system with the program data 224 by the one or more processors 204.
Computing device 200 may also include an interface bus 240 that facilitates communication from various interface devices (e.g., output devices 242, peripheral interfaces 244, and communication devices 246) to the basic configuration 202 via the bus/interface controller 230. The example output device 242 includes a graphics processing unit 248 and an audio processing unit 250. They may be configured to facilitate communication with various external devices, such as a display or speakers, via one or more a/V ports 252. Example peripheral interfaces 244 can include a serial interface controller 254 and a parallel interface controller 256, which can be configured to facilitate communications with external devices such as input devices (e.g., keyboard, mouse, pen, voice input device, touch input device) or other peripherals (e.g., printer, scanner, etc.) via one or more I/O ports 258. An example communication device 246 may include a network controller 260, which may be arranged to facilitate communications with one or more other computing devices 262 over a network communication link via one or more communication ports 264.
A network communication link may be one example of a communication medium. Communication media may typically be embodied by computer readable instructions, data structures, program modules, and may include any information delivery media, such as carrier waves or other transport mechanisms, in a modulated data signal. A "modulated data signal" may be a signal that has one or more of its data set or its changes made in such a manner as to encode information in the signal. By way of non-limiting example, communication media may include wired media such as a wired network or private-wired network, and various wireless media such as acoustic, Radio Frequency (RF), microwave, Infrared (IR), or other wireless media. The term computer readable media as used herein may include both storage media and communication media.
Computing device 200 may be implemented as a server, such as a database server, an application server, a WEB server, and the like, or as a personal computer including desktop and notebook computer configurations. Of course, computing device 200 may also be implemented as part of a small-sized portable (or mobile) electronic device.
In an embodiment according to the present invention, the computing device 200 is implemented as each component in the processing apparatus 400 of client anomaly early warning, and is configured to execute the processing method 300 of client anomaly early warning according to the embodiment of the present invention. The application 222 of the computing device 200 includes a plurality of instructions for executing the processing method 300 for client exception warning according to the embodiment of the present invention, and the program data 224 may further store configuration information of the client exception warning processing system 100, and the like.
Fig. 3 shows a flowchart of a processing method 300 for client anomaly early warning according to an embodiment of the present invention. The anomaly early warning method 300 is executed in the processing device 400 for client anomaly early warning. As shown in fig. 3, the processing method 300 of client anomaly early warning starts in step S310.
In step S310, log information reported by the client 110 is obtained, where the log information may include an abnormal log and a service object corresponding to the abnormal log. As described previously, the exception log corresponds to a page of client 110 and may indicate the occurrence of an exception event. Therefore, through the exception log and the page corresponding to the exception log, the page can be determined to have the exception event indicated by the exception log. Wherein, the abnormal event can be an abnormal event when a user browses or operates a page, such as a page element (picture or script) loading abnormality, a page interaction logic abnormality and the like. The invention is not limited to the specific type and content of the exception event.
Then, in step S320, based on the log information, the number of abnormal logs of the page corresponding to the service object in the predetermined time period is counted. The length of the predetermined time period may be specifically set according to specific situations, and may be set to several seconds or several minutes, for example.
Specifically, the page corresponding to the service object may be determined according to the page corresponding to the abnormal log. And then counting the number of the abnormal logs of the page corresponding to the business object. The number of the abnormal logs of the page corresponding to the business object can describe the number of the abnormal events of the page corresponding to the business object.
Finally, in step S330, it is determined whether to issue an early warning based on the number of abnormal logs of the page corresponding to the service object in the predetermined time period and the access amount of the page corresponding to the service object in the predetermined time period.
According to an embodiment of the present invention, before step S330, the access amount (Page View) of the Page corresponding to the service object in a predetermined time period may be counted.
After the access amount of the page corresponding to the service object in the predetermined time period is obtained through statistics, in some embodiments, the abnormal ratio of the service object in the predetermined time period may be calculated according to the number of the abnormal logs of the page corresponding to the service object in the predetermined time period and the access amount of the page corresponding to the service object in the predetermined time period. Then, whether to send out an early warning is judged based on the abnormal rate of the business object. It can be understood that the exception rate of the business object can describe the rate of the exception event occurring on the page corresponding to the business object.
In some embodiments, the abnormal log number of the page corresponding to the service object in the predetermined time period obtained by statistics is divided by the access amount of the page corresponding to the service object in the predetermined time period, so that the abnormal ratio of the service object can be obtained.
It should be noted that the business object may be a single business object or a plurality of business objects. That is, a single business object may be monitored, or multiple business objects may be monitored simultaneously.
In addition, since the abnormal events can have multiple types, the business object can be monitored for a certain type or multiple types of abnormal events.
According to one embodiment of the invention, the exception rate of a business object may be an exception rate of the business object for at least one type of exception event. Specifically, the number of abnormal logs indicating at least one type of abnormal event of the page corresponding to the service object in the predetermined time period may be counted, and then the abnormal ratio of the service object to the at least one type of abnormal event in the predetermined time period may be calculated according to the number of abnormal logs indicating the at least one type of abnormal event of the page corresponding to the service object in the predetermined time period and the access amount of the page corresponding to the service object in the predetermined time period. And finally, judging whether to send out early warning or not based on the abnormal rate of the business object to at least one type of abnormal event. The exception rate of the business object for at least one type of exception event may describe a rate of the at least one type of exception event occurring on a page corresponding to the business object.
For example, it is necessary to monitor the occurrence of two types of abnormal events, i.e. a picture loading error and a script loading error, in a business object. Therefore, the abnormal logs indicating the picture loading error and the script loading error of the page corresponding to the business object in the preset time period are determined, and the number of the abnormal logs is counted. And then, calculating the abnormal ratio of the business object to the picture loading error and the script loading error in a preset time period, and judging whether to send out an early warning or not based on the abnormal ratio.
After the abnormal rate of the business objects in the predetermined time period is calculated, the abnormal rate of the business objects in the predetermined time period can be compared with the corresponding historical mean value and/or the predetermined threshold value, and whether to send out an early warning is judged based on the comparison result.
Generally, the abnormal logs in a plurality of predetermined time periods can be collected continuously or discontinuously to calculate the abnormal rate of the business objects in each predetermined time period. For example, the anomaly rate of the business objects within 5 minutes may be calculated every 5 minutes. Thus, the respective historical averages may be calculated based on the abnormality ratios for the respective predetermined time periods prior to the current predetermined time period. The respective predetermined threshold may then be set based on the respective historical mean.
It can be understood that, under normal conditions, the abnormal rate of the business objects for the same kind of abnormal events in each predetermined time period should be consistent. Therefore, in some embodiments, if the variance of the anomaly rate of the business object compared to the corresponding historical mean and/or the predetermined threshold is greater than the predetermined variance threshold, an early warning is issued. And if the change is not greater than the preset change threshold, not giving out early warning.
According to another embodiment of the present invention, the abnormal ratio of the business object in the predetermined time period may be compared with the abnormal ratio of the business object in the previous predetermined time period, and whether to issue an early warning may be determined based on the comparison result. And if the change value of the abnormal ratio of the business object in the preset time period compared with the abnormal ratio of the business object in the previous preset time period is larger than a preset change threshold value, giving an early warning. And if the change is not greater than the preset change threshold, not giving out early warning.
In some embodiments, in the case of determining to send out the warning, the responsible party of the business object may be determined first, and then the warning may be sent out to the responsible party. The warning may include information about the business object regarding the rate of anomalies. Wherein the warning can be sent out through various sending channels, such as a communication number, instant communication software or mail, and the like. The invention does not limit the sending channel of the early warning.
Of course, besides the monitoring and early warning on the dimensionality of the business object, the monitoring and early warning can also be carried out on the dimensionality of the page, so that the dimensionality of the business object and the dimensionality of the page can be mutually adjudged and combined, and the accuracy and the reliability of early warning are improved.
According to the embodiment of the invention, aiming at the page of the client, the number of the abnormal logs of the page in the preset time period can be counted based on the log information, and whether to send out the early warning is judged based on the number of the abnormal logs of the page and the access amount of the page in the preset time period.
Specifically, the anomaly rate of the page in the predetermined time period can be calculated according to the number of the anomaly logs of the page in the predetermined time period and the access amount of the page in the predetermined time period. The exception rate for a page may describe the rate at which exceptions occur to the page. Then, whether to send out an early warning is judged based on the abnormal rate of the page.
In some embodiments, the counted number of the exception logs of the page in the predetermined time period is divided by the access amount of the page in the predetermined time period, so that the exception rate of the page in the predetermined time period can be obtained.
It should be noted that the above-mentioned page may be a single page or may be a plurality of pages. That is, the exception of a single page may be monitored, or the exceptions of multiple pages may be monitored simultaneously.
In addition, similar to the business object dimension, since the exception events may have multiple types, the page may also be monitored for one or more types of exception events.
According to one embodiment of the invention, the exception rate for a page may be an exception rate for the page for at least one type of exception event. Specifically, the number of the abnormal logs indicating at least one type of abnormal event of the page in the predetermined time period may be counted, and then the abnormal ratio of the page in the predetermined time period to the at least one type of abnormal event may be calculated according to the number of the abnormal logs indicating the at least one type of abnormal event of the page in the predetermined time period and the access amount of the page in the predetermined time period. And finally, judging whether to send out early warning or not based on the abnormal rate of the page aiming at least one type of abnormal event. The exception rate for a page for at least one type of exception event may describe a rate at which the page occurs for the at least one type of exception event.
For example, it is necessary to monitor the situation of a page with two types of abnormal events, i.e. a picture loading error and a script loading error. Therefore, the abnormal logs indicating the picture loading errors and the script loading errors of the page within a predetermined time period are determined, and the number of the abnormal logs is counted. And then, calculating the abnormal ratio of the page to the picture loading error and the script loading error in a preset time period, and judging whether to send out an early warning or not based on the abnormal ratio.
After the abnormal rate of the page within the preset time period is obtained, the abnormal rate of the page can be compared with the corresponding historical mean value and/or the preset threshold value, and whether to send out the early warning is judged based on the comparison result.
Generally, the abnormality logs in a plurality of predetermined time periods may be collected continuously or discontinuously to calculate the abnormality ratio of the page in each predetermined time period. For example, the anomaly rate of pages within 5 minutes may be calculated every 5 minutes. Thus, the corresponding historical mean may be calculated based on the anomaly rates for the pages for each predetermined time period prior to the current predetermined time period. The respective predetermined threshold may then be set based on the respective historical mean.
It will be appreciated that, under normal circumstances, the exception rates of pages with respect to homogeneous exception events within respective predetermined time periods should tend to be consistent. Thus, in some embodiments, if the variance of the anomaly rate of the page from the corresponding historical mean and/or predetermined threshold is greater than a predetermined variance threshold, an early warning is issued. And if the change is not greater than the preset change threshold, not giving out early warning.
According to another embodiment of the invention, the abnormal ratio of the page in the predetermined time period can be compared with the abnormal ratio of the page in the previous predetermined time period, and whether to give out the early warning or not can be judged based on the comparison result. And if the change value of the abnormal ratio of the page in the preset time period compared with the abnormal ratio of the page in the previous preset time period is larger than a preset change threshold value, giving an early warning. And if the change is not greater than the preset change threshold, not giving out early warning.
The specific process of the page dimension sending out the early warning is similar to the early warning process of the business object dimension described above, and is not described here again.
Fig. 4 is a block diagram illustrating a processing apparatus 400 for client anomaly early warning according to an embodiment of the present invention. As shown in fig. 4, the processing apparatus 400 for client anomaly early warning may include a log obtaining unit 410, a data statistics unit 420, and an early warning judgment unit 430.
The log obtaining unit 410 is adapted to obtain log information reported by the client 110, where the log information includes an abnormal log and a service object corresponding to the abnormal log. In some embodiments, the log information may also include a page corresponding to the exception log. The data statistics unit 420 is connected to the log obtaining unit 410, and is adapted to count the number of abnormal logs of the page corresponding to the service object in the predetermined time period based on the log information. The early warning determining unit 430 is connected to the data counting unit 420, and is adapted to determine whether to issue an early warning based on the number of abnormal logs of the page corresponding to the service object in the predetermined time period and the access amount of the page corresponding to the service object in the predetermined time period.
For the detailed processing logic and implementation process of each unit in the processing 400 for client exception warning, reference may be made to the related description of the processing method 300 for client exception warning in conjunction with fig. 1 to fig. 3, which is not described herein again.
Fig. 5 is a block diagram illustrating a processing method 500 for client anomaly early warning according to an embodiment of the present invention. The processing method 500 of client exception warning may be executed in the processing apparatus 600 of client exception warning. It should be noted that the processing method 500 of client exception warning monitors and warns the client 110 in the page dimension in a manner that is less intrusive to the client 110 code logic.
As shown in fig. 5, the processing method 500 of client anomaly early warning starts in step S510. In step S510, the obtaining client 110 obtains log information reported by the client, where the log information includes an abnormal log. The exception log corresponds to a page of the client 110 and may indicate the occurrence of an exception event. Then, in step 520, the number of abnormal logs of the page in a predetermined time period is counted based on the log information. Finally, in step S530, it is determined whether to issue an early warning based on the number of the abnormal logs of the page in the predetermined time period and the access amount of the page in the predetermined time period.
For detailed processing logic and implementation procedures of each step in the processing method 500 for client exception warning, reference may be made to the related description of the processing method 300 for client exception warning in conjunction with fig. 1 to 3, and details are not repeated herein.
Accordingly, fig. 6 shows a block diagram of a processing apparatus 600 for client anomaly early warning according to an embodiment of the present invention. As shown in fig. 6, the processing device 600 for client anomaly early warning may include a log obtaining unit 610, a data statistics unit 620, and an early warning judgment unit 630.
The log obtaining unit 610 is adapted to obtain log information reported by the client 110, where the log information includes an abnormal log. The data statistics unit 620 is connected to the log obtaining unit 610 and is adapted to count the number of abnormal logs of the page in a predetermined time period based on the log information. The early warning determination unit 630 is connected to the data statistics unit 620, and is adapted to determine whether to issue an early warning based on the number of abnormal logs of the page in a predetermined time period and the access amount of the page in the predetermined time period.
For the detailed processing logic and implementation process of each unit in the processing apparatus 600 for client exception warning, reference may be made to the related description of the processing method 300 for client exception warning in conjunction with fig. 1 to 3, which is not described herein again.
In summary, according to the processing scheme of client exception warning in the embodiment of the present invention, the exception log corresponds to the page, so that the intrusiveness on the link logic of the client is greatly reduced. And the client monitoring and early warning on the service object dimension are realized through the abnormal log corresponding to the service object. In addition, the method can also monitor and early warn in the page dimension, so that the service object dimension and the page dimension can be mutually proved and combined, and the accuracy and the reliability of early warning are improved.
The abnormal quantity can be normalized by monitoring the abnormal ratio rather than the abnormal quantity, so that the inaccuracy of judgment from the quantity change is avoided, and the accuracy and the reliability of early warning are further improved.
It should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in a device as described in this embodiment or alternatively may be located in one or more devices different from the devices in this example. The modules in the foregoing examples may be combined into one module or may be further divided into multiple sub-modules.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
Furthermore, some of the described embodiments are described herein as a method or combination of method elements that can be performed by a processor of a computer system or by other means of performing the described functions. A processor having the necessary instructions for carrying out the method or method elements thus forms a means for carrying out the method or method elements. Further, the elements of the apparatus embodiments described herein are examples of the following apparatus: the apparatus is used to implement the functions performed by the elements for the purpose of carrying out the invention.
As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.
While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this description, will appreciate that other embodiments can be devised which do not depart from the scope of the invention as described herein. Furthermore, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter. Accordingly, many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the appended claims. The present invention has been disclosed in an illustrative rather than a restrictive sense, and the scope of the present invention is defined by the appended claims.
Claims (16)
1. A processing method for client exception early warning comprises the following steps:
acquiring log information reported by a client, wherein the log information comprises an abnormal log and a service object corresponding to the abnormal log;
counting the number of abnormal logs of the corresponding page of the business object in a preset time period based on the log information; and
and judging whether to send out early warning or not based on the number of the abnormal logs and the access quantity of the page corresponding to the business object in the preset time period.
2. The method of claim 1, further comprising:
determining a page corresponding to the business object according to a page corresponding to the abnormal log; and
and counting the access amount of the page corresponding to the business object in the preset time period.
3. The method of claim 1, wherein the step of determining whether to issue an early warning based on the number of the abnormal logs and the access amount of the page corresponding to the business object in the predetermined time period comprises:
calculating the abnormal ratio of the business object in the preset time period according to the number of the abnormal logs and the access amount of the page corresponding to the business object in the preset time period;
and judging whether to send out early warning or not based on the abnormal rate of the business objects.
4. The method of claim 1, further comprising:
counting the number of abnormal logs of the page in the preset time period based on the log information;
and judging whether to send out early warning or not based on the number of the abnormal logs of the page and the access amount of the page in the preset time period.
5. The method of claim 4, wherein the step of determining whether to issue an early warning based on the number of abnormal logs of the page and the access amount of the page within the predetermined period of time comprises:
calculating the abnormal ratio of the page in the preset time period according to the number of the abnormal logs of the page and the access amount of the page in the preset time period;
and judging whether to send out early warning or not based on the abnormal rate of the page.
6. The method of claim 3 or 5, wherein the step of determining whether to issue an early warning based on the abnormal ratio of the business object or the page comprises:
comparing the abnormal rate of the business object or the page with a corresponding historical mean value and/or a preset threshold value;
and if the variation value of the abnormal ratio of the business object or the page compared with the corresponding historical mean value and/or the preset threshold value is larger than the preset variation threshold value, giving out an early warning.
7. The method as claimed in claim 3, wherein the exception log indicates the occurrence of an exception event, the exception rate of the business object includes the exception rate of the business object for at least one type of exception event, and the step of counting the number of exception logs of the corresponding page of the business object in a predetermined time period includes:
and counting the number of the abnormal logs indicating the at least one type of abnormal events of the pages corresponding to the business objects in a preset time period.
8. The method of claim 5, wherein the exception log indicates the occurrence of an exception event, the exception rate for the page comprises an exception rate for the page for at least one type of exception event, and the step of counting the number of exception logs for the page within the predetermined time period comprises:
and counting the number of the abnormal logs of the page in the preset time period, which indicate the at least one type of abnormal events.
9. The method of claim 6, the step of issuing an early warning comprising:
determining a responsible party of the business object or the page;
and sending an early warning to the responsible party.
10. The method of claim 9, wherein the step of issuing an early warning comprises:
the warning is sent out through a communication number, instant messaging software or a mail.
11. A processing method for client exception early warning comprises the following steps:
acquiring log information reported by a client, wherein the log information comprises an abnormal log;
counting the number of abnormal logs of the page in a preset time period based on the log information;
and judging whether to send out early warning or not based on the number of the abnormal logs of the page and the access amount of the page in the preset time period.
12. A processing device for client exception early warning comprises:
the log obtaining unit is suitable for obtaining log information reported by a client, wherein the log information comprises an abnormal log and a service object corresponding to the abnormal log;
the data statistics unit is suitable for counting the number of abnormal logs of the page corresponding to the business object in a preset time period based on the log information; and
and the early warning judging unit is suitable for judging whether to send out early warning or not based on the number of the abnormal logs and the access quantity of the page corresponding to the business object in the preset time period.
13. A processing device for client exception early warning comprises:
the log obtaining unit is suitable for obtaining log information reported by a client, wherein the log information comprises an abnormal log;
the data counting unit is suitable for counting the number of abnormal logs of the page in a preset time period based on the log information; and
and the early warning judging unit is suitable for judging whether to send out early warning or not based on the number of the abnormal logs of the page and the access amount of the page in the preset time period.
14. A processing system for client exception warning, comprising a client and a server, wherein the server resides in the processing device for client exception warning as claimed in claim 12 or 13, wherein
The client is suitable for providing a page; the method is also suitable for acquiring an abnormal log and establishing a corresponding relation between the abnormal log and the current page of the client; and the method is also suitable for sending log information to the server, wherein the log information comprises an abnormal log, a service object corresponding to the abnormal log and a page corresponding to the abnormal log.
15. A computing device, comprising:
one or more processors; and
a memory;
one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing any of the methods of handling client anomaly alerts of claims 1-11.
16. A computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a computing device, cause the computing device to perform any of the methods of handling client anomaly alerts of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910492629.5A CN112054915B (en) | 2019-06-06 | 2019-06-06 | Processing method, device and system for client exception pre-warning and computing equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910492629.5A CN112054915B (en) | 2019-06-06 | 2019-06-06 | Processing method, device and system for client exception pre-warning and computing equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112054915A true CN112054915A (en) | 2020-12-08 |
| CN112054915B CN112054915B (en) | 2023-10-03 |
Family
ID=73608682
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910492629.5A Active CN112054915B (en) | 2019-06-06 | 2019-06-06 | Processing method, device and system for client exception pre-warning and computing equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112054915B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113127319A (en) * | 2021-04-06 | 2021-07-16 | 北京大米科技有限公司 | Information monitoring method, related device and computer storage medium |
| CN113746703A (en) * | 2021-09-03 | 2021-12-03 | 上海众源网络有限公司 | Abnormal link monitoring method, system and device |
| CN114168880A (en) * | 2021-11-30 | 2022-03-11 | 北京达佳互联信息技术有限公司 | Webpage state determination method, device, equipment and storage medium |
| CN115982703A (en) * | 2023-03-22 | 2023-04-18 | 新兴际华集团财务有限公司 | User behavior data processing method and device, electronic equipment and computer readable medium |
| CN116846782A (en) * | 2023-08-31 | 2023-10-03 | 北京仁科互动网络技术有限公司 | Business anomaly observation method and device for mobile terminal of SAAS CRM system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102752141A (en) * | 2012-06-29 | 2012-10-24 | 杭州迪普科技有限公司 | Method and device for detecting accessibility of IP (internet protocol) address |
| CN105468765A (en) * | 2015-12-03 | 2016-04-06 | 中国南方电网有限责任公司信息中心 | Multi-node web service anomaly detection method and system |
| CN107423194A (en) * | 2017-06-30 | 2017-12-01 | 阿里巴巴集团控股有限公司 | Front end abnormality alarming processing method, apparatus and system |
| CN107979477A (en) * | 2016-10-21 | 2018-05-01 | 苏宁云商集团股份有限公司 | A kind of method and system of business monitoring |
| CN108900339A (en) * | 2018-07-02 | 2018-11-27 | 阿里巴巴集团控股有限公司 | A kind of method, apparatus and electronic equipment for measuring quality of service |
-
2019
- 2019-06-06 CN CN201910492629.5A patent/CN112054915B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102752141A (en) * | 2012-06-29 | 2012-10-24 | 杭州迪普科技有限公司 | Method and device for detecting accessibility of IP (internet protocol) address |
| CN105468765A (en) * | 2015-12-03 | 2016-04-06 | 中国南方电网有限责任公司信息中心 | Multi-node web service anomaly detection method and system |
| CN107979477A (en) * | 2016-10-21 | 2018-05-01 | 苏宁云商集团股份有限公司 | A kind of method and system of business monitoring |
| CN107423194A (en) * | 2017-06-30 | 2017-12-01 | 阿里巴巴集团控股有限公司 | Front end abnormality alarming processing method, apparatus and system |
| CN108900339A (en) * | 2018-07-02 | 2018-11-27 | 阿里巴巴集团控股有限公司 | A kind of method, apparatus and electronic equipment for measuring quality of service |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113127319A (en) * | 2021-04-06 | 2021-07-16 | 北京大米科技有限公司 | Information monitoring method, related device and computer storage medium |
| CN113746703A (en) * | 2021-09-03 | 2021-12-03 | 上海众源网络有限公司 | Abnormal link monitoring method, system and device |
| CN114168880A (en) * | 2021-11-30 | 2022-03-11 | 北京达佳互联信息技术有限公司 | Webpage state determination method, device, equipment and storage medium |
| CN115982703A (en) * | 2023-03-22 | 2023-04-18 | 新兴际华集团财务有限公司 | User behavior data processing method and device, electronic equipment and computer readable medium |
| CN116846782A (en) * | 2023-08-31 | 2023-10-03 | 北京仁科互动网络技术有限公司 | Business anomaly observation method and device for mobile terminal of SAAS CRM system |
| CN116846782B (en) * | 2023-08-31 | 2024-01-02 | 北京仁科互动网络技术有限公司 | Business anomaly observation method and device for mobile terminal of SAAS CRM system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112054915B (en) | 2023-10-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112054915A (en) | Processing method, device and system for client abnormity early warning and computing equipment | |
| CN110377569B (en) | Log monitoring method, device, computer equipment and storage medium | |
| US7904460B2 (en) | Determining computer information from processor properties | |
| US10171335B2 (en) | Analysis of site speed performance anomalies caused by server-side issues | |
| US9672242B2 (en) | System for automatically detecting abnormalities statistical data on usage, method therefor, and apparatus applied to same | |
| US10263833B2 (en) | Root cause investigation of site speed performance anomalies | |
| CN111078140B (en) | Nuclear power station file uploading management method and device, terminal equipment and medium | |
| US7610172B2 (en) | Method and system for monitoring non-occurring events | |
| CN111385148A (en) | Service alarm method, device, computer equipment and storage medium | |
| CN113489713A (en) | Network attack detection method, device, equipment and storage medium | |
| CN110941530B (en) | Method, device, computer equipment and storage medium for acquiring monitoring data | |
| US10073726B2 (en) | Detection of outage in cloud based service using usage data based error signals | |
| CN108241744A (en) | A kind of log read method and apparatus | |
| CN112270541A (en) | Transaction wind control management method, device, equipment and system | |
| US10504026B2 (en) | Statistical detection of site speed performance anomalies | |
| CN114996103A (en) | Page abnormity detection method and device, electronic equipment and storage medium | |
| CN110457255B (en) | Method, server and computer readable storage medium for archiving data | |
| CN109491733B (en) | Interface display method based on visualization and related equipment | |
| CN114595765A (en) | Data processing method and device, electronic equipment and storage medium | |
| CN114579446A (en) | Data processing method and device, computer equipment and computer readable storage medium | |
| CN116107789A (en) | Method for monitoring and analyzing application fault reasons and storage medium | |
| CN113708986B (en) | Server monitoring apparatus, method and computer-readable storage medium | |
| CN108111328B (en) | Exception handling method and device | |
| CN112130944A (en) | Page abnormity detection method, device, equipment and storage medium | |
| US20120173495A1 (en) | Computer Readable Medium, Systems, and Methods of Detecting a Discrepancy in a Chain-of-title of an Asset |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20230721 Address after: No. 699, Wangshang Road, Binjiang District, Hangzhou, Zhejiang Applicant after: Alibaba (China) Network Technology Co.,Ltd. Address before: Grand Cayman capital building, a mailbox four / 847 Applicant before: ALIBABA GROUP HOLDING Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |