Fault analysis method and device based on burying point data and electronic equipment

Through the fault analysis method based on buried point data, the buried point event data is used for classification and visualization, the problems of low efficiency and poor accuracy of software fault analysis are solved, and intuitive fault cause analysis is realized, which improves analysis efficiency and accuracy.

CN119066461APending Publication Date: 2024-12-03TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310645375.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-31
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

The prior art is inefficient in software failure analysis and the analysis results are inaccurate, which requires a deep understanding of the source code, which affects the efficiency and accuracy of problem positioning.

Method used

The fault analysis method based on buried point data is adopted. By receiving and classifying buried point event data, the target data of abnormal devices is filtered and converted into visual graphics to visualize the cause of the fault.

Benefits of technology

Improves the efficiency and accuracy of fault analysis and reduces the dependence on professional knowledge, and non-R&D personnel can quickly locate the cause of the problem through visualization images.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119066461A_ABST
    Figure CN119066461A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a fault analysis method and device based on burying point data and electronic equipment, and relates to the technical field of computers.The method comprises the steps that burying point event data reported when a preset burying point is triggered within a specified time range are received, and the burying point event data are divided into classified event data of different categories; according to the abnormal equipment and the equipment serial number corresponding to the burying point event data, screening out target burying point event data corresponding to the abnormal equipment in each classification event data; and according to the time sequence corresponding to the target burying point event data, converting the target burying point event data in each category classification event data into a visual graph, obtaining a visual image corresponding to the abnormal equipment, and determining a fault reason of the abnormal equipment based on the visual image. By utilizing the technical scheme provided by the specification, the computer software exception reason is visually analyzed, and the data processing efficiency and the fault reason analysis accuracy are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a fault analysis method, device and electronic equipment based on buried point data. Background Art

[0002] With the development of computer Internet technology, computer software is used more and more frequently in people's lives and work, which greatly facilitates people's work and life. However, computer software may also have some faults during use. General computer software faults can be discovered through detection alarms or user feedback. However, after discovering the problem, it is generally necessary to analyze the cause of the fault in order to solve the problem in a targeted manner or prevent the problem from happening again.

[0003] Usually, after a fault is discovered, the faulty device will be identified first, and then the specific cause of the faulty device will be analyzed. However, for the analysis of the cause of the fault, after locating the abnormal device, it is still necessary to use information such as device logs and system operation records to determine the direct cause of the device problem. This analysis method requires R&D personnel to have a source code level understanding of the corresponding module, and combined with reading the code, they can understand the log content and locate the cause of the problem. Not only is the process cumbersome and affects the efficiency of problem analysis, but this method also requires a high level of professionalism from the problem analyst, and the accuracy of the analysis results cannot be guaranteed.

[0004] How to improve the efficiency and accuracy of software problem analysis is a technical problem that needs to be solved urgently in this field. Summary of the invention

[0005] The embodiments of this specification provide a fault analysis method, apparatus, device, storage medium, and computer program product based on buried point data, which can realize visual analysis of the causes of computer software anomalies and improve the efficiency and accuracy of fault cause analysis.

[0006] On the one hand, an embodiment of this specification provides a fault analysis method based on buried point data, the method comprising:

[0007] Receive the tracking event data reported when the preset tracking point is triggered within the specified time range;

[0008] According to the event category corresponding to each buried event data, each buried event data is divided into classified event data of different categories;

[0009] According to the predetermined abnormal device and the device serial number corresponding to the buried event data, the target buried event data corresponding to the abnormal device in each classified event data is filtered out;

[0010] According to the time series corresponding to the target buried point event data, the target buried point event data in each category of classified event data is converted into a visualization graphic, and a visualization image corresponding to the abnormal device is obtained, so as to determine the failure cause of the abnormal device based on the visualization image; the visualization image includes the visualization graphics corresponding to the target buried point event data in each category of classified event data.

[0011] On the other hand, a fault analysis device based on buried point data is provided, the device comprising:

[0012] The data collection module is used to receive the buried point event data reported when the preset buried point is triggered within the specified time range;

[0013] A data classification module is used to classify each buried event data into classified event data of different categories according to the event category corresponding to each buried event data;

[0014] A data screening module, used to screen out target buried event data corresponding to the abnormal device in each classified event data according to the predetermined abnormal device and the device serial number corresponding to the buried event data;

[0015] A visualization module is used to convert the target buried event data in each category of classified event data into a visualization graphic according to the time series corresponding to the target buried event data, obtain a visualization image corresponding to the abnormal device, and determine the cause of the failure of the abnormal device based on the visualization image; the visualization image includes the visualization graphics corresponding to the target buried event data in each category of classified event data.

[0016] On the other hand, in some embodiments of this specification, the data classification module is specifically used for:

[0017] After receiving the buried event data, calling the pre-created classification reporting component to determine the label corresponding to each buried event data; the classification reporting component defines a method for determining the label of the buried event data according to the event category;

[0018] Classify each buried event data into different categories of classified event data according to the labels corresponding to each buried event data;

[0019] The visualization module is also used to display the label of the classified event data to which the target buried point event data corresponding to each visualization graphic in the visualization image belongs on the corresponding visualization graphic.

[0020] On the other hand, in some embodiments of the present specification, the classification reporting component further defines a method for determining event attributes and event names of buried event data. When calling a pre-created classification reporting component to determine the labels corresponding to each buried event data, the classification reporting component is also used to:

[0021] Call the classification reporting component to determine the event attributes and event names corresponding to each buried event data;

[0022] When converting the target buried point event data in each category classification event data into a visual graph, the event attributes and event names corresponding to each target buried point event data are added as hidden information to the corresponding visual graph;

[0023] When a designated operation is performed on the visual graphic, the hidden information corresponding to the visual graphic is displayed at a corresponding position of the visual graphic.

[0024] On the other hand, in some embodiments of this specification, the classification reporting component is specifically used for:

[0025] The classification reporting component is called in a chain calling manner to determine the label, event attribute and event name corresponding to each buried event data.

[0026] On the other hand, in some embodiments of this specification, the visualization module is specifically used for:

[0027] According to the timestamp corresponding to the target buried point event data in the classified event data, the target buried point event data in the classified event data of different categories are clustered according to the preset time range, and the target buried point event data in each category of the classified event data obtains multiple clustered event data;

[0028] According to the time series corresponding to the multiple clustered event data in each category of the classified event data, the target buried event data in each category of the classified event data is converted into a visual graph.

[0029] On the other hand, in some embodiments of this specification, the visualization module is specifically used for:

[0030] Convert the text format data of the target buried point event data in each category classification event data into a text graphic description language format file according to the time series;

[0031] The text graphic description language format file of the target buried point event data in each category classification event data is converted into a scalable vector graphic or a hypertext markup language graphic.

[0032] Another aspect provides an electronic device, including: a processor;

[0033] a memory for storing instructions executable by the processor;

[0034] Among them, the processor is configured to execute the instructions to implement any of the above-mentioned fault analysis methods based on buried point data.

[0035] On the other hand, a computer-readable storage medium is provided. When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute any of the above-mentioned fault analysis methods based on buried point data.

[0036] On the other hand, a computer program product or a computer program is provided, the computer program product or the computer program includes computer instructions, the computer instructions are stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the fault analysis method based on buried point data provided in the above various optional implementations.

[0037] The fault analysis method, device, equipment, storage medium, and computer program product based on buried point data provided by the embodiments of this specification have the following technical effects:

[0038] The fault analysis method based on buried point data provided in the embodiment of this specification uses preset buried points to collect buried point event data, and classifies and processes the buried point event data, extracts the target buried point data belonging to abnormal devices in each type of buried point event data, and then draws corresponding visualization graphics for each type of target buried point data with time as the horizontal axis. Display the visualization graphics corresponding to different types of target buried point data on an image to obtain a visualization image corresponding to the abnormal device. Different visualization graphics on the visualization image correspond to an event category, and visualization graphics corresponding to multiple time axes of the abnormal device can be obtained on the visualization image. By intuitively seeing the changes of different types of buried point event data of abnormal devices over time on the visualization image, the cause of the problem of the abnormal device can be quickly analyzed based on the multiple visualization graphics in the visualization image, thereby improving the efficiency of fault analysis. In addition, the entire process does not require the analysis of the log data of the abnormal device, and the visualization of the abnormal device data can be realized directly by using the event data reported by the preset buried point. The operation is simple, the visualization graphics are relatively intuitive, and there is no need to rely on professional knowledge, which improves the accuracy of fault analysis. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions and advantages in the embodiments of this specification or the prior art, the drawings required for use in the embodiments or the prior art descriptions are briefly introduced below. Obviously, the drawings described below are only some embodiments of this specification. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0040] Figure 1 What is shown is only an application environment of a fault analysis method based on buried point data;

[0041] Figure 2 This is a schematic diagram of abnormal conversion rate data comparison in a scenario example of this manual;

[0042] Figure 3 This is a schematic diagram of abnormal HID spitting data in a scenario example of this manual;

[0043] Figure 4 This is a schematic diagram of the number of abnormal sessions of abnormal devices in a scenario example of this manual;

[0044] Figure 5 It is a flowchart of a fault analysis method based on buried point data provided by an embodiment of this specification;

[0045] Figure 6 It is a flowchart of data filtering based on the label of buried event data in one embodiment of this specification;

[0046] Figure 7 is a schematic diagram of an interface of a visualization process in one embodiment of this specification;

[0047] Figure 8 is a schematic diagram of a fault analysis process based on buried point data in another embodiment of this specification;

[0048] Fig. 9 It is a structural schematic diagram of a fault analysis device based on buried point data provided in an embodiment of this specification;

[0049] Fig.10 It is a block diagram of an electronic device for fault analysis based on buried point data provided by an embodiment of this specification;

[0050] Fig.11 It is a block diagram of another electronic device for fault analysis based on buried point data provided in an embodiment of this specification. DETAILED DESCRIPTION

[0051] The following will be combined with the drawings in the embodiments of this specification to clearly and completely describe the technical solutions in the embodiments of this specification. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this specification.

[0052] It should be noted that the terms "first", "second", etc. in the description and claims of the embodiments of this specification and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of this specification described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0053] See also Figure 1 , Figure 1 It is a schematic diagram of an application environment of a fault analysis method based on buried point data provided in an embodiment of this specification, and the application environment may include at least a server 100 and a terminal 200.

[0054] In an optional embodiment, server 100 can be used to perform fault analysis and processing based on buried point data. Server 100 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, as well as big data and artificial intelligence platforms.

[0055] In an optional embodiment, the terminal 200 may be a client that sends buried point data or fault information to the server 100. Specifically, the terminal 200 may include but is not limited to smart phones, desktop computers, tablet computers, laptop computers, smart speakers, digital assistants, augmented reality (AR) / virtual reality (VR) devices, smart wearable devices, vehicle terminals, smart TVs and other types of electronic devices; it may also be software running on the above electronic devices, such as applications, applets, etc. The operating system running on the electronic device in the embodiments of this specification may include but is not limited to Android system, IOS system, Linux, Windows, etc.

[0056] In addition, it should be noted that Figure 1 What is shown is merely an application environment of a fault analysis method based on buried point data, and the embodiments of this specification are not limited to the above.

[0057] In the embodiments of this specification, the server 100 and the terminal 200 may be directly or indirectly connected via wired or wireless communication, which is not limited in the embodiments of this specification.

[0058] The fault analysis in the embodiments of this specification can be applied to software problem analysis scenarios, such as: some applications or office software may have some anomalies during use, and the cause of the anomaly can be analyzed using the solution provided in the embodiments of this specification.

[0059] For some computer software, there is usually a detection program that can perform real-time detection on the data of the computer software in daily use, or users can also report abnormal information when encountering an abnormality. Usually, the abnormal indicators can be determined based on the detected data or the data reported by the user, and then the equipment can be drilled down for analysis based on the abnormal indicators to determine the abnormal equipment, and then the cause of the abnormality can be determined by analyzing the log data of the abnormal equipment. Figure 2 This is a schematic diagram of abnormal conversion rate data comparison in a scenario example of this manual, such as Figure 2 As shown in the figure, the detection and alarm system found that the indicator "general abnormal conversion rate" suddenly increased by 40% compared with the comparison day, indicating that a fault occurred and fault analysis is required. "General abnormal conversion rate" is mainly used to describe the occurrence rate of abnormalities. Session in computers, especially in network applications, can be called "session control". For example: Statistics show that in N user sessions, the total number of abnormal events reported is M, then the abnormal occurrence rate is M / N, and the occurrence rate here is often also called conversion rate.

[0060] After discovering a fault, you need to confirm what event reporting surge has led to the abnormal final conversion rate, so as to solve the fault or provide data support for subsequent software maintenance. At this time, you need to switch to the "event id (Identity document)" dimension for drill-down analysis. Figure 3 This is a schematic diagram of abnormal HID spitting data in a scenario example of this manual, such as Figure 3 As shown in the figure, when analyzing different events, it is found that the event of "HID (Human Interface Device) code spitting abnormality" has obvious differences. After confirming the event, drill down analysis is performed on the dimension of "device SN (Serial Number)" to confirm which device has an abnormality that causes the final conversion rate to be abnormal. Figure 4 This is a schematic diagram of the number of abnormal sessions of abnormal devices in a scenario example of this manual, such as Figure 4 As shown, after drilling down and analyzing different devices, it can be determined Figure 4 The number of abnormal sessions of the device in the same day is significantly higher than that of the comparison day, thus determining Figure 4 The device with device SN TXAP11951002994ND002112 is an abnormal device. After identifying the abnormal device, it is necessary to extract the log data of the device according to the device SN and analyze the cause of the problem based on the keywords in the log. As in the above example, the R&D personnel found from the log that the USB of the device was disconnected, causing the device to continuously report errors and eventually trigger an alarm. Among them, the device SN can be used to identify the unique identity of the device.

[0061] It can be seen that the conventional fault analysis process is long, cumbersome, and heavily dependent on the past experience of R&D personnel. After locating the problematic device, it is still necessary to use information such as device logs and system operation records to determine the direct cause of the device problem. This analysis method also requires R&D personnel to have a source code level understanding of the corresponding module, combined with reading the code, in order to understand the log content and locate the cause of the problem. The accuracy of the fault cause analysis cannot be guaranteed.

[0062] The embodiments of this specification provide a fault analysis method based on tracking data. When the business system reports the tracking data, the reported data is classified, and the relevant data of the abnormal equipment is screened out from the data of different categories. Then, for the time series corresponding to the data of the abnormal equipment in the different categories of data, a time axis can be extracted for each category of data, and then multiple time axes are extracted. The data of the abnormal equipment in each category of data is visualized respectively to obtain a visualized image of the abnormal equipment. Based on the visualization graphics corresponding to the different categories in the visualization image, it is easy and intuitive to see which category of data has an abnormality, and then determine the cause of the fault. The efficiency of problem location is improved. The visualized timeline is easier to understand than the highly professional log files. Trained non-R&D professionals can also easily locate the cause of the problem based on the timeline, thereby providing preliminary technical support guidance.

[0063] The following describes a fault analysis method based on buried point data in an embodiment of this specification. Figure 5 This is a flow chart of a fault analysis method based on buried point data provided by an embodiment of this specification. This specification provides method operation steps such as the embodiment or flow chart, but may include more or fewer operation steps based on conventional or non-creative labor. The sequence of steps listed in the embodiment is only one way of executing the steps among many sequences, and does not represent the only execution sequence. When the actual system or server product is executed, it can be executed in sequence or in parallel according to the method shown in the embodiment or the accompanying drawings (for example, in a parallel processor or multi-threaded processing environment). The method can be applied to terminal devices such as computers, tablet computers, and smart phones. Specifically, Figure 5 As shown, the method may include:

[0064] S502: Receive the tracking point event data reported when the preset tracking point is triggered within the specified time range.

[0065] In the specific implementation process, the tracking point can be understood as the relevant technology and implementation process for capturing, processing and sending specific behaviors or business processes. Tracking points are generally used for feedback of recommendation systems, statistics and analysis of operation object behaviors, statistical analysis of new functions or operational activities, etc. Preset tracking points can be set in the business system or client in advance. The technical essence of tracking points is to first detect events in the running process of the software application in real time, judge and capture when events that need attention occur, and then obtain the necessary context information, and finally organize the information and send it to the server. The setting method of the preset tracking point can be determined according to actual business needs. Generally, the preset tracking point can be set to some specific operations, indicators or events, etc., which are not specifically limited in the embodiments of this specification. When the set specific operation or event occurs or a specific indicator appears, etc., it can be considered that the preset tracking point is triggered. Generally, tracking points are set in business systems or applications. The usage of business systems or applications is collected by setting tracking points to provide data support for the operation of business systems and applications.

[0066] When the preset burying point is triggered, the data related to the event that triggered the burying point can be reported. The server or business system receives the reported burying point event data and performs data analysis based on the received burying point event data. Generally, the burying point event data can include user behavior data or device performance data, etc. The specific content of the burying point event data can be determined according to actual needs, such as: it can include the specific operation corresponding to the event, the time when the event occurred, the event name, the page on which the event occurred, etc. The embodiments of this specification do not specifically limit the reported burying point event data. In the embodiments of this specification, the burying point event data received within a specified time range can be analyzed to determine the cause of the fault, where the specified time range can be determined according to actual needs, such as: it can be within a day, a week, or a month, etc. The embodiments of this specification do not specifically limit it.

[0067] S504: Classify each buried point event data into classified event data of different categories according to the event category corresponding to each buried point event data.

[0068] In the specific implementation process, after receiving the reported buried event data, the buried event data can be classified based on the event category. Among them, the event category can be determined according to the specific business scenario, such as: the event category can include behavioral events of the operating object, performance indicator events, environmental factor change events, etc. The embodiments of this specification do not specifically limit the specific types of event categories. In the embodiments of this specification, different categories of buried event data can be processed separately, such as: using different data processing modules to process different categories of buried event data to improve data processing efficiency.

[0069] S506: Filter out target buried event data corresponding to the abnormal device in each classified event data according to the predetermined abnormal device and the device serial number corresponding to the buried event data.

[0070] In the specific implementation process, the fault analysis in the embodiments of this specification is the process of analyzing the cause of the fault after the abnormal device has been determined. The determination of the abnormal device can refer to the description in the above embodiments. After the abnormal indicator is found, the device SN is used as the dimension for drill-down analysis to determine the abnormal device. The specific process is not specifically limited in the embodiments of this specification. After receiving the reported buried event data and classifying the buried event data, the target buried event data corresponding to the abnormal device in each category of the classified event data can be filtered out according to the device serial number corresponding to each category of the classified event data, that is, the device SN.

[0071] Of course, according to business needs, after classifying the buried event data, you can also process several specified classified event data. For example, after classification, if it is determined that some categories of events do not need to be processed, then you can only filter and subsequently visualize the event data belonging to abnormal devices in the specified category of classified event data.

[0072] S508. According to the time series corresponding to the target buried event data, the target buried event data in each category of classified event data is converted into a visualization graphic, and a visualization image corresponding to the abnormal device is obtained, so as to determine the cause of the failure of the abnormal device based on the visualization image; the visualization image includes the visualization graphics corresponding to the target buried event data in each category of classified event data.

[0073] In the specific implementation process, referring to the records of the above embodiments, the buried point event data contains a timestamp. After filtering out the target buried point event data in each category of classified event data, the target buried point event data in each category of classified event data can be converted into a visual graph based on the time series corresponding to the target buried point event data, and then the visual graph corresponding to the target buried point event data in each category of classified event data is drawn on a graph to obtain a visual image. Among them, the specific shape of the visual graph can be selected according to actual needs, such as: a line graph, a bar graph, a pie chart, etc., and different visual graphs can be selected according to specific needs. For example: a line graph or a bar graph can be used to display the time series of the behavior events of the operation object, and a relationship diagram or a tree diagram can be used to display the relationship between events. Data visualization software can be used to convert each category of target buried point data into a visual graph, such as: JavaScript technology can still be used to achieve visualization. Specifically, a JavaScript library such as viz.js can be used to create an interface for graphically displaying the target buried point data, or other methods can be selected to convert the data into a visual graph, which is not specifically limited in the embodiments of this specification. Among them, JavaScript (abbreviated as "JS") is a lightweight, interpreted or just-in-time compiled programming language with function priority. It is a scripting language for developing web pages and is also used in many non-browser environments. JavaScript is a dynamic scripting language based on prototype programming and multiple paradigms, and supports object-oriented, imperative, declarative, and functional programming paradigms.

[0074] Different visualization graphics on the visualization image correspond to an event category respectively, and each visualization graphic can represent the change of relevant data of the abnormal device in the corresponding event category over time. In this way, the visualization graphics corresponding to the event data of different categories of abnormal devices can be seen on the visualization image, and the visualization graphics corresponding to multiple time axes can be obtained. Then, the user can analyze the cause of the problem of the abnormal device based on the multiple visualization graphics that change over time in the visualization image, such as: analyzing the abnormal changes in the visualization graphics corresponding to each category of data at a certain point in time, or comparing whether the change patterns of the visualization graphics corresponding to different categories of data are consistent over time, etc., to analyze the cause of the problem of the abnormal device. The specific analysis method of the abnormal cause can be determined according to the business scenario, and the embodiments of this specification do not make specific limitations.

[0075] In some embodiments of this specification, the classified event data is text format data, and the target embedded event data in each category of the classified event data is converted into a visual graph, including:

[0076] Convert the text format data of the target buried point event data in each category classification event data into a text graphic description language format file according to the time series;

[0077] The text graphic description language format file of the target buried point event data in each category classification event data is converted into a scalable vector graphic or a hypertext markup language graphic.

[0078] In the specific implementation process, after classifying the buried event data, the classified event data can be converted into text format data such as SRT format. Specifically, in some scenario examples, by determining the label corresponding to each buried event data, and classifying the buried event data based on the label to obtain the classified event data, the classified event data with the label can be converted into text format data such as SRT format. Then use the visualization tool to convert the SRT format file into a text graphics description language format file such as DOT language format, and then convert the DOT language format into scalable vector graphics such as SVG or hypertext markup language graphics such as HTML. Among them, SRT is a simple text file format that carries time information; DOT is a text graphics description language that provides a simple way to describe graphics and can be understood by humans and computer programs; SVG (Scalable Vector Graphics) is a scalable vector graphics based on extensible markup language (a subset of standard generalized markup language) for describing two-dimensional vector graphics. A graphics format; HTML is a hypertext markup language, and JavaScript can be used to draw HTML graphics on a web page.

[0079] For example: In one example, two types of classified event data A and B are obtained, and both classified event data A and B are SRT format files. The target buried event data belonging to abnormal devices in classified event data A and classified event data B are screened respectively to obtain target buried event data a in classified event data A and target buried event data b in classified event data B. Target buried event data a and target buried event data b are also SRT files, wherein the SRT files contain timestamps. By using viz.js, the data in the SRT files of target buried event data a and target buried event data b can be converted into DOT language format according to the time series, and then the DOT language of target buried event data a and target buried event data b can be converted into SVG or HTML format graphics through viz.js, so that the time series and event relationship of behavioral event data can be easily displayed. Among them, viz.js is a JavaScript library based on Graphviz, which can convert the DOT language of Graphviz into SVG or HTML format graphics.

[0080] Visualization software is used to automatically convert text-formatted event data into DOT language format, and then convert DOT language into graphics in SVG or HTML format, thereby realizing the visualization of event data of different categories of abnormal equipment, making it convenient for users to analyze the cause of the fault based on graphics, and laying a data foundation for fault analysis.

[0081] In some embodiments of the present specification, the target buried event data in each category classification event data is converted into a visual graph according to the time series corresponding to the target buried event data, including:

[0082] According to the timestamp corresponding to the target buried point event data in the classified event data, the target buried point event data in the classified event data of different categories are clustered according to the preset time range, and the target buried point event data in each category of the classified event data obtains multiple clustered event data;

[0083] According to the time series corresponding to the multiple clustered event data in each category of the classified event data, the target buried event data in each category of the classified event data is converted into a visual graph.

[0084] In the specific implementation process, when visualizing the event data of abnormal devices, the target buried event data belonging to abnormal devices in different categories of classified event data can be clustered according to the preset time range. In this way, each category of classified event data can obtain multiple clustered event data. For example: Assuming that the received buried event data is data reported within a week, before visualization, the target buried event data belonging to abnormal devices in each category of classified event data can be clustered according to days, that is, the target buried event data of the same day in each category of classified event data are clustered into a specific event data. After clustering, the clustered event data in each category of classified event data can be converted into a visualization graph according to the corresponding time series.

[0085] For example, in the classified event data with event category A, when clustering the target buried point event data of abnormal equipment, 7 clustered event data were obtained. These 7 clustered event data correspond to different times, such as: the time corresponding to the first clustered event data is May 1, the time corresponding to the second clustered event data is May 2, and so on. Based on the time series corresponding to these 7 clustered event data, the target buried point data of the abnormal equipment can be converted into corresponding visualization graphics. For example, it can be a line chart or a bar chart, which can represent the changes of the data of event category A of the abnormal equipment over time.

[0086] By clustering the target tracking data of abnormal devices within a category according to a preset time range, multiple clustering event data in time series can be obtained. The clustering event data of each category is then visualized according to the corresponding time series, providing data support for subsequent fault analysis of abnormal devices.

[0087] The fault analysis method based on buried point data provided in the embodiment of this specification uses preset buried points to collect buried point event data, and classifies and processes the buried point event data, extracts the target buried point data belonging to abnormal devices in each type of buried point event data, and then draws corresponding visualization graphics for each type of target buried point data with time as the horizontal axis. Display the visualization graphics corresponding to different types of target buried point data on an image to obtain a visualization image corresponding to the abnormal device. Different visualization graphics on the visualization image correspond to an event category, and visualization graphics corresponding to multiple time axes of the abnormal device can be obtained on the visualization image. By intuitively seeing the changes of different types of buried point event data of abnormal devices over time on the visualization image, the cause of the problem of the abnormal device can be quickly analyzed based on the multiple visualization graphics in the visualization image, thereby improving the efficiency of fault analysis. In addition, the entire process does not require the analysis of the log data of the abnormal device, and the visualization of the abnormal device data can be realized directly by using the event data reported by the preset buried point. The operation is simple, the visualization graphics are relatively intuitive, and there is no need to rely on professional knowledge, which improves the accuracy of fault analysis.

[0088] In some embodiments of the present specification, the classification of each buried event data into different categories of classified event data according to the event category corresponding to each buried event data includes:

[0089] After receiving the buried event data, call the pre-created classification reporting component to determine the label corresponding to each buried event data; the classification reporting component defines a method for determining the label of the buried event data according to the event category;

[0090] Classify each buried event data into different categories of classified event data according to the labels corresponding to each buried event data;

[0091] When obtaining a visual image corresponding to the abnormal device, the method further includes:

[0092] The label of the classified event data to which the target buried point event data corresponding to each visualization graphic in the visualization image belongs is displayed on the corresponding visualization graphic.

[0093] In the specific facility process, in the embodiment of this specification, a classification reporting component such as a code SDK (Software Development Kit) for supporting classification data reporting can be created. The required methods can be defined in the classification reporting component SDK according to business needs, such as defining a method for determining the label of the buried point event data according to the event category. The specific content of the method can be set according to the actual business scenario, and the embodiment of this specification does not make specific restrictions. After receiving the buried point event data reported when the preset buried point is triggered, the interface of the pre-created classification reporting component, that is, the SDK, can be called to call the method defined in the SDK, such as calling the interface in the SDK to call the method for determining the label of the buried point event data according to the event category to determine the label corresponding to the reported buried point event data. Among them, the method for determining the label corresponding to each buried point event data can be set according to the actual business scenario requirements, such as extracting the keywords of the buried point event data, determining the corresponding label based on the keywords, or pre-setting the type of label according to business needs, and then matching the buried point event data with each label to match the corresponding label. Of course, there can be other ways, which are not specifically limited in the embodiment of this specification. Among them, the label determination of the buried point event data can be operated by the client or determined by the server. It can be determined specifically according to the actual business scenario, and the embodiments of this specification do not make specific limitations. After determining the label corresponding to each buried point event data, the label can be added to the field specified by the buried point event data. When classifying the buried point event data, the label corresponding to the buried point event data can be directly obtained from the specified field of the buried point event data. Then classify the buried point event data according to the label corresponding to each buried point event data, such as: classify the buried point event data with the same label into one category. Generally, one buried point event data corresponds to one label. Of course, according to actual needs, one buried point event data can also correspond to multiple labels. When classifying the buried point event data according to the label, if one buried point event data has multiple labels, then the buried point event data can be divided into classified event data of multiple categories.

[0094] Figure 6 FIG. 1 is a flow chart of data filtering based on the label of buried event data in one embodiment of this specification, such as Figure 6 As shown in the figure, when the client receives the buried event data reported within the specified time range, it can report the collected data to the background system. After the background system receives the data, it can first determine the label corresponding to each buried event data, and then pass the data to the parsing module for parsing. The parsing module parses the data into a format that can be processed by the filtering module. The filtering module can classify the buried event data based on the labels corresponding to the parsed data, and assign different categories of data to corresponding modules for subsequent processing. Figure 6 As shown, in a scenario example, three embedded event data are received, the labels of event 1 and event 2 are tagA, and the label of event 3 is tagB. Event 1 and event 2 are assigned as a class to a processing service module for subsequent processing, and event 3 is assigned as a separate class to another processing service module for subsequent processing.

[0095] After classifying the buried event data based on the determined labels, the labels corresponding to each type of classified event data can be displayed on the corresponding visualization graphs during visualization. In this way, users can directly see the visualization graphs corresponding to different labels on the displayed visualization images, and can then intuitively see how the data corresponding to different label categories change over time, facilitating the analysis of the cause of the fault. Figure 7 is a schematic diagram of the interface of the visualization process in one embodiment of this specification, such as Figure 7 As shown, based on the method described in the above embodiment, after visualizing the target buried event data in the classified event data of different categories, it is possible to obtain Figure 7 The visualization is shown on the right. Figure 7 As shown, the visualization image includes multiple visualization graphics. The corresponding label is displayed on the right side of each visualization graphic, such as: on-site photo sequence, performance change, environmental factors, and user operation are all labels of the corresponding visualization graphics. The horizontal axis of each visualization graphic is time. Each visualization graphic can represent the change of event data corresponding to each label of abnormal equipment over time.

[0096] Of course, according to actual business needs, different categories of labels can also be freely combined, and the visual graphics corresponding to the labels can be displayed together. Or according to the correlation between the events corresponding to different labels, the associated classified event data can be combined for visual analysis. For example: if the event data corresponding to label A has a certain correlation with the event data corresponding to label B, the events corresponding to label A and label B can be combined together, and the target buried event data corresponding to label A and label B belonging to abnormal equipment can be converted into visual graphics on a timeline. In other words, the changes of event data of two categories of labels A and label B in abnormal equipment over time can be displayed on a timeline, so as to more clearly show whether there are problems with the change rules of event data corresponding to labels A and B, or whether the abnormality of event data of one label will cause abnormality of events corresponding to another label associated with it. By visually displaying the data corresponding to labels of different categories, the buried data can be visualized more flexibly to better discover potential problems.

[0097] The embodiments of this specification pre-create a classification reporting component. After receiving the buried point data, the component can be directly called to automatically determine the label of the reported buried point event data using the label definition method defined in the component, and then the buried point event data is classified based on the label, thereby providing data support for the subsequent visualization of abnormal device-related data. The entire process does not require manual operation, thereby improving the efficiency of data processing.

[0098] In some embodiments of this specification, the classification reporting component further defines a method for determining event attributes and event names of buried event data. When calling a pre-created classification reporting component to determine a label corresponding to each buried event data, the method further includes:

[0099] Call the classification reporting component to determine the event attributes and event names corresponding to each buried event data;

[0100] When converting the target buried point event data in each category classification event data into a visual graph, the event attributes and event names corresponding to each target buried point event data are added as hidden information to the corresponding visual graph;

[0101] When a specified operation is performed on the visual graphic, the hidden information corresponding to the visual graphic is displayed at the corresponding position of the visual graphic.

[0102] In the specific implementation process, when creating a classification reporting component, not only can the method for determining the label be defined in the component, but also the method for determining the event attribute event name can be defined. Of course, other required methods can also be defined according to actual needs. Among them, the specific definition method and specific content of each method can be determined according to the actual business scenario, and the embodiments of this specification do not make specific limitations. For example: In a scenario instance of this specification, a "Reporter.report" method is defined in the classification reporting component, which can be used for data reporting; a ".withTag("user.behaviour")" method is also defined to be used to determine the tag corresponding to the event data to be reported; a ".withAction("scxml.state.enter")" method is also defined, which can be used to determine the event name of the event to be reported; and a ".withExtKey1("state")" method is also defined, which can be used to determine the event attribute of the event to be reported. Among them, the event name can be understood as the action corresponding to the event, such as: the specific operation of the user, and the event attribute can be understood as the state or identification in the event, etc., which depends on the actual business scenario, and the embodiments of this specification do not make specific limitations. Each event may correspond to multiple event attributes.

[0103] When calling the classification reporting component to determine the label of the reported buried event data, the corresponding method in the classification reporting component can also be called to determine the event attributes and event names of the buried event data. When visualizing the target buried event data of different categories corresponding to the abnormal device, the event attributes and event names can be added as hidden information to the corresponding visualization graphics. When the user performs a specified operation on the visualization graphics, such as clicking a visualization graphic or moving the mouse to the area corresponding to a visualization graphic, the event attributes and event names corresponding to the visualization graphic are displayed at the corresponding position of the visualization graphic for the user to view. In addition, according to the needs of the business scenario, the target buried event data of different categories can be converted into visualization graphics of different time units, and the visualization graphics with a small time unit are hidden as hidden information in the corresponding visualization graphics. When performing some specific operations on the visualization graphics, the visualization graphics corresponding to the more subdivided time axis of the visualization graphics can also be displayed. For example, if the time axis of the visualization graphics corresponding to the original category is in days, when the mouse moves to the graphic area of ​​a certain day in the visualization graphics, the specific details of the visualization graphics of that day can be displayed in hours. Users can analyze the causes of abnormal equipment failures based on the changes of various visualization graphs over time, combined with the event attributes and event names displayed on the visualization graphs, to improve the accuracy of fault analysis results.

[0104] In addition, in some embodiments of this specification, the method further includes:

[0105] The classification reporting component is called in a chain calling manner to determine the label, event attribute and event name corresponding to each buried event data.

[0106] In the specific implementation process, when calling the classification reporting component to determine the label, event attribute and event name corresponding to the buried event data, a chain call method can be used. There is no need for repeated calls, and the event label, attribute and event name can be specified more flexibly to meet the needs of different business scenarios and user needs. At the same time, the code style of using chain calls can also improve the readability and maintainability of the code, and reduce the time and workload of writing code. Chain calls refer to calling multiple methods on an object continuously, and each method call returns the object itself so that the next method can be called. This calling method can complete multiple operations in each statement.

[0107] Figure 8 This is a schematic diagram of a fault analysis process based on buried point data in another embodiment of this specification. Figure 8 The overall process of fault analysis in some embodiments of this specification is specifically described as follows: Figure 8 As shown, in some embodiments of this specification, fault analysis can be mainly divided into four steps:

[0108] 1. According to the event category, select the corresponding appropriate label in the tracking point reporting code;

[0109] 2. After the data is reported to the backend system, the backend will classify, filter and aggregate it according to the tags;

[0110] 3. The backend storage system divides the events of each tag according to the device SN and the events selected by the user, and determines the data of the abnormal devices in the events of each tag;

[0111] 4. Visualize the cut SRT file and present it to the user for analysis.

[0112] Specifically, when determining the label, you can create a classification reporting component SDK to define the label determination method, event attribute determination method, event name determination method, etc., where some of the SDK contents can be referenced as follows:

[0113] Reporter.report(WxPayChainReport.ChainReportBuilder

[0114] .aChainReport()

[0115] .withTag("user.behaviour")

[0116] .withAction("scxml.state.enter")

[0117] .withExtKey1("state")

[0118] .withExtValue1(stateId)

[0119] .withExtKey2("event") ......

[0121] .withExtra(extraString)

[0122] .build());

[0123] The process of calling the above SDK to determine the labels and attributes of the reported events is as follows:

[0124] 1). Call WxPayChainReport.ChainReportBuilder.aChainReport() method to create an event chain object.

[0125] 2). Use the .withTag("user.behaviour") method to specify the tag of the event (Action) to be reported. For example, "user.behaviour" represents the behavior event of the operation object.

[0126] 3). Use the .withAction("scxml.state.enter") method to specify the specific action of the event to be reported. For example, "scxml.state.enter" means entering a state of the state machine.

[0127] 4). Use the .withExtKey1("state") and .withExtValue1(stateId) methods to specify the properties of the event. For example, "state" represents the state of the state machine, and stateId represents the ID of the state.

[0128] 5). Use the .withExtra(extraString) method to specify the extended attributes of the event. For example, extraString can be a JSON string containing more event attributes. By reserving the calling interface of the extended attributes, in case the specified attributes are not enough to meet the actual business needs, users can use this method to allow the business to be freely expanded.

[0129] 6). Use the .build() method to generate the event chain object and call the Reporter.report method to report the data.

[0130] After determining the labels of the reported events, the events can be classified and filtered based on the labels, that is, the events corresponding to different labels are assigned to different data processing modules for processing. The specific process can be found in the records of the above embodiments, which will not be repeated here. The filtering module classifies and organizes the reported data to facilitate subsequent data analysis and marketing activities. At the same time, the filtering module can also improve the processing efficiency and accuracy of the data and reduce unnecessary data transmission and processing.

[0131] After filtering based on tags, you can segment events by device SN. In the reported fields, the default field will include the device SN. The content of the SRT file can be referred to as follows:

[0132] [2022-07-17+8.0 10:12:28.269][onExit]Identity.Main

[0133] [2022-07-17+8.0 10:12:28.273][onEntry]Identity.Done

[0134] [2022-07-17+8.0 10:12:28.292][onExit]Identity.Done

[0135] [2022-07-17+8.0 10:12:28.294][onExit]Identity

[0136] The [2022-07-17+8.0 10:12:28.294] in front is the timestamp of the event. The second [onEntry] and [onExit] can be understood as event names. The above events are codes for behavioral events, representing the entry and exit of the page.

[0137] Events can be classified according to device SN and timestamp. For example, events of the same device (abnormal device) on the same day can be sorted into the same SRT file, which can facilitate subsequent data analysis and problem location, and also improve data processing efficiency and accuracy.

[0138] The SRT file is a data file in text format, which records information such as the timestamp, label, and event name of the event. In order to better understand and analyze event data, a visualization analysis method can be used in the embodiments of this specification to display the data in the SRT file. The specific visualization method can refer to the records in the above embodiments and will not be repeated here.

[0139] The above-mentioned data analysis such as filtering, cutting, clustering, etc. can also use automated anomaly analysis algorithms, such as Adtributor, iDice and HotSpot algorithms, to achieve automatic data analysis.

[0140] From the above content, it can be seen that the fault analysis based on the buried data provided by the embodiments of this specification can automatically extract several key timelines related to the problem from the data according to the buried data actively reported by the equipment in real time, and then perform visual analysis on the timeline to improve the efficiency of problem location. In addition, the visualized timeline is easier to understand than the highly professional log files. Trained non-R&D professionals can also easily locate the cause of the problem based on the timeline, thereby providing preliminary technical support guidance and improving the accuracy of fault analysis.

[0141] Based on the above-mentioned fault analysis method based on buried point data, one or more embodiments of this specification also provide a client and server for fault analysis processing based on buried point data. The client and server may include devices (including distributed systems), software (applications), modules, components, servers, clients, etc. that use the methods described in the embodiments of this specification and are combined with necessary implementation hardware. Based on the same innovative concept, the devices in one or more embodiments provided in the embodiments of this specification are as described in the following embodiments. Since the implementation scheme and method of the device to solve the problem are similar, the implementation of the specific device in the embodiments of this specification can refer to the implementation of the aforementioned method, and the repetitions will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements predetermined functions. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0142] It can be seen from the technical solutions provided in the above embodiments of this specification that the embodiments of this specification also provide a fault analysis device based on buried point data. Fig. 9 is a structural diagram of a fault analysis device based on buried point data provided by an embodiment of this specification, such as Fig. 9 As shown, the above device comprises:

[0143] The data collection module 910 is used to receive the buried point event data reported when the preset buried point is triggered within a specified time range;

[0144] The data classification module 920 is used to classify each buried event data into classified event data of different categories according to the event category corresponding to each buried event data;

[0145] The data screening module 930 is used to screen out target buried event data corresponding to the abnormal device in each classified event data according to the predetermined abnormal device and the device serial number corresponding to the buried event data;

[0146] The visualization module 940 is used to convert the target buried event data in each category of classified event data into a visualization graphic according to the time series corresponding to the target buried event data, obtain the visualization image corresponding to the abnormal device, and determine the failure cause of the abnormal device based on the visualization image; the visualization image includes the visualization graphics corresponding to the target buried event data in each category of classified event data.

[0147] In some embodiments of this specification, the data classification module is specifically used for:

[0148] After receiving the buried event data, calling the pre-created classification reporting component to determine the label corresponding to each buried event data; the classification reporting component defines a method for determining the label of the buried event data according to the event category;

[0149] Classify each buried event data into different categories of classified event data according to the labels corresponding to each buried event data;

[0150] The visualization module is also used to display the label of the classified event data to which the target buried point event data corresponding to each visualization graphic in the visualization image belongs on the corresponding visualization graphic.

[0151] Regarding the device in the above embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment of the method, and will not be elaborated in detail here. The device in the above embodiment may also include other implementation methods according to the description of the method embodiment, and the specific implementation method can refer to the description of the relevant method embodiment, which will not be repeated here one by one.

[0152] Fig.10 is a block diagram of an electronic device for fault analysis based on buried point data provided by an embodiment of this specification. The electronic device may be a terminal, and its internal structure diagram may be as shown in FIG. Fig.10 As shown. The electronic device includes a processor, a memory, a network interface, a display screen and an input device connected via a system bus. Among them, the processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a fault analysis method based on buried point data is implemented. The display screen of the electronic device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the electronic device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the housing of the electronic device, or an external keyboard, touchpad or mouse, etc.

[0153] Fig.11 is a block diagram of another electronic device for fault analysis based on buried point data provided by an embodiment of this specification. The electronic device may be a server, and its internal structure diagram may be as shown in FIG. Fig.11As shown. The electronic device includes a processor, a memory and a network interface connected via a system bus. Among them, the processor of the electronic device is used to provide computing and control capabilities. The memory of the electronic device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the electronic device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a fault analysis method based on buried point data is implemented.

[0154] Those skilled in the art will understand that Fig.10 or Fig.11 The structure shown in the figure is merely a block diagram of a portion of the structure related to the embodiment scheme of this specification, and does not constitute a limitation on the electronic device to which the embodiment scheme of this specification is applied. The specific electronic device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0155] In an exemplary embodiment, an electronic device is also provided, comprising: a processor; a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement a fault analysis method based on buried point data as in the embodiment of this specification.

[0156] In an exemplary embodiment, a computer-readable storage medium is also provided. When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute the fault analysis method based on buried point data in the embodiment of this specification.

[0157] In an exemplary embodiment, a computer program product or a computer program is also provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the fault analysis method based on buried point data provided in the above-mentioned various optional implementations.

[0158] It is understandable that in the specific implementation of this specification, user-related data is involved. When the above embodiments of this specification are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards of relevant countries and regions.

[0159] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this specification can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0160] Those skilled in the art will readily appreciate other implementations of the embodiments of the present specification after considering the specification and practicing the invention disclosed herein. The present specification is intended to cover any variations, uses, or adaptations of the embodiments of the present specification, which follow the general principles of the embodiments of the present specification and include common knowledge or customary technical means in the art that are not disclosed in the embodiments of the present specification. The description and embodiments are to be considered merely as exemplary, and the true scope and spirit of the embodiments of the present specification are indicated by the following claims.

[0161] It should be understood that the embodiments of the present specification are not limited to the precise structures described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the embodiments of the present specification is limited only by the appended claims.

Claims

1. A fault analysis method based on buried point data, characterized in that: The method comprises: Receive the tracking event data reported when the preset tracking point is triggered within the specified time range; According to the event category corresponding to each buried event data, each buried event data is divided into classified event data of different categories; According to the predetermined abnormal device and the device serial number corresponding to the buried event data, the target buried event data corresponding to the abnormal device in each classified event data is filtered out; According to the time series corresponding to the target buried point event data, the target buried point event data in each category of classified event data is converted into a visualization graphic, and a visualization image corresponding to the abnormal device is obtained, so as to determine the failure cause of the abnormal device based on the visualization image; the visualization image includes the visualization graphics corresponding to the target buried point event data in each category of classified event data.

2. The method according to claim 1, characterized in that According to the event category corresponding to each buried event data, each buried event data is classified into different categories of classified event data, including: After receiving the buried event data, calling the pre-created classification reporting component to determine the label corresponding to each buried event data; the classification reporting component defines a method for determining the label of the buried event data according to the event category; Classify each buried event data into different categories of classified event data according to the labels corresponding to each buried event data; When obtaining the visual image corresponding to the abnormal device, the method further includes: The label of the classified event data to which the target buried point event data corresponding to each visualization graphic in the visualization image belongs is displayed on the corresponding visualization graphic.

3. The method according to claim 2, characterized in that The classification reporting component also defines a method for determining event attributes and event names of buried event data. When the pre-created classification reporting component is called to determine the labels corresponding to each buried event data, the method further includes: Calling the classification reporting component to determine the event attributes and event names corresponding to each buried event data; When converting the target buried point event data in each category classification event data into a visual graph, the event attributes and event names corresponding to each target buried point event data are added as hidden information to the corresponding visual graph; When a designated operation is performed on the visual graphic, the hidden information corresponding to the visual graphic is displayed at a corresponding position of the visual graphic.

4. The method according to claim 3, characterized in that: The method further comprises: The classification reporting component is called in a chain calling manner to determine the label, event attribute and event name corresponding to each buried event data.

5. The method according to claim 1, characterized in that The step of converting the target buried event data in each category classification event data into a visual graph according to the time series corresponding to the target buried event data comprises: According to the timestamp corresponding to the target buried point event data in the classified event data, the target buried point event data in the classified event data of different categories are clustered according to the preset time range, and the target buried point event data in each category of the classified event data obtains multiple clustered event data; According to the time series corresponding to the multiple clustered event data in each category of the classified event data, the target buried event data in each category of the classified event data is converted into a visual graph.

6. The method according to claim 1, characterized in that The classified event data is text format data, and the target buried event data in each category of classified event data is converted into a visual graph, including: Convert the text format data of the target buried point event data in each category classification event data into a text graphic description language format file according to the time series; The text graphic description language format file of the target buried point event data in each category classification event data is converted into a scalable vector graphic or a hypertext markup language graphic.

7. A fault analysis device based on buried point data, characterized in that: The device comprises: The data collection module is used to receive the buried point event data reported when the preset buried point is triggered within the specified time range; A data classification module is used to classify each buried event data into classified event data of different categories according to the event category corresponding to each buried event data; A data screening module, used to screen out target buried event data corresponding to the abnormal device in each classified event data according to the predetermined abnormal device and the device serial number corresponding to the buried event data; A visualization module is used to convert the target buried event data in each category of classified event data into a visualization graphic according to the time series corresponding to the target buried event data, obtain a visualization image corresponding to the abnormal device, and determine the cause of the failure of the abnormal device based on the visualization image; the visualization image includes the visualization graphics corresponding to the target buried event data in each category of classified event data.

8. The device according to claim 7, characterized in that The data classification module is specifically used for: After receiving the buried event data, calling the pre-created classification reporting component to determine the label corresponding to each buried event data; the classification reporting component defines a method for determining the label of the buried event data according to the event category; Classify each buried event data into different categories of classified event data according to the labels corresponding to each buried event data; The visualization module is also used to display the label of the classified event data to which the target buried point event data corresponding to each visualization graphic in the visualization image belongs on the corresponding visualization graphic.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the fault analysis method based on buried point data as described in any one of claims 1 to 6.

10. A computer-readable storage medium, characterized in that: When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the fault analysis method based on buried point data as described in any one of claims 1 to 6.