A method, device and medium for collecting software task information of storage management

Abstract

The application relates to the storage technical field and discloses a storage management software task information collection method and device and medium, which comprises the following steps: creating a module association table according to historical log information to record the association levels of various modules and the dependency relationship among the modules; when a task fails, determining the direct association module and the indirect association module corresponding to the current task failure module according to the module association table, and calling a pre-constructed module information collector to collect the abnormal information of the current task failure module, the direct association module and the indirect association module to obtain an abnormal information set, and determining the cause of the current task failure according to the abnormal information set. It can be seen that when a module executes a task and fails, in addition to collecting the abnormal information of the current task module, the abnormal information of the module directly or indirectly associated with the current task module is also collected according to the pre-created module association table, the cause of the task failure is determined according to the accurate and comprehensive abnormal information, and the reliability of a storage system is improved.

Description

Technical Field

[0001] This application relates to the field of storage technology, and in particular to a method, apparatus and medium for collecting task information in storage management software. Background Technology

[0002] Browser / Server (B / S) architecture is a network structure that emerged after the rise of the Web. B / S architecture utilizes the increasingly mature Web browser technology to achieve powerful functions that previously required dedicated software, thus saving development costs.

[0003] Existing storage management software, based on a B / S architecture, provides a visual, user-friendly interface for managing storage systems, allowing users to manage storage resources through the interface. However, due to the complexity of the storage ecosystem, operations performed through this interface may fail due to various factors. Currently, many alarms and error messages are incomplete, preventing users from pinpointing the cause of failure and addressing errors or faults promptly. For example, when creating a storage pool, if the creation fails because the selected storage disk is already used or full, the software only notifies the user of the pool's failure without specifying the reason. This often requires developers to locate and troubleshoot the error, increasing manpower costs and providing a poor user experience.

[0004] Therefore, how to quickly obtain the reasons for task failures in storage management software and improve the user experience is a problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a method, apparatus, and medium for collecting task information in storage management software, so as to quickly locate the cause of task failure in storage management software, reduce the intervention of developers, and improve the user experience.

[0006] To address the aforementioned technical problems, this application provides a method for collecting task information in storage management software, comprising:

[0007] Create a module association table based on historical log information to record the association level of different modules in the storage management software and the dependencies between different modules;

[0008] Upon receiving a task failure signal, the direct and indirect associated modules corresponding to the current task failure module are determined based on the module association table.

[0009] A pre-built module information collector is invoked to collect the current task failure modules, the directly associated modules, and the indirectly associated modules to obtain an exception information set;

[0010] The reason for the current task failure is determined based on the set of abnormal information.

[0011] Preferably, the abnormal information set obtained by collecting the abnormal information of the current task failure module, the directly related module, and the indirectly related module includes:

[0012] Collect abnormal information of the current task failure module, the directly associated module, and the indirectly associated module during the time period from the start of the task to the end of the task.

[0013] The abnormal information set is obtained by storing the abnormal information collected from each failed task.

[0014] Preferably, determining the reason for the current task failure based on the set of abnormal information includes:

[0015] The abnormal information of the target within the preset period is classified to obtain the classification result;

[0016] Based on the classification results, the frequency of abnormal information occurrences in the current task failure module, the directly associated module, and the indirectly associated module is determined respectively;

[0017] The current task failure module is determined based on the frequency of the corresponding abnormal information of each module, and the current association level is determined for the directly associated module and the indirectly associated module.

[0018] The reason for the current task failure is determined based on the current association level described above.

[0019] Preferably, the step of determining the current task failure module based on the frequency of abnormal information corresponding to each module, wherein the current association level corresponding to the directly associated module and the indirectly associated module includes:

[0020] When the frequency of abnormal information exceeds the first threshold, the current association level is determined to be of importance.

[0021] When the frequency of abnormal information is greater than the second threshold and less than or equal to the first threshold, the current association level is determined to be medium.

[0022] When the frequency of abnormal information is no greater than the second threshold, the current association level is determined to be the general level.

[0023] Preferably, after determining the current association level of the currently failed task module, the directly associated module, and the indirectly associated module based on the frequency of the abnormal information corresponding to each module, the method further includes:

[0024] Determine whether the current association level of the module that failed the current task, the directly associated module, and the indirectly associated module are the same as the association level in the module association table;

[0025] If they are different, the module association table is updated based on the current association level.

[0026] Preferably, the method for collecting task information of the storage management software further includes:

[0027] Upon receiving a self-modification instruction, the module association table is modified according to the self-modification instruction.

[0028] Preferably, the step of creating a module association table based on historical log information to record the association levels of different modules in the storage management software and the dependencies between different modules includes:

[0029] The abnormal information in the historical log information is classified to determine the frequency of abnormal information in different modules;

[0030] The association level for different modules is determined based on the frequency of the abnormal information corresponding to the modules.

[0031] The correlation between different modules is determined based on the historical log information to determine the dependencies between different modules.

[0032] To address the aforementioned technical problems, this application also provides an apparatus for collecting task information in storage management software, comprising:

[0033] Create a module to create a module association table based on historical log information to record the association level of different modules in the storage management software and the dependencies between different modules;

[0034] The first determining module is used to determine the directly associated module and indirectly associated module corresponding to the current task failure module according to the module association table when a task failure signal is obtained.

[0035] The calling module is used to call a pre-built module information collector to collect the current task failure modules, the directly associated modules and the indirectly associated modules to obtain an exception information set;

[0036] The second determining module is used to determine the reason for the failure of the current task based on the set of abnormal information.

[0037] To address the aforementioned technical problems, this application also provides an apparatus for collecting task information of storage management software, including a memory for storing computer programs;

[0038] A processor, used to execute the computer program, implements the steps of the method for collecting task information of the storage management software.

[0039] To address the aforementioned technical problems, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the storage management software task information collection method.

[0040] This invention provides a method for collecting task information in storage management software, comprising: creating a module association table based on historical log information to record the association levels and dependencies between different modules in the storage management software; upon receiving a task failure signal, determining the directly and indirectly related modules corresponding to the currently failed module based on the created module association table, and calling a pre-built module information collector to collect the exception information of the currently failed module, its directly and indirectly related modules, and other exception information to obtain an exception information set; thereby, the cause of the current task failure can be determined based on the exception information set. Therefore, the technical solution provided by this application, based on the pre-created module association table, when a module fails to execute a task, not only collects the exception information of the current task module but also collects the exception information of modules directly and indirectly related to the current task module. The cause of the task failure is determined based on an accurately located and comprehensive exception information set, reducing developer intervention, improving the reliability of the entire storage system, and enhancing the user experience.

[0041] In addition, this application also provides an apparatus and medium for collecting task information of storage management software, which corresponds to the above-mentioned method for collecting task information of storage management software and has the same effect. Attached Figure Description

[0042] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0043] Figure 1 A flowchart illustrating a method for collecting task information in storage management software, provided as an embodiment of this application;

[0044] Figure 2 A structural diagram of a storage management software task information collection device provided in an embodiment of this application;

[0045] Figure 3 This is a structural diagram of a storage management software task information collection device provided in another embodiment of this application. Detailed Implementation

[0046] 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 of ordinary skill in the art without creative effort are within the protection scope of this application.

[0047] The core of this application is to provide a method, apparatus, and medium for collecting task information in storage management software. Based on a created module association table, the direct and indirect associated modules of the currently failed task module in the storage management software are determined, and the abnormal information of the currently failed task module, the directly associated modules, and the indirect associated modules is obtained, thereby obtaining comprehensive information on task failure and achieving the purpose of quickly locating the cause of task failure.

[0048] To enable those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the accompanying drawings and specific embodiments.

[0049] Browser / Server (B / S) architecture is a network structure that emerged after the rise of the Web. B / S architecture utilizes the increasingly mature Web browser technology to achieve powerful functions that previously required dedicated software, thus saving development costs.

[0050] Existing storage management software, based on a B / S architecture, provides a visual, user-friendly interface for managing storage systems, allowing users to manage storage resources through the interface. However, due to the complexity of the storage ecosystem, operations performed through this interface may fail due to various factors. Currently, many alarms and error messages are incomplete, preventing users from pinpointing the cause of failure and addressing errors or faults promptly. For example, when creating a storage pool, if the creation fails because the selected storage disk is already used or full, the software only notifies the user of the pool's failure without specifying the reason. This often requires developers to locate and troubleshoot the error, increasing manpower costs and providing a poor user experience.

[0051] To quickly obtain the reasons for task failures in storage management software and improve user experience, this application provides a method for collecting task information in storage management software. A module association table is created based on historical log information, and the directly associated and indirectly associated modules corresponding to the currently failed task are determined based on the created module association table, so as to collect all relevant abnormal signals of task failure and realize the rapid location of the cause of task failure.

[0052] Figure 1 A flowchart illustrating a method for collecting task information in storage management software provided in this application embodiment is shown below. Figure 1 As shown, the method includes:

[0053] S10: Create a module association table based on historical log information to record the association level of different modules in the storage management software and the dependencies between different modules;

[0054] In specific embodiments, different modules in the storage management software (e.g., alarm module, file system module, etc.) may have direct relationships, indirect relationships, or no relationships at all. Determining the dependencies between different modules based on historically stored log information means that the existence of direct or indirect relationships between different modules is determined based on the anomaly information of all modules in the historical log information. Therefore, the dependencies between different modules are stored in a module association table.

[0055] Furthermore, the frequency of anomaly information in different modules can be determined based on historical log information, and the association level of different modules can be set according to the frequency of anomaly information. It should be noted that the association level is used to characterize the degree of anomaly correlation that may occur when a module performs a certain task; that is, the probability of an anomaly occurring during task execution. The association level can be divided into important, medium, and general levels, or it can be divided into A, B, C, and D levels. This application does not limit the precision of the association level classification or the naming format.

[0056] Therefore, the module association table is obtained by storing the association levels of different modules and the dependencies between different modules.

[0057] S11: When a task failure signal is received, determine the directly associated and indirectly associated modules corresponding to the current task failure module based on the module association table;

[0058] When a signal indicating that a module has failed to execute a task is received, the directly and indirectly related modules corresponding to the module that failed are determined according to the module association table created in step S10. For example, when module A fails to execute a task, the directly related modules are determined to be B and C, and the indirectly related module is determined to be D, based on the module association table. Module B and module D have a direct relationship, while there is no relationship between module C and module D.

[0059] S12: Call the pre-built module information collector to collect the failure information of the current task module, the directly related module and the indirectly related module to obtain the exception information set;

[0060] S13: Determine the reason for the current task failure based on the set of exception information.

[0061] In fact, before obtaining the task failure signal, a module information collector is first constructed to collect abnormal signals generated by the modules. Therefore, in step S12, the pre-constructed module information collector is invoked to collect abnormal information generated by the current task failure module, directly related modules, and indirectly related modules to obtain an abnormal information set, and the cause of the current task failure is determined based on the collected abnormal information set.

[0062] When collecting exception information from failed modules, directly related modules, and indirectly related modules, the specific module information collector first determines the time node and time period corresponding to the start of task execution and the termination of task, and collects all exception information of each module within that time period.

[0063] Furthermore, when determining the cause of task failure, target anomaly information within a preset period is acquired, and the target anomaly signals within this preset period are classified to obtain classification results. Then, based on the classification results, the frequency of anomaly information appearing in the current task failure module, directly related modules, and indirectly related modules is determined, and the current association level corresponding to the current task failure module, directly related modules, and indirectly related modules is determined based on the frequency of the corresponding anomaly information of each module. Finally, the cause of the current task failure is determined based on the current association level.

[0064] The method for collecting task information in storage management software provided in this application includes: creating a module association table based on historical log information to record the association levels of different modules in the storage management software and the dependencies between different modules; when a task failure signal is received, determining the directly associated and indirectly associated modules corresponding to the currently failed module based on the created module association table, and calling a pre-built module information collector to collect the exception information of the currently failed module, the directly associated modules, and the indirectly associated modules to obtain an exception information set; thereby, the cause of the current task failure can be determined based on the exception information set. Therefore, the technical solution provided in this application, based on the pre-created module association table, when a module fails to execute a task, in addition to collecting the exception information of the current task module, also collects the exception information of modules directly and indirectly associated with the current task module, and determines the cause of the task failure based on an accurately located and comprehensive exception information set, reducing developer intervention, improving the reliability of the entire storage system, and enhancing the user experience.

[0065] In a specific embodiment, in order to further ensure the correlation between the currently acquired abnormal signals and the factors causing task failure, when collecting abnormal information of the current task failure module, directly related module and indirectly related module, all abnormal information of the previous task failure module, directly related module and indirectly related module within the time period from the start of the task to the end of the task is collected, and all abnormal signals of each task failure are stored to obtain an abnormal signal set.

[0066] The storage management software task information collection method provided in this application collects abnormal information from the current task failure module, the directly associated module, and the indirectly associated module during the time period from the start to the end of the current task. This avoids collecting abnormal signals from other time periods, which would reduce the accuracy of locating the cause of task failure, thereby ensuring the reliability of the storage system.

[0067] Based on the above embodiments, an abnormal information set is obtained by collecting various abnormal information from different task failure time periods. When determining the cause of the current task incident, in order to ensure the comprehensiveness and accuracy of the abnormal information, the target abnormal signal within a preset period is obtained and the target abnormal signal is classified, that is, it is determined which module each abnormal signal belongs to.

[0068] It should be noted that this application does not limit the duration of the preset period. However, in order to ensure the correlation between the acquired abnormal signals and the current task failure cause, that is, to ensure the accuracy of the finally determined task failure cause, the preset period is preferably based on the historical preset duration starting from the current moment. For example, if the preset period is 1 hour, then it is preferable to use the abnormal information from the previous 1 hour starting from the current moment as the target abnormal information.

[0069] After classifying and determining which module each abnormal signal belongs to, the frequency of abnormal information appearing in the current task failure module, directly related modules, and indirectly related modules is determined based on the classification results. In other words, the number of times abnormal information appears in the current task failure module, directly related modules, and indirectly related modules is determined, and then the current association level of each module is determined based on the number of abnormal information appearances.

[0070] Specifically, when the frequency of abnormal information exceeds a first threshold, the current association level is determined to be important; when the frequency of abnormal information exceeds a second threshold but is less than or equal to the first threshold, the current association level is determined to be medium; and when the frequency of abnormal information is not greater than the second threshold, the current association level is determined to be normal. Of course, this application does not limit the number of levels or the naming convention for the levels.

[0071] In fact, the higher the correlation level, the higher the correlation of the reasons for task failure. For example, in the alarm module, when the CPU is occupied to write data, when the memory usage exceeds 80%, the writing task cannot continue. At this time, when all the abnormal information of the relevant modules of the task failure are obtained, the abnormal information generated by the alarm module should be the most. Therefore, the correlation level of the alarm module is the highest, and correspondingly, the probability of the task failure caused by the alarm module is the highest.

[0072] After determining the current relevance of each module, appropriate processing solutions can be recommended to users based on the current relevance level. For example, when performing batch volume deletion operations, if deletion fails and the volume to be deleted has a volume mapping, it is understandable that volumes with volume mappings cannot be directly deleted. In this case, the deletion information can be sent to the visualization interface for users to view, and the module information related to the failed deletion task can also be transmitted to the visualization interface. Furthermore, the recommended operation solution of "removing the mapping before deleting" can be displayed on the visualization interface, allowing users to proceed directly to the next step based on the recommendation.

[0073] Of course, for more complex reasons for task failure, all related module information and corresponding abnormal signals can be transmitted to the visualization interface. That is, the information of the module that failed in the current task, as well as the information of the modules that are directly and indirectly related to the module that failed in the current task and the abnormal signals generated by each module are transmitted to the visualization interface so that users can analyze and locate the reason for the task failure based on the information currently displayed.

[0074] In other words, the technical solution provided in this application, in addition to providing relevant exception information for task failure, also provides corresponding processing recommendations. Of course, after transmitting the recommended solutions and exception information to the visual interface, the user can determine the factors contributing to the task failure and select the corresponding processing measures.

[0075] The method for collecting task information in storage management software provided in this application, when determining the cause of current task failure based on a set of abnormal information, first classifies the target abnormal information within a preset period to obtain classification results. Based on the classification results, the frequency of abnormal information occurring in the current task failure module, directly related modules, and indirectly related modules is determined. Then, based on the frequency of abnormal information corresponding to each module, the current association level corresponding to the current task failure module, directly related modules, and indirectly related modules is determined. After determining each current association level, the cause of current task failure can be determined based on the association level. Therefore, all abnormal information generated by the directly and indirectly related modules of the current task failure can be provided, ensuring comprehensive information while enabling rapid location of the cause of task failure, thereby improving the user experience.

[0076] Based on the above embodiments, in order to further ensure the accuracy of locating and determining the cause of task failure, after determining the current task failure module, the current association level of the directly associated module and the indirectly associated module according to the frequency of the abnormal information corresponding to each module, it is determined whether the current association level of the current task failure module, the directly associated module and the indirectly associated module is the same as the association level in the module association table. If they are not the same, the module association table is updated based on the current association level.

[0077] In other words, after determining the current association level of all modules associated with task failure, it is determined whether the association level of the currently failed module, its directly associated modules, and its indirectly associated modules has changed. If it has changed, the association level in the module association table is updated.

[0078] The method for collecting task information in storage management software provided in this application update the module association table based on the current association level when the current association level of the module, directly associated module, and indirectly associated module that are determined to be the current task failure module is different from the association level in the module association table. This ensures the accuracy of the module association table information when the next task failure analysis is performed, thereby realizing the dynamic management of the module association table.

[0079] In practice, users may not care about the abnormal signals generated by a directly or indirectly related module corresponding to the module that failed in the current task. In this case, in order to avoid obtaining too many abnormal signals and causing errors when analyzing the cause of task failure, the module association table is modified according to the user-triggered self-modification instruction when the user triggers the self-modification instruction. For example, a directly or indirectly related module of a module is deleted from the module association table.

[0080] The method for collecting task information in storage management software provided in this application, when a self-modification instruction is obtained, modifies the module association table according to the self-modification instruction, thereby enabling users to make self-adjustments to the module association table and improving the user experience.

[0081] During implementation, when creating a module association table based on historical log information to record the association level of different modules in the storage management software and the dependencies between different modules, the abnormal information in the historical log information is classified to determine the frequency of abnormal information in different modules, and the association level of different modules is determined based on the frequency of abnormal information corresponding to the module.

[0082] Furthermore, it is understandable that the abnormal information of all modules in the historical log information can determine whether there is a direct or indirect relationship between different modules. Therefore, the correlation between different modules can be determined based on the historical log information to determine the dependency relationship between different modules, and the dependency relationship between different modules can be stored in the module association table.

[0083] It should be noted that, in addition to creating the module association table based on historical log information, since the switch personnel understand the dependencies between modules, it can also be created by the developers.

[0084] The method for collecting task information in storage management software provided in this application creates a module association table based on historical log information, so as to quickly locate the cause of task failure based on the module association table, thereby ensuring the reliability of the entire storage system.

[0085] In the above embodiments, the method for collecting task information of storage management software has been described in detail. This application also provides an embodiment of a device for collecting task information of storage management software. It should be noted that this application describes the embodiment of the device from two perspectives: one is based on functional modules, and the other is based on hardware structure.

[0086] Figure 2 A structural diagram of a storage management software task information collection device provided in this application embodiment is shown below. Figure 2 As shown, the device includes:

[0087] Create module 10, which is used to create a module association table based on historical log information to record the association level of different modules in the storage management software and the dependency relationship between different modules;

[0088] The first determining module 11 is used to determine the directly associated module and indirectly associated module corresponding to the current task failure module according to the module association table when a task failure signal is obtained.

[0089] Module 12 is invoked to call a pre-built module information collector to collect the exception information of the currently failed modules, directly associated modules and indirectly associated modules to obtain an exception information set;

[0090] The second determination module 13 is used to determine the reason for the failure of the current task based on the set of abnormal information.

[0091] Since the embodiments of the apparatus and the embodiments of the method correspond to each other, please refer to the description of the embodiments of the method for the embodiments of the apparatus, which will not be repeated here.

[0092] The device for collecting task information in storage management software provided in this application includes: creating a module association table based on historical log information to record the association levels and dependencies between different modules in the storage management software; upon receiving a task failure signal, determining the directly and indirectly related modules corresponding to the currently failed module based on the created module association table, and calling a pre-built module information collector to collect the exception information of the currently failed module, its directly and indirectly related modules, and other exception information to obtain an exception information set; thereby, the cause of the current task failure can be determined based on the exception information set. Therefore, the technical solution provided in this application, based on the pre-created module association table, when a module fails to execute a task, not only collects the exception information of the current task module but also collects the exception information of modules directly and indirectly related to the current task module. The cause of the task failure is determined based on an accurately located and comprehensive exception information set, reducing developer intervention, improving the reliability of the entire storage system, and enhancing the user experience.

[0093] Figure 3 A structural diagram of a storage management software task information collection device provided in another embodiment of this application is shown below. Figure 3 As shown, the device for collecting task information of storage management software includes: a memory 20 for storing computer programs;

[0094] The processor 21 is configured to implement the steps of the method for collecting task information of storage management software as described in the above embodiments when executing a computer program.

[0095] The device for collecting task information of storage management software provided in this embodiment may include, but is not limited to, smartphones, tablets, laptops, or desktop computers.

[0096] The processor 21 may include one or more processing cores, such as a quad-core processor or an octa-core processor. The processor 21 may be implemented using at least one of the following hardware forms: Digital Signal Processor (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 21 may also include a main processor and a coprocessor. The main processor, also known as the Central Processing Unit (CPU), is used to process data in the wake-up state; the coprocessor is a low-power processor used to process data in the standby state. In some embodiments, the processor 21 may integrate a Graphics Processing Unit (GPU), which is responsible for rendering and drawing the content to be displayed on the screen. In some embodiments, the processor 21 may also include an Artificial Intelligence (AI) processor, which is used to handle computational operations related to machine learning.

[0097] The memory 20 may include one or more computer-readable storage media, which may be non-transitory. The memory 20 may also include high-speed random access memory and non-volatile memory, such as one or more disk storage devices or flash memory devices. In this embodiment, the memory 20 is used to store at least the following computer program 201, which, after being loaded and executed by the processor 21, is capable of implementing the relevant steps of the storage management software task information collection method disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202 and data 203, and the storage method may be temporary or permanent storage. The operating system 202 may include Windows, Unix, Linux, etc. The data 203 may include, but is not limited to, the relevant data involved in the storage management software task information collection method.

[0098] In some embodiments, the storage management software task information collection device may further include a display screen 22, an input / output interface 23, a communication interface 24, a power supply 25, and a communication bus 26.

[0099] Those skilled in the art will understand that Figure 3 The structure shown does not constitute a limitation on the means of collecting task information for storage management software and may include more or fewer components than shown.

[0100] The storage management software task information collection apparatus provided in this application includes a memory and a processor. When the processor executes a program stored in the memory, it can implement the following method: a method for collecting storage management software task information.

[0101] The storage management software task information collection device provided in this application embodiment, based on a pre-created module association table, when a module fails to execute a task, in addition to collecting the exception information of the current task module, also collects the exception information of modules directly and indirectly associated with the current task module. Based on the accurately located and comprehensive set of exception information, the cause of task failure is determined, reducing the intervention of developers, improving the reliability of the entire storage system, and enhancing the user experience.

[0102] Finally, this application also provides an embodiment corresponding to a computer-readable storage medium. The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps described in the above method embodiments.

[0103] It is understood that if the methods in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and executes all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0104] The foregoing has provided a detailed description of a method, apparatus, and medium for collecting task information in storage management software as provided in this application. The various embodiments in the 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. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

[0105] It should also be noted that, in this specification, 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.

Claims

1. A method for collecting task information in storage management software, characterized in that, include: Create a module association table based on historical log information to record the association level of different modules in the storage management software and the dependencies between different modules; Upon receiving a task failure signal, the direct and indirect associated modules corresponding to the current task failure module are determined based on the module association table. A pre-built module information collector is invoked to collect the current task failure modules, the directly associated modules, and the indirectly associated modules to obtain an exception information set; The reason for the current task failure is determined based on the set of abnormal information. The collection of exception information from the current task failure module, the directly related module, and the indirectly related module yields an exception information set including: Collect abnormal information of the current task failure module, the directly associated module, and the indirectly associated module during the time period from the start of the task to the end of the task. The abnormal information collection obtained from each failed task is stored to obtain the abnormal information set; The step of determining the reason for the current task failure based on the set of abnormal information includes: The abnormal information of the target within the preset period is classified to obtain the classification result; Based on the classification results, the frequency of abnormal information occurrences in the current task failure module, the directly associated module, and the indirectly associated module is determined respectively; The current task failure module is determined based on the frequency of the corresponding abnormal information of each module, and the current association level is determined for the directly associated module and the indirectly associated module. The reason for the current task failure is determined based on the current association level described above; The current task failure module is determined based on the frequency of abnormal information corresponding to each module. The current association level of the directly associated module and the indirectly associated module includes: When the frequency of abnormal information exceeds the first threshold, the current association level is determined to be of importance. When the frequency of abnormal information is greater than the second threshold and less than or equal to the first threshold, the current association level is determined to be medium. When the frequency of abnormal information is not greater than the second threshold, the current association level is determined to be the general level; After determining the current task failure module, the current association level of the directly associated module, and the indirectly associated module based on the frequency of the corresponding exception information of each module, the process further includes: Determine whether the current association level of the module that failed the current task, the directly associated module, and the indirectly associated module are the same as the association level in the module association table; If they are different, the module association table is updated based on the current association level.

2. The method for collecting task information in storage management software according to claim 1, characterized in that, Also includes: Upon receiving a self-modification instruction, the module association table is modified according to the self-modification instruction.

3. The method for collecting task information in storage management software according to claim 1, characterized in that, The step of creating a module association table based on historical log information to record the association levels of different modules in the storage management software and the dependencies between different modules includes: The abnormal information in the historical log information is classified to determine the frequency of abnormal information in different modules; The association level for different modules is determined based on the frequency of the abnormal information corresponding to the modules. The correlation between different modules is determined based on the historical log information to determine the dependencies between different modules.

4. A device for collecting task information of storage management software, characterized in that, include: Create a module to create a module association table based on historical log information to record the association level of different modules in the storage management software and the dependencies between different modules; The first determining module is used to determine the directly associated module and indirectly associated module corresponding to the current task failure module according to the module association table when a task failure signal is obtained. The calling module is used to call a pre-built module information collector to collect the current task failure modules, the directly associated modules and the indirectly associated modules to obtain an exception information set; The second determining module is used to determine the reason for the current task failure based on the set of abnormal information. The calling module is also used for: Collect abnormal information of the current task failure module, the directly associated module, and the indirectly associated module during the time period from the start of the task to the end of the task. The abnormal information collection obtained from each failed task is stored to obtain the abnormal information set; The second determining module is further configured to: The abnormal information of the target within the preset period is classified to obtain the classification result; Based on the classification results, the frequency of abnormal information occurrences in the current task failure module, the directly associated module, and the indirectly associated module is determined respectively; The current task failure module is determined based on the frequency of the corresponding abnormal information of each module, and the current association level is determined for the directly associated module and the indirectly associated module. The reason for the current task failure is determined based on the current association level described above; The second determining module is further configured to: When the frequency of abnormal information exceeds the first threshold, the current association level is determined to be of importance. When the frequency of abnormal information is greater than the second threshold and less than or equal to the first threshold, the current association level is determined to be medium. When the frequency of abnormal information is not greater than the second threshold, the current association level is determined to be the general level; The second determining module is further configured to: Determine whether the current association level of the module that failed the current task, the directly associated module, and the indirectly associated module are the same as the association level in the module association table; If they are different, the module association table is updated based on the current association level.

5. A device for collecting task information of storage management software, characterized in that, Includes memory used to store computer programs; A processor, configured to implement the steps of the method for collecting task information of storage management software as described in any one of claims 1 to 3 when executing the computer program.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the storage management software task information collection method as described in any one of claims 1 to 3.

Images