Fault analysis data management method, searching method, device, equipment and medium
By using fishbone diagrams to manage fault analysis data, the problems of inconvenient searching and data disorganization in existing technologies have been solved, enabling rapid searching and efficient management, and improving user experience and analysis efficiency.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- INSPUR BUSINESS MACHINE CO LTD
- Filing Date
- 2023-03-24
- Publication Date
- 2026-05-29
Smart Images
Figure CN116383150B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of computer technology, and in particular to a method, retrieval method, apparatus, device, and storage medium for managing fault analysis data. Background Technology
[0002] With the rise of the computer industry, various projects generate a large amount of data during the R&D and debugging phases. This includes analysis of classic and difficult problems (lesson learners), compiled and summarized knowledge reserve expansion documents (SOPs), and necessary problem analysis tools (Debug tools). All of this data needs to be archived and preserved to facilitate summarizing lessons learned and reduce the effort required to solve similar problems in the future. Currently, there are two methods for organizing fault data: one is to distinguish data by name, with the name containing key information for fault analysis, but the data is not categorized and is stored uniformly in a local or server-wide folder; the other is to establish a fixed path on a fixed server, initially categorizing the fault analysis data and storing it in different folders within that fixed path. However, the first method, which distinguishes data by name, cannot completely store all key information in the fault analysis data through naming, potentially leading to omissions during searches. Furthermore, it requires users to be very familiar with the key factors of the fault to access the data, and when there is a large amount of data, it can easily lead to data archiving chaos and difficulty in maintaining the data. The second method, with its complex folder tree structure, requires a connection to a fixed server or periodic downloads of all data, making it inconvenient to operate. Summary of the Invention
[0003] In view of this, the purpose of this invention is to provide a method, retrieval method, apparatus, device, and storage medium for managing fault analysis data, which can graphically represent the data and manage fault analysis data in a fishbone diagram format so that users can more conveniently and quickly retrieve fault analysis data using the fishbone diagram. The specific solution is as follows:
[0004] Firstly, this application discloses a method for managing fault analysis data, including:
[0005] The target fault component is selected through the local preset software terminal, and several types of fault information of the target fault component and several fault analysis folders located in the background server are obtained; the fault analysis folders contain corresponding fault analysis data.
[0006] Generate folder data search buttons corresponding to each of the aforementioned fault analysis folders, and generate a target fishbone diagram corresponding to the target fault component by marking different fault information and the corresponding folder data search buttons on different fishbone branches.
[0007] The target fishbone diagram is displayed on a preset human-computer interaction interface so that users can use the target fishbone diagram displayed on the preset human-computer interaction interface to search for fault analysis data.
[0008] Optionally, before selecting the target faulty component through a local preset software terminal, the method further includes:
[0009] Download all the fault analysis data stored in the backend server to establish a local fault data copy library, so as to respond to requests for accessing the fault analysis data obtained locally using the local fault data copy library.
[0010] Optionally, after downloading all the fault analysis data stored in the background server to establish a local fault data copy library, the method further includes:
[0011] If the current connection to the backend server is via an internal network, then obtain the first update timestamp corresponding to all the fault analysis data in the backend server, and determine whether the first update timestamp is consistent with the second update timestamp of the local fault data copy database.
[0012] If not, then obtain the updated fault analysis data issued by the backend server, synchronize the updated fault analysis data to the local fault data copy database, and determine the second update timestamp as the first update timestamp.
[0013] Optionally, selecting the target faulty component through a local preset software terminal includes:
[0014] The target fault component can be selected from all fault components through several preset interactive buttons on the preset graphical interface of the local preset software terminal; different preset interactive buttons correspond to different fault components.
[0015] Optionally, the preset graphical interface further includes:
[0016] By selecting a preset data classification attribute through the preset graphical interface, the fault analysis data of all fault components are classified accordingly based on the preset data classification attribute, and all the classified fault analysis data are displayed in a list form through a list pop-up interface.
[0017] Secondly, this application discloses a method for searching fault analysis data, including:
[0018] The target fishbone diagram corresponding to the target fault component is displayed on the preset human-computer interaction interface; each fishbone branch on the target fishbone diagram is pre-marked with different fault information of the target fault component and corresponding folder data search buttons, and different folder data search buttons correspond to different fault analysis folders;
[0019] Obtain the click instruction received from the preset human-computer interaction interface for the target folder data search button on the target fishbone diagram;
[0020] The click command triggers a corresponding search operation to locate the target fault analysis folder corresponding to the target folder data search button and the fault analysis data in the target fault analysis folder. The found fault analysis data is then displayed so that the user can view it.
[0021] Optionally, the fault analysis data retrieval method further includes:
[0022] Based on the naming keywords obtained through the preset graphical interface, the fault analysis data containing the corresponding naming keywords are searched from the fault analysis data of all fault components, and the currently found fault analysis data are displayed in a list form through a list pop-up interface.
[0023] Thirdly, this application discloses a fault analysis data management device, comprising:
[0024] The fault selection module is used to select a target fault component through a local preset software terminal, and obtain several types of fault information of the target fault component and several fault analysis folders located in the background server; the fault analysis folders contain corresponding fault analysis data.
[0025] The fishbone diagram generation module is used to generate folder data search buttons corresponding to each of the fault analysis folders, and to generate a target fishbone diagram corresponding to the target fault component by marking different fault information and the corresponding folder data search buttons on different fishbone branches.
[0026] The first fishbone diagram display module is used to display the target fishbone diagram on a preset human-computer interaction interface, so that users can use the target fishbone diagram displayed on the preset human-computer interaction interface to search for fault analysis data.
[0027] Fourthly, this application discloses a fault analysis data retrieval device, comprising:
[0028] The second fishbone diagram display module is used to display the target fishbone diagram corresponding to the target fault component on a preset human-computer interaction interface; each fishbone branch on the target fishbone diagram is pre-marked with different fault information of the target fault component and corresponding folder data search buttons, and different folder data search buttons correspond to different fault analysis folders;
[0029] The instruction acquisition module is used to acquire the click instruction received in the preset human-computer interaction interface for the target folder data search button on the target fishbone diagram;
[0030] The data search module is used to trigger a corresponding search operation based on the click instruction, to find the target fault analysis folder corresponding to the target folder data search button and the fault analysis data in the target fault analysis folder, and to display the found fault analysis data so that the user can view the fault analysis data.
[0031] Fifthly, this application discloses an electronic device, comprising:
[0032] Memory, used to store computer programs;
[0033] A processor is used to execute the computer program to implement the aforementioned fault analysis data management and fault analysis data retrieval method.
[0034] Sixthly, this application discloses a computer-readable storage medium for storing a computer program, which, when executed by a processor, implements the aforementioned fault analysis data management and fault analysis data retrieval method.
[0035] As can be seen, this application first selects a target fault component through a local preset software terminal and obtains several types of fault information of the target fault component and several fault analysis folders located in the background server; the fault analysis folders contain corresponding fault analysis data; then, it generates folder data search buttons corresponding to each of the fault analysis folders, and generates a target fishbone diagram corresponding to the target fault component by marking different fault information and corresponding folder data search buttons on different fishbone branches; then, it displays the target fishbone diagram on a preset human-computer interaction interface so that users can use the target fishbone diagram displayed on the preset human-computer interaction interface to perform fault analysis data search operations. Therefore, this application generates a fishbone diagram corresponding to the fault component, including fault information and corresponding fault analysis data, so that users can search for the required fault analysis data through the fishbone diagram. In this way, the graphical visual interactive interface enables quick searching and opening of problem-related fault analysis data, and the classification and analysis of various fault information through the fishbone diagram can accelerate the efficiency of problem analysis and resolution, making the management and search operations of fault analysis data more convenient and clear. Attached Figure Description
[0036] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.
[0037] Figure 1 This application discloses a flowchart of a fault analysis data management method.
[0038] Figure 2 This application discloses a flowchart of a specific method for managing fault analysis data.
[0039] Figure 3 This is a flowchart of a fault analysis data retrieval method disclosed in this application;
[0040] Figure 4 This is a schematic diagram of a fault analysis data management and retrieval method disclosed in this application;
[0041] Figure 5 This is a schematic diagram of the structure of a fault analysis data management device disclosed in this application;
[0042] Figure 6 This is a schematic diagram of a fault analysis data retrieval device disclosed in this application;
[0043] Figure 7This is a structural diagram of an electronic device disclosed in this application. Detailed Implementation
[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0045] There are currently two methods for organizing fault data. One method distinguishes data by name, with the name containing key information for fault analysis. However, the data is not categorized and is stored uniformly in a local or server-wide folder. The other method establishes a fixed path on a fixed server, initially categorizes the fault analysis data, and stores it in different folders within that fixed path. However, the first method, which distinguishes data by name, cannot store all the key information in the fault analysis data by name, which may lead to omissions during searching. Furthermore, users need to be very clear about the key factors of the fault to find the data. When there is a large amount of data, it is also easy to cause problems such as data archiving disorder and difficulty in data maintenance. On the other hand, the hierarchical structure of the folder tree in the second method is too complex, and it is necessary to connect to a fixed server or download all data periodically, which is inconvenient to operate.
[0046] See Figure 1 As shown in the figure, this application discloses a method for managing fault analysis data, including:
[0047] Step S11: Select the target fault component through the local preset software terminal, and obtain several types of fault information of the target fault component and several fault analysis folders located in the background server; the fault analysis folders contain corresponding fault analysis data.
[0048] In this embodiment, a local preset software client is used to select a target faulty component from several faulty components, and obtains several fault information of the target faulty component and several fault analysis folders located in the background server. The fault analysis folders store corresponding fault analysis data. The preset software client is software located on the local computer device. Users can manage and search for fault analysis data through the software, but the preset software client only has read and download permissions and cannot operate the storage resources of the background server. The background server is used to manage and store fault analysis data in the form of a folder tree according to a fishbone diagram branch classification. The fault analysis data stored in the background server is based on components that have been manually pre-classified. The faulty component can be a component on the computer device, such as memory, hard disk, etc.
[0049] Step S12: Generate folder data search buttons corresponding to each of the fault analysis folders, and generate a target fishbone diagram corresponding to the target fault component by marking different fault information and the corresponding folder data search buttons on different fishbone branches.
[0050] In this embodiment, using several fault information items and several fault analysis folders, a folder search button corresponding to each fault analysis folder is generated. Different fault information items and their corresponding folder search buttons are labeled on different fishbone branches to generate a target fishbone diagram corresponding to the target fault component. The fault information is labeled next to the fishbone branches, and each fishbone branch can contain several fault information items. A corresponding folder search button is labeled at the end of each fishbone branch to open the fault analysis data in the corresponding fault analysis folder. In this way, by generating corresponding fishbone diagrams based on the fault information and fault analysis folders corresponding to different fault problems, the fault problems of each fault component can be more clearly and concisely displayed through different fishbone branches. This allows users to identify the current fault problem based on the fault information in each fishbone branch, greatly improving the user experience.
[0051] Step S13: Display the target fishbone diagram on a preset human-computer interaction interface so that the user can use the target fishbone diagram displayed on the preset human-computer interaction interface to search for fault analysis data.
[0052] In this embodiment, after generating the target fishbone diagram, it is displayed on a preset human-computer interaction interface. This allows the user to identify the current fault using the target fishbone diagram displayed on the interface, and to open the corresponding folder using the folder search button at the end of the target fishbone branch to retrieve fault analysis data. In this way, the graphical visual interface enables quick retrieval and opening of problem-related fault analysis data, and the fishbone diagram-based classification and analysis of various fault information accelerates problem analysis and resolution efficiency, making the management and retrieval of fault analysis data more convenient and clear.
[0053] As can be seen, this embodiment first selects a target fault component through a local preset software terminal and obtains several types of fault information of the target fault component and several fault analysis folders located in the background server; the fault analysis folders contain corresponding fault analysis data; then, it generates folder data search buttons corresponding to each of the fault analysis folders, and generates a target fishbone diagram corresponding to the target fault component by marking different fault information and corresponding folder data search buttons on different fishbone branches; then, it displays the target fishbone diagram on a preset human-computer interaction interface so that users can use the target fishbone diagram displayed on the preset human-computer interaction interface to perform fault analysis data search operations. Therefore, this embodiment generates a fishbone diagram corresponding to the fault component, including fault information and corresponding fault analysis data, so that users can find the required fault analysis data through the fishbone diagram. In this way, the graphical visual interactive interface enables quick searching and opening of problem-related fault analysis data, and the classification and analysis of various fault information through the fishbone diagram can accelerate the efficiency of problem analysis and resolution, making the management and search operations of fault analysis data more convenient and clear.
[0054] See Figure 2 As shown in the figure, this application discloses a specific method for managing fault analysis data, including:
[0055] Step S21: Download all fault analysis data stored in the background server through the local preset software to establish a local fault data copy library, so as to respond to the request for accessing the fault analysis data obtained locally using the local fault data copy library.
[0056] In this embodiment, when using the preset software client for the first time, all fault analysis data stored in the background server can be downloaded through the local preset software client, and a local fault data copy library can be established on the local computer. In this way, the local fault data copy library can be used to respond to requests for accessing the fault analysis data obtained locally. That is, when generating the target fishbone diagram and searching for relevant fault analysis data in the future, the local fault data copy library can be directly used for management and searching, without having to connect to and obtain resources from the background server every time.
[0057] In this embodiment, after downloading all the fault analysis data stored in the backend server to establish a local fault data copy library, the process may further include: if the current connection to the backend server is via an internal network, obtaining the first update timestamp corresponding to all the fault analysis data in the backend server, and determining whether the first update timestamp is consistent with the second update timestamp of the local fault data copy library; if not, obtaining the updated fault analysis data issued by the backend server, synchronizing the updated fault analysis data to the local fault data copy library, and determining the second update timestamp as the first update timestamp. When the preset software connects to the backend server via an internal network, it can obtain the first update timestamp of the last update of all fault analysis data in the backend server. It then determines whether the first update timestamp matches the second update timestamp of the last update of all fault analysis data in the local fault data copy database. This determines whether the data in the backend server has been updated. If they match, no synchronization update is performed. If they do not match, it indicates that the fault analysis data in the backend server has been updated. The updated fault analysis data issued by the backend server is then obtained and synchronized to the local fault data copy database. The second update timestamp is set as the first update timestamp to ensure that the data update time of the backend server remains consistent. In this way, by promptly checking whether the first update timestamp of the backend server matches the second update timestamp of the local fault data copy database, it determines whether an update of the local fault data copy database is needed. This ensures that the local fault data copy database is updated in a timely manner and consistent with the backend server, preventing problems such as outdated or incomplete data due to prolonged periods without updates.
[0058] Step S22: Select the target fault component from all fault components through several preset interactive buttons on the preset graphical interface of the preset software terminal; different preset interactive buttons correspond to different fault components.
[0059] In this embodiment, the user can select a target fault component from all fault components through several preset interactive buttons on a preset graphical interface in the local preset software terminal. Different preset interactive buttons correspond to different fault components. In this way, the user can obtain the corresponding fault analysis data of the component by selecting the fault component with the problem.
[0060] Step S23: Obtain several types of fault information of the target fault component and several fault analysis folders located in the background server; the fault analysis folders contain corresponding fault analysis data.
[0061] In this embodiment, the preset graphical interface may further include: selecting a preset data classification attribute through the preset graphical interface to perform corresponding classification operations on the fault analysis data of all fault components based on the preset data classification attribute, and displaying all the classified fault analysis data in a list form in a list pop-up interface. The preset graphical interface also includes a data classification function. Users can select preset data classification attributes by clicking the preset classification method button to classify all fault analysis data of faulty components according to the preset data classification attributes. A list pop-up window on the preset software side displays all the classified fault analysis data in a list format. The preset data classification attributes may include: lesson learn, SOP (Standard Operating Procedure), and debug tool, etc. Lesson learn refers to experience summary, or lessons learned, usually after a bad event occurs, defects are corrected, and rectification is completed. It is a quality management method that summarizes some methods, processes, and management methods based on the information obtained to prevent the same or similar problems from recurring. SOP refers to standard operating procedures, which refers to the standard operating steps and requirements of a certain event described in a unified format to guide and standardize daily work. Debug tool refers to relevant software and tools used to assist in troubleshooting. It can be understood that users can directly open the relevant data file stored locally by clicking on any fault analysis data in the list pop-up window interface. In this way, users can also categorize three types of fault analysis data—lesson learn, debug tool, and SOP—using preset category buttons, making the classification management methods more diverse and the hierarchy more distinct, providing users with more choices.
[0062] Step S24: Generate folder data search buttons corresponding to each of the fault analysis folders, and generate a target fishbone diagram corresponding to the target fault component by marking different fault information and corresponding folder data search buttons on different fishbone branches.
[0063] Step S25: Display the target fishbone diagram on a preset human-computer interaction interface so that the user can use the target fishbone diagram displayed on the preset human-computer interaction interface to search for fault analysis data.
[0064] The specific processes of steps S23 to S25 can be found in the relevant content disclosed in the foregoing embodiments, and will not be repeated here.
[0065] As can be seen, this embodiment can download all fault analysis data to the local machine upon initial connection with the backend server to establish a local fault data copy library. This local copy library can then be directly used for management and searching, eliminating the need to connect to and retrieve resources from the backend server for each operation. Furthermore, by regularly checking whether the first update timestamp of the backend server matches the second update timestamp of the local fault data copy library, the system determines whether an update is needed. This ensures the timely updating of the local fault data copy library and its consistency with the backend server, preventing issues such as outdated or incomplete data due to prolonged periods without updates. This application also includes a data categorization function in the preset graphical interface. Users can further categorize fault analysis data into three types: lesson learn, debug tool, and SOP, using preset categorization buttons. This makes the categorization management methods more diverse and hierarchical, providing users with more choices.
[0066] See Figure 3 As shown in the figure, this application discloses a method for finding fault analysis data, including:
[0067] Step S31: Display the target fishbone diagram corresponding to the target fault component on the preset human-computer interaction interface; each fishbone branch on the target fishbone diagram is pre-marked with different fault information of the target fault component and corresponding folder data search buttons, and different folder data search buttons correspond to different fault analysis folders.
[0068] In this embodiment, after the user selects a target fault component through preset interactive buttons in a preset graphical interface on the preset software, a target fishbone diagram corresponding to the target fault component will be displayed on the preset human-computer interaction interface. Each branch of the target fishbone diagram is pre-labeled with different fault information of the target fault component and corresponding folder search buttons. Furthermore, different folder search buttons correspond to different fault analysis folders. It should be noted that the displayed target fishbone diagram can be a fishbone diagram regenerated using a fault analysis management method. Alternatively, if the data has not been updated, historically generated fishbone diagrams stored in the system can be displayed. This avoids the resource consumption problem caused by regenerating historically generated fishbone diagrams when the data has not been updated.
[0069] Step S32: Obtain the click instruction received in the preset human-computer interaction interface for the target folder data search button on the target fishbone diagram.
[0070] In this embodiment, after the user determines the current fault problem based on the fault information in the target fishbone diagram and selects the corresponding target folder data search button, the preset software terminal obtains the click instruction for the target folder data search button received in the preset human-computer interaction interface, so as to open the corresponding fault analysis folder.
[0071] Step S33: Trigger the corresponding search operation according to the click instruction to find the target fault analysis folder corresponding to the target folder data search button and the fault analysis data in the target fault analysis folder, and display the found fault analysis data so that the user can view the fault analysis data.
[0072] In this embodiment, the click instruction triggers a corresponding search operation to locate the target fault analysis folder corresponding to the target folder's data search button, along with the fault analysis data within that folder. The searched analysis data is then displayed in a list format through a preset list interface for user viewing. It is understood that users can directly open and view the locally stored fault analysis data by clicking on the corresponding data in the preset list interface, eliminating the need for manual searching and opening from a local fault data copy library. This significantly improves data management and search efficiency, allowing users to directly access the corresponding fault analysis data through the software without manual analysis and searching.
[0073] In this embodiment, the fault analysis and search method may further include: searching for fault analysis data containing the corresponding named keywords from the fault analysis data of all fault components based on named keywords obtained through a preset graphical interface, and displaying the currently found fault analysis data in a list format through a list pop-up interface. The user inputs the named keywords of the fault analysis data to be searched through a preset graphical interface in the preset software terminal. After obtaining the named keywords, the preset software terminal searches for fault analysis data containing the corresponding named keywords from the fault analysis data of all fault components, and displays the currently found fault analysis data in a list format through a list pop-up interface, so that the user can directly select and open the required fault analysis data through the list pop-up interface. In this way, by providing users with a keyword search function, they can obtain the data they need to view without having to select through component and fault problem classification; they can directly obtain and open the corresponding fault analysis data by searching for keywords, allowing users to view relevant fault analysis data more directly and improving the user experience.
[0074] See Figure 4As shown, the user first uses the graphical interface 1 (main interface) in the preset software client, which contains several preset interactive buttons, namely the "XXX Fault Analysis" button, to select the corresponding fault component. Each "XXX Fault Analysis" button corresponds to one fault component. The interactive buttons can be, for example, "Memory Fault Analysis," "Hard Disk Fault Analysis," etc. After clicking the button corresponding to the target fault component, a preset human-computer interaction interface is opened. The preset human-computer interaction interface displays the target fishbone diagram corresponding to the target fault component. Each branch in the target fishbone diagram has different fault information and corresponding folder data viewing buttons for the fault analysis folder. Each branch corresponds to a fault problem. The folder data viewing buttons are mapped one-to-one to the corresponding fault analysis folders through the server. After determining the fault problem through the fault information, the user can select the target folder data search button at the end of the corresponding fishbone branch and open a preset list interface to display several fault analysis data in the target fault analysis folder. The user can directly open the file of the fault analysis data stored locally by clicking on the fault analysis data they want to view.
[0075] As can be seen, this embodiment first displays the target fishbone diagram corresponding to the target fault component on a preset human-computer interaction interface. Each branch of the target fishbone diagram is pre-labeled with different fault information of the target fault component and corresponding folder search buttons. Different folder search buttons correspond to different fault analysis folders. Next, the preset human-computer interaction interface receives a click instruction for the target folder search button on the target fishbone diagram. Then, based on the click instruction, a corresponding search operation is triggered to find the target fault analysis folder corresponding to the target folder search button and the fault analysis data within that folder. The found fault analysis data is then displayed for the user to view. Therefore, this embodiment uses a fishbone diagram containing fault information and corresponding fault analysis data corresponding to the fault component to find the required fault analysis data. This allows for quick searching and opening of problem-related fault analysis data using a graphical visual interactive interface. Furthermore, classifying and analyzing various fault information using the fishbone diagram accelerates problem analysis and resolution efficiency, making the management and searching of fault analysis data more convenient and clear.
[0076] refer to Figure 5 The present application also discloses a fault analysis data management device, comprising:
[0077] The fault selection module 11 is used to select a target fault component through a local preset software terminal, and obtain several types of fault information of the target fault component and several fault analysis folders located in the background server; the fault analysis folders contain corresponding fault analysis data.
[0078] The fishbone diagram generation module 12 is used to generate folder data search buttons corresponding to each of the fault analysis folders, and to generate a target fishbone diagram corresponding to the target fault component by marking different fault information and the corresponding folder data search buttons on different fishbone branches.
[0079] The first fishbone diagram display module 13 is used to display the target fishbone diagram on a preset human-computer interaction interface so that the user can use the target fishbone diagram displayed on the preset human-computer interaction interface to search for fault analysis data.
[0080] As can be seen, this embodiment first selects a target fault component through a local preset software terminal and obtains several types of fault information of the target fault component and several fault analysis folders located in the background server; the fault analysis folders contain corresponding fault analysis data; then, it generates folder data search buttons corresponding to each of the fault analysis folders, and generates a target fishbone diagram corresponding to the target fault component by marking different fault information and corresponding folder data search buttons on different fishbone branches; then, it displays the target fishbone diagram on a preset human-computer interaction interface so that users can use the target fishbone diagram displayed on the preset human-computer interaction interface to perform fault analysis data search operations. Therefore, this embodiment generates a fishbone diagram corresponding to the fault component, including fault information and corresponding fault analysis data, so that users can find the required fault analysis data through the fishbone diagram. In this way, the graphical visual interactive interface enables quick searching and opening of problem-related fault analysis data, and the classification and analysis of various fault information through the fishbone diagram can accelerate the efficiency of problem analysis and resolution, making the management and search operations of fault analysis data more convenient and clear.
[0081] In some specific embodiments, the fault analysis data management device may further include:
[0082] The data download module is used to download all the fault analysis data stored in the backend server to establish a local fault data copy library, so as to respond to requests for accessing the fault analysis data obtained locally using the local fault data copy library.
[0083] In some specific embodiments, the fault analysis data management device may further include:
[0084] The timestamp determination module is used to obtain the first update timestamp corresponding to all the fault analysis data in the backend server if the current connection to the backend server is through an internal network, and to determine whether the first update timestamp is consistent with the second update timestamp of the local fault data copy database.
[0085] The replica database update module is used to, if not, obtain the updated fault analysis data issued by the backend server, synchronize the updated fault analysis data to the local fault data replica database, and determine the second update timestamp as the first update timestamp.
[0086] In some specific embodiments, the fault selection module 11 can be used to select a target fault component from all fault components through a number of preset interactive buttons on a preset graphical interface of a local preset software terminal; different preset interactive buttons correspond to different fault components.
[0087] In some specific embodiments, the fault analysis data management device may further include:
[0088] The data classification module is used to select preset data classification attributes through the preset graphical interface to perform corresponding classification operations on the fault analysis data of all fault components based on the preset data classification attributes, and to display all the classified fault analysis data in a list form through a list pop-up interface.
[0089] refer to Figure 6 The present application also discloses a fault analysis data retrieval device, comprising:
[0090] The second fishbone diagram display module 21 is used to display the target fishbone diagram corresponding to the target fault component on a preset human-computer interaction interface; each fishbone branch on the target fishbone diagram is pre-marked with different fault information of the target fault component and corresponding folder data search buttons, and different folder data search buttons correspond to different fault analysis folders.
[0091] Instruction acquisition module 22 is used to acquire click instructions received in the preset human-computer interaction interface for the target folder data search button on the target fishbone diagram;
[0092] The data search module 23 is used to trigger a corresponding search operation according to the click instruction, so as to find the target fault analysis folder corresponding to the target folder data search button and the fault analysis data in the target fault analysis folder, and display the found fault analysis data so that the user can view the fault analysis data.
[0093] As can be seen, this embodiment first displays the target fishbone diagram corresponding to the target fault component on a preset human-computer interaction interface. Each branch of the target fishbone diagram is pre-labeled with different fault information of the target fault component and corresponding folder search buttons. Different folder search buttons correspond to different fault analysis folders. Next, the preset human-computer interaction interface receives a click instruction for the target folder search button on the target fishbone diagram. Then, based on the click instruction, a corresponding search operation is triggered to find the target fault analysis folder corresponding to the target folder search button and the fault analysis data within that folder. The found fault analysis data is then displayed for the user to view. Therefore, this embodiment uses a fishbone diagram containing fault information and corresponding fault analysis data corresponding to the fault component to find the required fault analysis data. This allows for quick searching and opening of problem-related fault analysis data using a graphical visual interactive interface. Furthermore, classifying and analyzing various fault information using the fishbone diagram accelerates problem analysis and resolution efficiency, making the management and searching of fault analysis data more convenient and clear.
[0094] In some specific embodiments, the fault analysis data retrieval device may further include:
[0095] The keyword search module is used to search for fault analysis data containing the corresponding named keywords from all fault component fault analysis data based on the named keywords obtained through the preset graphical interface, and to display the currently found fault analysis data in a list form through a list pop-up interface.
[0096] Furthermore, embodiments of this application also disclose an electronic device, Figure 7 This is a structural diagram of an electronic device 20 according to an exemplary embodiment. The content of the diagram should not be construed as limiting the scope of this application.
[0097] Figure 7 This is a schematic diagram of the structure of an electronic device 30 provided in an embodiment of this application. Specifically, the electronic device 30 may include: at least one processor 31, at least one memory 32, a power supply 33, a communication interface 34, an input / output interface 35, and a communication bus 36. The memory 32 stores a computer program, which is loaded and executed by the processor 31 to implement the relevant steps in the fault analysis data management method and fault analysis data retrieval method disclosed in any of the foregoing embodiments. Furthermore, the electronic device 30 in this embodiment may specifically be an electronic computer.
[0098] In this embodiment, the power supply 33 is used to provide operating voltage for each hardware device on the electronic device 30; the communication interface 34 can create a data transmission channel between the electronic device 30 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 35 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.
[0099] In addition, the memory 32, as a carrier for resource storage, can be a read-only memory, random access memory, disk or optical disk, etc. The resources stored thereon can include operating system 321, computer program 322, etc., and the storage method can be temporary storage or permanent storage.
[0100] The operating system 321 is used to manage and control the various hardware devices on the electronic device 30 and the computer program 322, which may be Windows Server, Netware, Unix, Linux, etc. In addition to including computer programs capable of performing the fault analysis data management method and fault analysis data search method executed by the electronic device 30 as disclosed in any of the foregoing embodiments, the computer program 322 may further include computer programs capable of performing other specific tasks.
[0101] Furthermore, this application also discloses a computer-readable storage medium for storing a computer program; wherein, when the computer program is executed by a processor, it implements the aforementioned fault analysis data management method and fault analysis data retrieval method. Specific steps of this method can be found in the corresponding content disclosed in the foregoing embodiments, and will not be repeated here.
[0102] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.
[0103] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0104] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.
[0105] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0106] The technical solutions provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A method for managing fault analysis data, characterized in that, include: Select the target fault component through the local preset software terminal, and obtain several types of fault information of the target fault component and several fault analysis folders located in the background server. The fault analysis folder contains corresponding fault analysis data; wherein, before selecting the target fault component through the local preset software client, the process further includes: downloading all the fault analysis data stored in the backend server to establish a local fault data copy library, so as to respond to requests for accessing the fault analysis data obtained locally using the local fault data copy library; wherein, the backend server is used to manage and store the fault analysis data in the form of a folder tree according to a fishbone diagram branch classification; the preset software client only has read and download permissions and cannot operate the storage resources of the backend server; The process of downloading all the fault analysis data stored in the backend server to establish a local fault data copy library further includes: if the current connection to the backend server is via an internal network, obtaining the first update timestamp corresponding to all the fault analysis data in the backend server, and determining whether the first update timestamp is consistent with the second update timestamp of the local fault data copy library; if not, obtaining the updated fault analysis data issued by the backend server, synchronizing the updated fault analysis data to the local fault data copy library, and determining the second update timestamp as the first update timestamp; Generate folder data search buttons corresponding to each of the aforementioned fault analysis folders, and generate a target fishbone diagram corresponding to the target fault component by marking different fault information and the corresponding folder data search buttons on different fishbone branches. The target fishbone diagram is displayed on a preset human-computer interaction interface so that users can use the target fishbone diagram displayed on the preset human-computer interaction interface to search for fault analysis data.
2. The fault analysis data management method according to claim 1, characterized in that, The step of selecting the target faulty component through a local preset software terminal includes: The target fault component can be selected from all fault components through several preset interactive buttons on the preset graphical interface of the local preset software terminal; different preset interactive buttons correspond to different fault components.
3. The fault analysis data management method according to claim 2, characterized in that, The preset graphical interface also includes: By selecting a preset data classification attribute through the preset graphical interface, the fault analysis data of all fault components are classified accordingly based on the preset data classification attribute, and all the classified fault analysis data are displayed in a list form through a list pop-up interface.
4. A method for finding fault analysis data, characterized in that, include: Display the target fishbone diagram corresponding to the target faulty component in the preset human-computer interaction interface; Each branch of the fishbone diagram on the target is pre-marked with different fault information of the target fault component and corresponding folder data search buttons. Furthermore, different folder data search buttons correspond to different fault analysis folders. Obtain the click instruction received from the preset human-computer interaction interface for the target folder data search button on the target fishbone diagram; The click instruction triggers a corresponding search operation to locate the target fault analysis folder corresponding to the target folder data search button and the fault analysis data within that folder. The found fault analysis data is then displayed for the user to view. Before selecting the target fault component via the local preset software, the process includes downloading all fault analysis data stored on the backend server to establish a local fault data copy library. This local copy library is used to respond to requests for accessing the fault analysis data. The backend server manages and stores the fault analysis data in a folder tree structure according to a fishbone diagram. The preset software only has read and download permissions and cannot manipulate the backend server's storage resources. The process of downloading all the fault analysis data stored in the backend server to establish a local fault data copy library further includes: if the current connection to the backend server is via an internal network, obtaining the first update timestamp corresponding to all the fault analysis data in the backend server, and determining whether the first update timestamp is consistent with the second update timestamp of the local fault data copy library; if not, obtaining the updated fault analysis data issued by the backend server, synchronizing the updated fault analysis data to the local fault data copy library, and determining the second update timestamp as the first update timestamp.
5. The fault analysis data retrieval method according to claim 4, characterized in that, Also includes: Based on the naming keywords obtained through the preset graphical interface, the fault analysis data containing the corresponding naming keywords are searched from the fault analysis data of all fault components, and the currently found fault analysis data are displayed in a list form through a list pop-up interface.
6. A fault analysis data management device, characterized in that, include: The fault selection module is used to select a target fault component through a local preset software terminal, and obtain several types of fault information of the target fault component and several fault analysis folders located in the background server. The fault analysis folder contains corresponding fault analysis data; wherein, before selecting the target fault component through the local preset software client, the process further includes: downloading all the fault analysis data stored in the backend server to establish a local fault data copy library, so as to respond to requests for accessing the fault analysis data obtained locally using the local fault data copy library; wherein, the backend server is used to manage and store the fault analysis data in the form of a folder tree according to a fishbone diagram branch classification; the preset software client only has read and download permissions and cannot operate the storage resources of the backend server; The process of downloading all the fault analysis data stored in the backend server to establish a local fault data copy library further includes: if the current connection to the backend server is via an internal network, obtaining the first update timestamp corresponding to all the fault analysis data in the backend server, and determining whether the first update timestamp is consistent with the second update timestamp of the local fault data copy library; if not, obtaining the updated fault analysis data issued by the backend server, synchronizing the updated fault analysis data to the local fault data copy library, and determining the second update timestamp as the first update timestamp; The fishbone diagram generation module is used to generate folder data search buttons corresponding to each of the fault analysis folders, and to generate a target fishbone diagram corresponding to the target fault component by marking different fault information and the corresponding folder data search buttons on different fishbone branches. The first fishbone diagram display module is used to display the target fishbone diagram on a preset human-computer interaction interface, so that users can use the target fishbone diagram displayed on the preset human-computer interaction interface to search for fault analysis data.
7. A fault analysis data retrieval device, characterized in that, include: The second fishbone diagram display module is used to display the target fishbone diagram corresponding to the target fault component on the preset human-machine interaction interface. Each branch of the fishbone diagram on the target is pre-marked with different fault information of the target fault component and corresponding folder data search buttons. Furthermore, different folder data search buttons correspond to different fault analysis folders. The instruction acquisition module is used to acquire the click instruction received in the preset human-computer interaction interface for the target folder data search button on the target fishbone diagram; The data search module is used to trigger a corresponding search operation based on the click instruction to find the target fault analysis folder corresponding to the target folder data search button and the fault analysis data in the target fault analysis folder, and to display the found fault analysis data so that the user can view the fault analysis data; wherein, before selecting the target fault component through the local preset software terminal, it also includes: downloading all the fault analysis data stored in the background server to establish a local fault data copy library, so as to respond to the request for accessing the fault analysis data obtained locally using the local fault data copy library; wherein, the background server is used to manage and store the fault analysis data in the form of a folder tree according to the fishbone diagram branch classification; the preset software terminal only has read and download permissions and cannot operate the storage resources of the background server; The process of downloading all the fault analysis data stored in the backend server to establish a local fault data copy library further includes: if the current connection to the backend server is via an internal network, obtaining the first update timestamp corresponding to all the fault analysis data in the backend server, and determining whether the first update timestamp is consistent with the second update timestamp of the local fault data copy library; if not, obtaining the updated fault analysis data issued by the backend server, synchronizing the updated fault analysis data to the local fault data copy library, and determining the second update timestamp as the first update timestamp.
8. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor is configured to execute the computer program to implement the fault analysis data management method and the fault analysis data retrieval method as described in any one of claims 1 to 5.
9. A computer-readable storage medium, characterized in that, Used to store computer programs, which, when executed by a processor, implement the fault analysis data management method and the fault analysis data retrieval method as described in any one of claims 1 to 5.