CN115168095A - Method, device and medium for collecting storage management software task information - Google Patents

Method, device and medium for collecting storage management software task information Download PDF

Info

Publication number
CN115168095A
CN115168095A CN202210890234.2A CN202210890234A CN115168095A CN 115168095 A CN115168095 A CN 115168095A CN 202210890234 A CN202210890234 A CN 202210890234A CN 115168095 A CN115168095 A CN 115168095A
Authority
CN
China
Prior art keywords
module
association
information
task
abnormal information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210890234.2A
Other languages
Chinese (zh)
Inventor
马聪
谢鹏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Inspur Jinan data Technology Co ltd
Original Assignee
Inspur Jinan data Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Inspur Jinan data Technology Co ltd filed Critical Inspur Jinan data Technology Co ltd
Priority to CN202210890234.2A priority Critical patent/CN115168095A/en
Publication of CN115168095A publication Critical patent/CN115168095A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0727Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a storage system, e.g. in a DASD or network based storage system
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766Error or fault reporting or storing
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/079Root cause analysis, i.e. error or fault diagnosis

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application relates to the technical field of storage, and discloses a method, a device and a medium for collecting storage management software task information, wherein the method comprises the following steps: and when the task fails, determining a direct correlation module and an indirect correlation module corresponding to the current task failure module according to the module correlation table, calling a pre-constructed module information collector to collect the current task failure module, obtaining abnormal information sets from the abnormal information of the direct correlation module and the indirect correlation module, and determining the reason of the current task failure according to the abnormal information sets. Therefore, when the module fails to execute the task, according to the pre-established module association table, the abnormal information of the current task module is collected, the abnormal information of the module directly or indirectly associated with the current task module is also collected, the reason of the task failure is determined according to the accurately positioned and comprehensive abnormal information, and the reliability of the storage system is improved.

Description

Method, device and medium for collecting storage management software task information
Technical Field
The present application relates to the field of storage technologies, and in particular, to a method, an apparatus, and a medium for collecting task information of storage management software.
Background
A Browser/Server (B/S) structure is a network structure after Web is started, and the B/S structure utilizes a mature Web Browser technology to realize powerful functions which can be realized only by special software in the past, so that the development cost is saved.
The existing storage management software realizes the visual interface management of the storage system based on the B/S architecture, and a user can realize the storage resource management through interface operation. Currently, due to the complex storage ecological environment, the operation executed by the interface may cause the task execution failure due to various factors, however, many current alarms or error prompt messages are not comprehensive enough, so that the user cannot determine the reason of the task failure, and the error or fault that occurs cannot be eliminated in time. For example, when a task of creating a storage pool is executed, if the creation fails due to the borrowing of the selected storage disk or the full disk, the user can only be reminded of the failure of the current storage pool currently, and the user cannot be informed of the specific failure reason. At this time, research and development personnel are often required to locate and eliminate errors or faults, so that the labor cost is increased, and meanwhile, poor experience is brought to users.
Therefore, how to quickly acquire the reason for the task failure in the storage management software and improve the user experience is a problem to be solved urgently by the technical personnel in the field.
Disclosure of Invention
The application aims to provide a method, a device and a medium for collecting task information of storage management software, which are used for quickly positioning reasons of task failure in the storage management software, reducing access of developers and improving user experience.
In order to solve the above technical problem, the present application provides a method for collecting task information of storage management software, including:
creating a module association table according to the historical log information so as to record association levels of different modules in the storage management software and dependency relationships among the different modules;
when a task failure signal is obtained, determining a direct association module and an indirect association module corresponding to the current task failure module according to the module association table;
calling a pre-constructed module information collector to collect the current task failure module, wherein abnormal information of the direct correlation module and the indirect correlation module obtains an abnormal information set;
and determining the reason of the current task failure according to the abnormal information set.
Preferably, the collecting the abnormal information of the current task failure module, the obtaining of the abnormal information set by the direct correlation module and the indirect correlation module includes:
collecting abnormal information of the current task failure module, the direct correlation module and the indirect correlation module in a time period from the start of the current task to the termination of the current task;
and storing the abnormal information collected by the previous task failure to obtain the abnormal information set.
Preferably, the determining the reason for the current task failure according to the abnormal information set includes:
classifying the target abnormal information in a preset period to obtain a classification result;
respectively determining the frequency of abnormal information of the current task failure module, the direct association module and the indirect association module according to the classification result;
determining the current task failure module according to the frequency of the abnormal information corresponding to each module, and the current association levels corresponding to the direct association module and the indirect association module;
and determining the reason of the current task failure according to each current association grade.
Preferably, the determining the current task failure module according to the frequency of the abnormal information corresponding to each module, and the current association levels corresponding to the direct association module and the indirect association module include:
when the frequency of the abnormal information is greater than a first threshold value, determining that the current association grade is an important grade;
when the frequency of the abnormal information is greater than a second threshold value and less than or equal to the first threshold value, determining that the current association level is a medium level;
when the frequency of the abnormal information is not greater than the second threshold value, the current association level is determined to be a general level.
Preferably, after the determining the current task failure module according to the frequency of the abnormal information corresponding to each module, the current association levels corresponding to the direct association module and the indirect association module further include:
determining whether the current association levels corresponding to the direct association module and the indirect association module are the same as the association levels in the module association table or not by the current task failure module;
and if not, updating the module association table based on the current association level.
Preferably, the method for collecting task information of storage management software further includes:
and when an autonomous modification instruction is acquired, modifying the module association table according to the autonomous modification instruction.
Preferably, the creating a module association table according to the historical log information to record association levels of different modules and dependencies among the different modules in the storage management software includes:
classifying various abnormal information in the historical log information to determine the frequency of the abnormal information of different modules;
determining the association levels corresponding to different modules according to the frequency of the abnormal information corresponding to the modules;
and determining the association degree between different modules according to the historical log information so as to determine the dependency relationship between different modules.
In order to solve the above technical problem, the present application further provides a device for collecting task information of storage management software, including:
the creating module is used for creating a module association table according to the historical log information so as to record association levels of different modules and dependency relationships among the different modules in the storage management software;
the first determining module is used for determining a direct association module and an indirect association module corresponding to the current task failure module according to the module association table when the task failure signal is obtained;
the calling module is used for calling a pre-constructed module information collector to collect the current task failure module, and the abnormal information of the direct correlation module and the indirect correlation module obtains an abnormal information set;
and the second determining module is used for determining the reason of the current task failure according to the abnormal information set.
In order to solve the above technical problem, the present application further provides an apparatus for storing and managing software task information, which includes a memory for storing a computer program;
and the processor is used for realizing the steps of the storage management software task information collection method when executing the computer program.
In order to solve the above technical problem, the present application further provides a computer-readable storage medium, on which a computer program is stored, and the computer program, when executed by a processor, implements the steps of the method for collecting task information of storage management software.
The invention provides a method for collecting task information of storage management software, which comprises the following steps: the method comprises the steps of creating a module association table according to historical log information to record association levels of different modules in storage management software and dependency relationships among the different modules, determining a direct association module and an indirect association module corresponding to a current task failure module according to the created module association table when a task failure signal is obtained, calling a pre-constructed module information collector to collect the current task failure module, and obtaining an abnormal information set according to abnormal information of the direct association module and the indirect association module, so that the reason of current task failure can be determined according to the abnormal information set. Therefore, according to the technical scheme provided by the application, when the module executes the task and fails, the abnormal information of the current task module is collected, the abnormal information of the module directly and indirectly associated with the current task module is also collected according to the pre-established module association table, the reason of the task failure is determined according to the accurately positioned and comprehensive abnormal information set, the intervention of developers is reduced, the reliability of the whole storage system is improved, and meanwhile, the user experience is improved.
In addition, the application also provides a device and a medium for collecting the task information of the storage management software, which correspond to the method for collecting the task information of the storage management software, and the effects are the same.
Drawings
In order to more clearly illustrate the embodiments of the present application, the drawings needed for the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings can be obtained by those skilled in the art without inventive effort.
FIG. 1 is a flowchart of a method for collecting task information of storage management software according to an embodiment of the present application;
FIG. 2 is a block diagram of an apparatus for storing management software task information provided in an embodiment of the present application;
fig. 3 is a block diagram of an apparatus for collecting task information of storage management software according to another embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments in the present application without any creative effort belong to the protection scope of the present application.
The core of the application is to provide a method, a device and a medium for collecting task information of storage management software, a direct correlation module and an indirect correlation module of a current task failure module in the storage management software are determined according to a created module correlation table, and abnormal information of the current task failure module, the direct correlation module and the indirect correlation module is obtained, so that comprehensive information of task failure is obtained, and the purpose of quickly locating the reason of task failure is achieved.
In order that those skilled in the art will better understand the disclosure, the following detailed description will be given with reference to the accompanying drawings.
A Browser/Server (B/S) structure is a network structure after Web is started, and the B/S structure utilizes a mature Web Browser technology to realize powerful functions which can be realized only by special software in the past, so that the development cost is saved.
The existing storage management software realizes the visual interface management of the storage system based on the B/S architecture, and a user can realize the storage resource management through interface operation. Currently, due to the complex storage ecological environment, the operation executed by the interface may cause the task execution failure due to various factors, however, many current alarms or error prompt messages are not comprehensive enough, so that the user cannot determine the reason of the task failure, and the error or fault that occurs cannot be eliminated in time. For example, when a task of creating a storage pool is executed, if the creation fails due to the borrowing of the selected storage disk or the full disk, the user can only be reminded of the failure of the current storage pool currently, and the user cannot be informed of the specific failure reason. At this time, research and development personnel are often required to locate and eliminate errors or faults, so that the labor cost is increased, and meanwhile, poor experience is brought to users.
In order to achieve quick acquisition of reasons for task failure in storage management software and improve user experience, embodiments of the present application provide a method for collecting task information of storage management software, a module association table is created according to historical log information, and a direct association module and an indirect association module corresponding to a current task failure module are determined according to the created module association table, so as to collect all relevant abnormal signals of task failure, and realize quick positioning of reasons for task failure.
Fig. 1 is a flowchart of a method for collecting storage management software task information according to an embodiment of the present application, where as shown in fig. 1, the method includes:
s10: creating a module association table according to the historical log information so as to record association levels of different modules in the storage management software and dependency relationships among the different modules;
in particular embodiments, a direct relationship or an indirect relationship may exist between different modules (e.g., an alarm module, a file system module, etc.) in the storage management software, and certainly, no relationship may exist. Determining the dependency relationship between different modules according to the history stored log information, wherein it can be understood that whether a direct relationship or an indirect relationship exists between different modules is determined according to the abnormal information of all modules in the history log information, and thus, the dependency relationship between different modules is stored in the module association table.
In addition, the frequency of abnormal information of different modules can be determined according to the historical log information, and the association levels of different modules are set according to the frequency of abnormal information. It should be noted that the association level is used to characterize the degree of association that an exception occurs when a module executes a certain task, that is, the probability of an exception occurring when a task is executed. The association level may be divided into an important level, a medium level and a general level, and may also be divided into an a level, a B level, a C level and a D level, and the division precision and the naming form of the association level are not limited in the present application.
Therefore, the association levels of different modules and the dependency relationship among different modules are stored to obtain a module association table.
S11: when a task failure signal is obtained, determining a direct correlation module and an indirect correlation module corresponding to a current task failure module according to a module correlation table;
when a signal that a certain module fails to execute a task is acquired, a direct association module and an indirect association module corresponding to the current task failure module are determined according to the module association table created in step S10. For example, when the module a fails to execute a certain task, it is determined that the direct association modules are B and C and the indirect association module is D according to the module association table, where the module B and the module D are in a direct association relationship, and the module C and the module D are not in a relationship.
S12: calling a pre-constructed module information collector to collect current task failure modules, and obtaining abnormal information sets by the abnormal information of the direct correlation modules and the indirect correlation modules;
s13: and determining the reason of the current task failure according to the abnormal information set.
In fact, before acquiring the task failure signal, a module information collector is constructed for collecting the abnormal signal generated by the module. Therefore, in step S12, a pre-constructed module information collector is called to collect the abnormal information generated by the current task failure module, the direct association module and the indirect association module to obtain an abnormal information set, and the reason for the current task failure is determined according to the collected abnormal information set.
When the specific module information collector collects the abnormal information of the task failure module, the direct correlation module and the indirect correlation module before, the time node and the time period corresponding to the task from the start to the termination of the task are determined, and all the abnormal information of each module in the time period is collected.
Further, when the reason of the task failure is determined, target abnormal information in a preset period is obtained, and the target abnormal signals in the preset period are classified to obtain a classification result. And then, respectively determining the frequency of abnormal information of the current task failure module, the direct correlation module and the indirect correlation module according to the classification result, and determining the current correlation level corresponding to the current task failure module, the direct correlation module and the indirect correlation module based on the frequency of the abnormal information corresponding to the modules. And finally, determining the reason of the current task failure according to the current association level.
The method for collecting task information of storage management software provided by the embodiment of the application comprises the following steps: the method comprises the steps of creating a module association table according to historical log information to record association levels of different modules in storage management software and dependency relationships among the different modules, determining a direct association module and an indirect association module corresponding to a current task failure module according to the created module association table when a task failure signal is obtained, calling a pre-constructed module information collector to collect the current task failure module, and obtaining an abnormal information set according to abnormal information of the direct association module and the indirect association module, so that the reason of current task failure can be determined according to the abnormal information set. Therefore, according to the technical scheme provided by the application, when the module executes the task and fails, the abnormal information of the current task module is collected, the abnormal information of the module directly and indirectly associated with the current task module is also collected, the reason of the task failure is determined according to the accurately positioned and comprehensive abnormal information set, the intervention of developers is reduced, the reliability of the whole storage system is improved, and the user experience is improved.
In a specific embodiment, in order to further ensure the relevance between the currently acquired abnormal signals and the task failure factors, when the abnormal information of the current task failure module, the direct association module and the indirect association module is collected, all the abnormal information of the current task from the task start to the task termination time period, the direct association module and the indirect association module, and all the abnormal signals of the word task failure are stored to obtain an abnormal signal set.
According to the method for collecting the task information of the storage management software, the current task failure module, the direct association module and the indirect association module collect abnormal information of the current task in the time period from the start of the task to the termination of the task, the accuracy of locating the task failure reason due to the fact that abnormal signals in other time periods are collected is avoided, and the reliability of a storage system is further guaranteed.
On the basis of the above embodiment, an abnormal information set is obtained according to various abnormal information collected in different task failure time periods, and when the cause of the current task event change is determined, in order to ensure the completeness and the accuracy of the abnormal information, a target abnormal signal in a preset period is obtained, and the target abnormal signal is classified, that is, which module each abnormal signal belongs to is determined.
It should be noted that, in the present application, the duration of the preset period is not limited, but in order to ensure the correlation between the acquired abnormal signal and the current task failure reason, that is, to ensure the accuracy of the finally determined task failure reason, the preset period preferably acquires the historical preset duration as the period from the current time as the preset period. For example, if the preset period is 1 hour, it is preferable to use the abnormality information within the first 1 hour from the current time as the target abnormality information.
After determining which module different abnormal signals belong to by classification, respectively determining the frequency of abnormal information of the current task failure module, the direct association module and the indirect association module according to the classification result, namely determining the frequency of the abnormal information of the current task failure module, the direct association module and the indirect association module, and then determining the current association grade corresponding to each module according to the frequency of the abnormal information.
Specifically, when the frequency of the abnormal information is greater than a first threshold, the current association level is determined to be an important level, when the frequency of the abnormal information is greater than a second threshold and is less than or equal to the first threshold, the current association level is determined to be a medium level, and when the frequency of the abnormal information is not greater than the second threshold, the current association level is determined to be a general level. Of course, the number of the grade divisions and the naming mode of the grade are not limited in the present application.
In fact, the higher the current association level is, the higher the association level of the cause of the task failure is, for example, when the CPU is occupied in the alarm module to write data, when the memory occupation exceeds 80%, the writing task cannot be continued, and when all the abnormal information in each related module of the task failure is obtained at this time, the maximum amount of abnormal information generated by the alarm module is required, so the association level of the alarm module is the highest, and correspondingly, the probability of the task failure caused by the alarm module is the highest.
After the current association degree of each module is determined, a corresponding processing scheme can be recommended to the user according to the current association degree level. For example, when batch volume deletion operation is performed, if deletion failure occurs and a volume to be deleted has volume mapping, it can be understood that the volume having the volume mapping cannot be directly deleted, at this time, deletion information can be sent to a visual interface so as to be checked by a user, module information associated with deletion task failure is transmitted to the visual interface, an operation recommendation scheme of 'deleting after contact mapping' is displayed on the visual interface, and at this time, the user can directly perform the next operation according to the recommendation.
Of course, for more complex reasons of task failure, all relevant module information and abnormal signals generated correspondingly can be transmitted to the visual interface, that is, the current task failure module information, the module information directly and indirectly relevant to the current task failure module, and the abnormal signals generated by each module are transmitted to the visual interface, so that a user can analyze and position the reasons of task failure according to the currently displayed information.
That is to say, the technical solution provided in the embodiment of the present application provides a corresponding processing recommendation scheme in addition to the relevant abnormal information of the corresponding task failure. Of course, after the recommended scheme and the abnormal information are transmitted to the visual interface, the user determines the task failure factor and selects the corresponding processing measure.
According to the method for collecting task information of storage management software, when the reason of current task failure is determined according to an abnormal information set, target abnormal information in a preset period is classified to obtain a classification result, current task failure modules are determined according to the classification result, the frequency of abnormal information appearing in the direct association modules and the indirect association modules is determined according to the classification result, then the current task failure modules are determined according to the frequency of the abnormal information corresponding to the modules, the current association levels corresponding to the direct association modules and the indirect association modules are determined, and the reason of current task failure can be determined according to the association levels after the current association levels are determined. Therefore, all abnormal information generated by the association module and the indirect association module related to the current task failure can be provided, the information is comprehensive, and meanwhile, the reason for the task failure can be quickly positioned, so that the user experience is improved.
On the basis of the embodiment, in order to further ensure the accuracy of task failure reason positioning and determination, after determining the current task failure module according to the frequency of the abnormal information corresponding to each module, and determining the current association levels corresponding to the direct association module and the indirect association module, the current task failure module is determined, whether the current association levels corresponding to the direct association module and the indirect association module are the same as the association levels in the module association table or not is determined, and if not, the module association table is updated based on the current association levels.
That is, after determining the current association levels of all modules associated with the task failure, determining whether the association levels corresponding to the current task failure module, the direct association module and the indirect association module are changed, and if the association levels are changed, updating the association levels in the module association table.
According to the method for collecting the task information of the storage management software, when the current task failure module is determined, and the current association levels corresponding to the direct association module and the indirect association module are different from the association levels in the module association table, the module association table is updated based on the current association levels, so that the accuracy of the module association table information is guaranteed when the task failure analysis is performed next time, and the dynamic management of the module association table is achieved.
In fact, in implementation, a user may not care about an abnormal signal generated by a certain direct correlation module or a certain indirect correlation module corresponding to the current task failure module, and at this time, in order to avoid acquiring too many abnormal signals and causing an error when analyzing a task failure reason, when an autonomous modification instruction triggered by the user is acquired, the module correlation table is modified according to the autonomous modification instruction, for example, a certain direct correlation module or a certain indirect correlation module of a certain module is deleted in the module correlation table.
According to the method for collecting the task information of the storage management software, when the autonomous modification instruction is obtained, the module association table is modified according to the autonomous modification instruction, so that autonomous adjustment of the module association table by a user is achieved, and user experience is improved.
In implementation, when a module association table is created according to the historical log information to record association levels of different modules and dependency relationships among the different modules in the storage management software, the abnormal information in the historical log information is classified to determine the frequency of the abnormal information of the different modules, and the association levels corresponding to the different modules are determined according to the frequency of the abnormal information corresponding to the modules.
In addition, it can be understood that whether a direct relationship or an indirect relationship exists between different modules can be determined according to the abnormal information of all modules in the historical log information, so that the association degree between different modules is determined according to the historical log information to determine the dependency relationship between different modules, and the dependency relationship between different modules is stored in the module association table.
It should be noted that, when creating the module association table, the creation may be performed according to history log information, and since the switching personnel know the dependency relationship between the modules, the creation may also be performed by the developer.
According to the method for collecting the task information of the storage management software, the module association table is created according to the historical log information, so that the reason for the task failure can be quickly positioned according to the module association table, and the reliability of the whole storage system is further ensured.
In the foregoing embodiments, the method for collecting task information of storage management software is described in detail, and the present application also provides an embodiment corresponding to the apparatus for collecting task information of storage management software. It should be noted that the present application describes the embodiments of the apparatus portion from two perspectives, one is based on the functional module, and the other is based on the hardware structure.
Fig. 2 is a structural diagram of an apparatus for collecting storage management software task information according to an embodiment of the present application, where as shown in fig. 2, the apparatus includes:
the creating module 10 is used for creating a module association table according to the historical log information so as to record the association levels of different modules and the dependency relationship among the different modules in the storage management software;
the first determining module 11 is configured to determine, according to the module association table, a direct association module and an indirect association module corresponding to the current task failure module when the task failure signal is acquired;
the calling module 12 is used for calling a pre-constructed module information collector to collect the current task failure module, and obtaining an abnormal information set by the abnormal information of the direct correlation module and the indirect correlation module;
and a second determining module 13, configured to determine, according to the abnormal information set, a reason why the current task fails.
Since the embodiments of the apparatus portion and the method portion correspond to each other, please refer to the description of the embodiments of the method portion for the embodiments of the apparatus portion, which is not repeated here.
The device for collecting task information of storage management software provided by the embodiment of the application comprises the following components: the method comprises the steps of creating a module association table according to historical log information to record association levels of different modules in storage management software and dependency relations among the different modules, when a task failure signal is obtained, determining a direct association module and an indirect association module corresponding to a current task failure module according to the created module association table, calling a pre-constructed module information collector to collect the current task failure module, and obtaining an abnormal information set according to abnormal information of the direct association module and the indirect association module, so that the reason of the current task failure can be determined according to the abnormal information set. Therefore, according to the technical scheme provided by the application, when the module executes the task and fails, the abnormal information of the current task module is collected, the abnormal information of the module directly and indirectly associated with the current task module is also collected according to the pre-created module association table, the reason of the task failure is determined according to the accurately positioned and comprehensive abnormal information set, the intervention of developers is reduced, the reliability of the whole storage system is improved, and meanwhile, the user experience is improved.
Fig. 3 is a block diagram of an apparatus for collecting task information of storage management software according to another embodiment of the present application, and as shown in fig. 3, the apparatus for collecting task information of storage management software includes: a memory 20 for storing a computer program;
a processor 21 for implementing the steps of the method for storage management software task information collection as mentioned in the above embodiments when executing the computer program.
The device for collecting task information of storage management software provided by the embodiment may include, but is not limited to, a smart phone, a tablet computer, a notebook computer, or a desktop computer.
The processor 21 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and the like. The Processor 21 may be implemented in at least one hardware form of a Digital Signal Processor (DSP), a Field-Programmable Gate Array (FPGA), and a Programmable Logic Array (PLA). The processor 21 may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 21 may be integrated with an image processor (GPU), and the GPU is responsible for rendering and drawing content required to be displayed on the display screen. In some embodiments, the processor 21 may further include an Artificial Intelligence (AI) processor for processing computing operations related to machine learning.
The memory 20 may include one or more computer-readable storage media, which may be non-transitory. Memory 20 may also include high speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In this embodiment, the memory 20 is at least used for storing the computer program 201, wherein after being loaded and executed by the processor 21, the computer program can implement the relevant steps of the method for collecting task information of storage management software disclosed in any of the foregoing embodiments. In addition, the resources stored in the memory 20 may also include an operating system 202, data 203, and the like, and the storage manner may be a transient storage manner or a permanent storage manner. Operating system 202 may include, among others, windows, unix, linux, and the like. Data 203 may include, but is not limited to, relevant data involved in the method of storing management software task information collections.
In some embodiments, the storage management software task information collecting 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.
Those skilled in the art will appreciate that the architecture illustrated in FIG. 3 does not constitute a limitation on the means for storage management software task information collection and may include more or fewer components than those illustrated.
The device for collecting task information of storage management software provided by the embodiment of the application comprises a memory and a processor, wherein when the processor executes a program stored in the memory, the following method can be realized: a method for collecting task information of storage management software.
According to the device for collecting the task information of the storage management software, when the module executes the task and fails, the abnormal information of the current task module is collected, the abnormal information of the module directly and indirectly related to the current task module is also collected, the reason of the task failure is determined according to the accurately positioned and comprehensive abnormal information set, the intervention of developers is reduced, the reliability of the whole storage system is improved, and meanwhile, the user experience is improved.
Finally, the application also provides a corresponding embodiment of the computer readable storage medium. The computer-readable storage medium has stored thereon a computer program which, when being executed by a processor, carries out the steps as set forth in the above-mentioned method embodiments.
It is understood that, if the method in the above embodiments is implemented in the form of software functional units and sold or used as a stand-alone product, it can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application, which are essential or part of the prior art, or all or part of the technical solutions may be embodied in the form of a software product, which is stored in a storage medium and executes all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description details a method, an apparatus, and a medium for collecting task information of storage management software provided in the present application. The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It should also be noted that, in this specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.

Claims (10)

1. A method for collecting storage management software task information, comprising:
creating a module association table according to the historical log information so as to record association levels of different modules in the storage management software and dependency relationships among the different modules;
when a task failure signal is obtained, determining a direct association module and an indirect association module corresponding to the current task failure module according to the module association table;
calling a pre-constructed module information collector to collect the current task failure module, and obtaining an abnormal information set by the abnormal information of the direct correlation module and the indirect correlation module;
and determining the reason of the current task failure according to the abnormal information set.
2. The method for collecting task information of storage management software according to claim 1, wherein collecting exception information of the current task failure module, the directly associating module and the indirectly associating module to obtain an exception information set comprises:
collecting abnormal information of the current task failure module, the direct correlation module and the indirect correlation module in a time period from the start of the current task to the termination of the current task;
and storing the abnormal information collected by the previous task failure to obtain the abnormal information set.
3. The method of storage management software task information collection according to claim 2, wherein said determining a reason for a current task failure from the set of exception information comprises:
classifying the target abnormal information in a preset period to obtain a classification result;
respectively determining the frequency of abnormal information of the current task failure module, the direct association module and the indirect association module according to the classification result;
determining the current task failure module according to the frequency of the abnormal information corresponding to each module, and the current association levels corresponding to the direct association module and the indirect association module;
and determining the reason of the current task failure according to each current association grade.
4. The method for collecting task information of storage management software according to claim 3, wherein the determining the current task failure module according to the frequency of the abnormal information corresponding to each module includes:
when the frequency of the abnormal information is larger than a first threshold value, determining the current association grade as an important grade;
when the frequency of the abnormal information is greater than a second threshold value and less than or equal to the first threshold value, determining that the current association level is a medium level;
when the frequency of the abnormal information is not greater than the second threshold, the current association level is determined to be a general level.
5. The method for collecting task information of storage management software according to claim 3, wherein after determining the current task failure module according to the frequency of the abnormal information corresponding to each module, the current association level corresponding to the direct association module and the indirect association module, the method further comprises:
determining whether the current association levels corresponding to the direct association module and the indirect association module are the same as the association levels in the module association table or not by the current task failure module;
and if not, updating the module association table based on the current association level.
6. The method for task information collection of storage management software according to any one of claims 1 to 5, further comprising:
and when an autonomous modification instruction is acquired, modifying the module association table according to the autonomous modification instruction.
7. The method for task information collection of storage management software according to claim 1, wherein the creating a module association table according to the historical log information to record association levels of different modules and dependencies among different modules in the storage management software comprises:
classifying each abnormal information in the historical log information to determine the frequency of the abnormal information of different modules;
determining the association levels corresponding to different modules according to the frequency of the abnormal information corresponding to the modules;
and determining the association degree between different modules according to the historical log information so as to determine the dependency relationship between different modules.
8. An apparatus for storage management software task information collection, comprising:
the creating module is used for creating a module association table according to the historical log information so as to record the association levels of different modules and the dependency relationship among the different modules in the storage management software;
the first determining module is used for determining a direct association module and an indirect association module corresponding to the current task failure module according to the module association table when the task failure signal is acquired;
the calling module is used for calling a pre-constructed module information collector to collect the current task failure module, and the abnormal information of the direct correlation module and the indirect correlation module obtains an abnormal information set;
and the second determining module is used for determining the reason of the current task failure according to the abnormal information set.
9. An apparatus for storage management software task information collection, comprising a memory for storing a computer program;
a processor for implementing the steps of the method of storage management software task information collection according to any one of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, characterized in that a computer program is stored on the computer-readable storage medium, which computer program, when being executed by a processor, carries out the steps of the method of storage management software task information collection according to any one of claims 1 to 7.
CN202210890234.2A 2022-07-27 2022-07-27 Method, device and medium for collecting storage management software task information Pending CN115168095A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210890234.2A CN115168095A (en) 2022-07-27 2022-07-27 Method, device and medium for collecting storage management software task information

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210890234.2A CN115168095A (en) 2022-07-27 2022-07-27 Method, device and medium for collecting storage management software task information

Publications (1)

Publication Number Publication Date
CN115168095A true CN115168095A (en) 2022-10-11

Family

ID=83496316

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210890234.2A Pending CN115168095A (en) 2022-07-27 2022-07-27 Method, device and medium for collecting storage management software task information

Country Status (1)

Country Link
CN (1) CN115168095A (en)

Similar Documents

Publication Publication Date Title
US10878335B1 (en) Scalable text analysis using probabilistic data structures
CN108363657B (en) Method, equipment and medium for monitoring integrity of embedded data acquisition of APP client
US20240020215A1 (en) Analyzing large-scale data processing jobs
CN114153688A (en) Distributed monitoring method and device based on cloud platform
CN110018932B (en) Method and device for monitoring container magnetic disk
CN112767080A (en) Alarming method, device and medium based on stream type calculation
CN114647548A (en) Log generation method and device
CN112181853A (en) Program debugging method, device and system
CN112433888A (en) Data processing method and device, storage medium and electronic equipment
CN115168095A (en) Method, device and medium for collecting storage management software task information
CN113568769B (en) Exception handling method, device, server and storage medium
CN115203190A (en) Method, device and medium for deleting garbage object
CN115114070A (en) Fault diagnosis method, device, equipment and medium
CN114153601A (en) Resource scheduling method, device and medium under multi-cloud model
CN114328112A (en) Monitoring method, device, equipment and medium for heterogeneous chip
CN113672660A (en) Data query method, device and equipment
CN114138509B (en) Data interaction method and device and computer readable storage medium
CN117055718B (en) System, method, device, equipment and storage medium for detecting power consumption of server
CN111651323A (en) Application software monitoring method, device and equipment
CN114265555A (en) Method, device and medium for cleaning disk data
CN113869882A (en) Data processing method, device and medium
CN114168440A (en) Performance test method, device, equipment and medium for metadata acquisition
CN115687010A (en) Log early warning method and device
CN115329049A (en) System slow query analysis method, device and medium
CN115185757A (en) Storage pressure testing method, device, equipment and medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination