Storage system SDK docking method, device, equipment and storage medium
By traversing the interface classes in the preset configuration file and instantiating objects, it realizes docking with the performance monitoring system, and solves the docking problem caused by the differences in data acquisition methods of different monitoring systems, and improves the flexibility and efficiency of the change and promotion of monitoring system.
Patent Information
- Application Number
- CN202210327779.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-29
- Publication Date
- 2025-02-18
- Estimated Expiration
- 2042-03-29
AI Technical Summary
Different monitoring systems have different methods of data collection, which leads to the application layer needing to cooperate with transformation when the monitoring system logic is changed or replaced, which makes it difficult to promote changes and affects business development.
By obtaining the interface class of the performance monitoring system, traverse the preset interface class in the preset configuration file, match and obtain the corresponding preset implementation class information, instantiate the object and obtain the interface docking method, and realize docking with the performance monitoring system.
It realizes the flexibility and adaptability of data acquisition and docking of monitoring system, and can deal with logic changes or replacements of monitoring system without application layer transformation, reducing the interference of infrastructure changes to the application layer.
Smart Images

Figure CN114625347B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the technical field of cloud computing, and in particular to a storage system SDK docking method, device, equipment, storage medium and program product. Background Art
[0002] With the diversification of distributed systems and the complexity of service capabilities, full-link monitoring of business processing has become particularly important. However, different monitoring systems have different ways of collecting data. When the collection logic of the monitoring system changes or the monitoring system is replaced, the application layer needs to cooperate with the transformation, which makes it difficult to promote changes in the monitoring system. There is a long-term process of alternating between the old and the new, and it also makes it impossible for applications to focus on business development and is disturbed by changes in infrastructure. Summary of the invention
[0003] In view of the above problems, the present disclosure provides a storage system SDK docking method, device, equipment, storage medium and program product, aiming to solve the problem of difficulty in data collection docking.
[0004] According to a first aspect of the present disclosure, a storage system SDK docking method is provided, comprising:
[0005] Get the interface class of the performance monitoring system;
[0006] According to the interface class, traverse the preset interface class in the preset configuration file, and when the interface class matches the preset interface class, obtain the preset implementation class information of the corresponding preset interface class;
[0007] Instantiate the object according to the preset implementation class information, obtain the interface docking method, and dock with the performance monitoring system according to the interface docking method.
[0008] According to an embodiment of the present disclosure, according to the interface class, the step of traversing the preset interface class in the preset configuration file includes:
[0009] According to the interface class, obtain the corresponding thread class loader;
[0010] Through the thread class loader, traverse the preset interface classes in the preset configuration file.
[0011] According to an embodiment of the present disclosure, according to the interface class, the step of traversing the preset interface class in the preset configuration file further includes:
[0012] When the interface class cannot match the preset interface class, construct a new interface class and the corresponding new implementation class information corresponding to the interface class;
[0013] Cache new interface class and new implementation class information to the preset configuration file.
[0014] According to an embodiment of the present disclosure, a plurality of preset configuration files are provided;
[0015] According to the interface class, the step of traversing the preset interface class in the preset configuration file further includes:
[0016] When the interface class does not match the preset interface class, switch the preset configuration file;
[0017] The preset interface classes in the switched preset configuration file are traversed until the interface class matches the preset interface class, otherwise the preset configuration file continues to be switched.
[0018] According to an embodiment of the present disclosure, after the step of docking with the performance monitoring system, the following steps are further included:
[0019] Cache interface connection method.
[0020] According to an embodiment of the present disclosure, after the step of docking with the performance monitoring system, the following steps are further included:
[0021] Obtain data collection requirements for performance monitoring systems;
[0022] Access the storage system based on data collection requirements.
[0023] A second aspect of the present disclosure provides a storage system SDK docking device, including:
[0024] Transmission module, used to obtain the interface class of the performance monitoring system;
[0025] The configuration file module is used to traverse the preset interface class according to the interface class, and when the interface class matches the preset interface class, obtain the preset implementation class information of the corresponding preset interface class;
[0026] The service discovery module instantiates an object according to the preset implementation class information, obtains the interface docking method, and performs docking and collection with the performance monitoring system according to the interface docking method; and
[0027] The service provider interface module is used to connect with the performance monitoring system according to the interface connection method.
[0028] The third aspect of the present disclosure provides an electronic device, comprising one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above-mentioned storage system SDK docking method.
[0029] A third aspect of the present disclosure provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, causes the processor to execute the above-mentioned storage system SDK docking method.
[0030] A fourth aspect of the present disclosure provides a computer program product, including a computer program, where the computer program is executed by a processor to implement the storage system SDK docking method. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] The above contents and other objects, features and advantages of the present disclosure will become more apparent through the following description of the embodiments of the present disclosure with reference to the accompanying drawings, in which:
[0032] Figure 1 The application scenario diagram schematically shows the storage system SDK docking method, apparatus, device, medium and program product according to the embodiment of the present disclosure;
[0033] Figure 2 A flowchart schematically shows a method for docking a storage system SDK according to an embodiment of the present disclosure;
[0034] Figure 3 Schematically shows Figure 2 A flowchart of an embodiment of step S20;
[0035] Figure 4 Schematically shows Figure 2 Flow chart of the first embodiment of step S20;
[0036] Figure 5 Schematically shows Figure 2 Flow chart of the second embodiment of step S20;
[0037] Figure 6 A flowchart schematically shows a method for docking a storage system SDK according to another embodiment of the present disclosure;
[0038] Figure 7 Schematically shows Figure 2 A flowchart of an embodiment of step S40;
[0039] Figure 8 The structure block diagram of the docking device of the storage system SDK according to the embodiment of the present disclosure is schematically shown;
[0040] Fig. 9 A structural block diagram schematically shows a specific embodiment of a docking device for a storage system SDK;
[0041] Fig.10 A flowchart of a specific embodiment of a storage system SDK docking method is schematically shown.
[0042] Fig.11 A block diagram of an electronic device suitable for implementing a method for docking a storage system SDK according to an embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION
[0043] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present disclosure. In the following detailed description, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessary confusion of the concepts of the present disclosure.
[0044] The terms used herein are only for describing specific embodiments and are not intended to limit the present disclosure. The terms "comprise", "include", etc. used herein indicate the existence of features, steps, operations and / or components, but do not exclude the existence or addition of one or more other features, steps, operations or components.
[0045] All terms (including technical and scientific terms) used herein have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification, and should not be interpreted in an idealized or overly rigid manner.
[0046] When using expressions such as "at least one of A, B, and C, etc.", they should generally be interpreted according to the meaning of the expression commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).
[0047] In the technical solution disclosed in the present invention, the acquisition, storage and application of user personal information involved are in compliance with the provisions of relevant laws and regulations, necessary confidentiality measures are taken, and do not violate public order and good morals.
[0048] The present disclosure provides a storage system SDK docking method, including:
[0049] Get the interface class of the performance monitoring system;
[0050] According to the interface class, traverse the preset interface class in the preset configuration file, and when the interface class matches the preset interface class, obtain the preset implementation class information of the corresponding preset interface class;
[0051] Instantiate the object according to the preset implementation class information and obtain the interface docking method;
[0052] Connect to the performance monitoring system according to the interface connection method.
[0053] Figure 1The application scenario diagram of the storage system SDK docking method and device according to the embodiment of the present disclosure is schematically shown.
[0054] like Figure 1 As shown, the application scenarios according to this embodiment may include the financial services field. The network 102 is used to provide a medium for a communication link between the terminal device 101 and the server 103. The network 102 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.
[0055] The user can use the terminal device 101 to interact with the server 103 through the network 102 to receive or send messages, etc. Various communication client applications can be installed on the terminal device 101, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only as examples).
[0056] The terminal device 101 may be any electronic device having a display screen and supporting web browsing, including but not limited to a smart phone, a tablet computer, a laptop computer, a desktop computer, and the like.
[0057] The server 103 may be a server that provides various services, such as a background management server (only as an example) that provides support for websites browsed by users using the terminal device 101. The background management server may analyze and process received data such as user requests, and feed back processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal device.
[0058] It should be noted that the docking method of the storage system SDK provided in the embodiment of the present disclosure can generally be executed by the server 103. Accordingly, the information prompting device provided in the embodiment of the present disclosure can generally be set in the server 103. The docking method of the storage system SDK provided in the embodiment of the present disclosure can also be executed by a server or server cluster that is different from the server 103 and can communicate with the terminal device 101 and / or the server 103. Correspondingly, the information prompting device provided in the embodiment of the present disclosure can also be set in a server or server cluster that is different from the server 103 and can communicate with the terminal device 101 and / or the server 103.
[0059] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.
[0060] The following will be based on Figure 1 The scene described by Figures 2 to 8 The storage system SDK docking method of the disclosed embodiment is described in detail.
[0061] Figure 2 A flowchart of a storage system SDK docking method according to an embodiment of the present disclosure is schematically shown.
[0062] like Figure 2 As shown, the storage system SDK docking method of this embodiment includes steps S10 to S30, and the storage system SDK docking method can be executed by a storage system SDK docking device.
[0063] In operation S10, an interface class of a performance monitoring system is obtained;
[0064] In operation S20, according to the interface class, the preset interface class in the preset configuration file is traversed, and when the interface class matches the preset interface class, the preset implementation class information of the corresponding preset interface class is obtained;
[0065] In operation S30, an object is instantiated according to the preset implementation class information to obtain an interface docking method;
[0066] In operation S40, the interface is connected to the performance monitoring system according to the interface connection method.
[0067] In the technical solution provided by the present invention, the implementation class of the interface is defined in a preset configuration file. When docking with the monitoring system, the implementation class of the interface is obtained from the configuration file according to the interface class, and instantiated through class loading to form a service provider mechanism. That is, only one key (i.e., the interface class) needs to be input to obtain an instance of the corresponding class, thereby realizing the decoupling of the application layer and the performance data collection logic of the monitoring system. When the monitoring system undergoes logical changes or system replacement, there is no need for business applications to cooperate with program transformation, so as to have elegant expansion or change capabilities and reduce the interference of infrastructure changes to the application layer.
[0068] It should be noted that SDK (Software Development Kit) is generally a collection of development tools used by software engineers to build application software for specific software packages, software frameworks, hardware platforms, operating systems, etc. SDK refers to a collection of related documents, examples and tools that assist in the development of a certain type of software. In this embodiment, the application directly accesses the storage system through the SDK and sends the collected data to the monitoring system. In addition, instantiation refers to the process of creating objects with classes in object-oriented programming. It is the process of making an abstract concept class specific to the physical object of that class. In this disclosure, it is the specific interface docking method of obtaining the interface through the interface class.
[0069] It should be noted that, in this embodiment, the implementation class information of the interface class is obtained in the configuration file by Class.forName. Further, in order to facilitate the search and loading of the preset configuration file, the preset configuration file is loaded by loading the fully qualified name of the interface class.
[0070] For further information, see Figure 3 , step S20 comprises:
[0071] S21. Obtain the corresponding thread class loader according to the interface class;
[0072] S22. Traverse the preset interface classes in the preset configuration file through the thread class loader.
[0073] When docking with the monitoring system, the monitoring system provides many interfaces, allowing third parties to provide implementations for these interfaces. The implementation codes of these interfaces are included in the class path, and specific implementation classes need to be loaded. It cannot be delegated to the system class loader because it is the ancestor class loader of the system class loader. Therefore, in this embodiment, a thread class loader is set to successfully load the interface class.
[0074] Also, see Figure 4 In one embodiment provided in the present disclosure, step S20 further includes:
[0075] S201. When the interface class cannot match the preset interface class, construct a new interface class and corresponding new implementation class information corresponding to the interface class;
[0076] S202, caching new interface class and new implementation class information to a preset configuration file.
[0077] In order to adapt to more systems, in this embodiment, for interface classes that are not cached in the preset configuration file, when the preset configuration file cannot be matched, a new interface class and the corresponding implementation class information are constructed and cached in the preset configuration file, so that the data acquisition system can be connected to the monitoring system. There is no need to modify the application layer, which improves applicability and facilitates improvement for different systems.
[0078] In another embodiment provided by the present disclosure, please refer to Figure 5 ,There are multiple preset profile settings;
[0079] Step S20 also includes:
[0080] S203, when the interface class does not match the preset interface class, switching the preset configuration file;
[0081] S204: traverse the preset interface classes in the switched preset configuration file until the interface class matches the preset interface class, otherwise continue to switch the preset configuration file.
[0082] There are multiple preset configuration files, each of which contains different interface classes and implementation class information. For different systems, you can directly switch the preset configuration files to find the corresponding interface class and increase applicability.
[0083] In addition, it should be noted that in the embodiments provided in the present disclosure, the matching methods of the above two interface types may exist at the same time, so as to increase the applicability of the data acquisition system docking method.
[0084] Furthermore, a fully qualified name is set for the storage location of the configuration file, and different configuration files are loaded correspondingly by loading the fully qualified name of the interface, so that the required configuration file can be found among multiple configuration files without searching one by one, thus improving the processing speed.
[0085] To facilitate subsequent multiple connections with the performance monitoring system, please refer to Figure 6 , after step S40, further comprising:
[0086] S50: Cache interface connection method.
[0087] Since docking with the monitoring system often needs to last for a period of time, but the connection is often time-limited, in order to avoid each time with the monitoring system, the interface docking method is cached in the memory to facilitate the next docking without calling the configuration file again.
[0088] On the other hand, see Figure 7 , after step S40, further comprising:
[0089] S41. Obtaining data collection requirements of the performance monitoring system;
[0090] S42. Access the storage system according to data collection requirements.
[0091] After the connection with the performance monitoring system is completed, the data collection requirements to be collected are obtained from the performance monitoring system, and the storage system is accessed according to the data collection requirements to facilitate data transmission.
[0092] Based on the above storage system SDK docking method, the present disclosure also provides a storage system SDK docking device. Figure 8 The device is described in detail.
[0093] Figure 8 The structural block diagram of the storage system SDK according to the embodiment of the present disclosure is schematically shown.
[0094] like Figure 8 As shown, the docking device 200 of the storage system SDK of this embodiment includes a transmission module 1, a configuration file module 2, a service discovery module 3 and a service provider interface module 4; the transmission module 1 is used to obtain the interface class of the performance monitoring system; the configuration file module 2 is used to traverse the preset interface class according to the interface class, and when the interface class matches the preset interface class, obtain the preset implementation class information of the corresponding preset interface class; the service discovery module 3 instantiates the object according to the preset implementation class information, obtains the interface docking method, and performs docking and collection with the performance monitoring system according to the interface docking method; the service provider interface module 4 is used to dock with the performance monitoring system according to the interface docking method.
[0095] It should be noted that the storage system SDK docking device 200 also includes a service module and a performance collection module; the service module is used to obtain data collection requirements of the performance monitoring system; the performance collection module is used to access the storage system according to the data collection requirements.
[0096] See also Fig. 9 , which is a specific embodiment provided by the present disclosure. In this embodiment, the storage system SDK includes a service provider interface, ServiceDiscover (service discovery) and a performance collection module. The storage system SDK is used to access remote storage media; the service provider interface is an interface or an abstract class, which defines the functions that need to be extended and implemented; ServiceDiscover is used to load and instantiate the Java class of the service, and provides an interface for obtaining the service object; wherein LazyIterator is a private inner class of ServiceDiscover, which is responsible for loading, instantiating and caching all service classes. The storage system SDK obtains the specific service provider iterator through the interface exposed by ServiceDiscover, and traverses and calls ServiceDiscover; a configuration file is set in the performance collection module, and the configuration file is configured with relevant information of the service provider, including the fully qualified name of the implementation class.
[0097] Based on the above specific embodiments, the present disclosure also provides a specific storage system SDK docking method.
[0098] See also Fig.10 ,In this embodiment, the storage system SDK remotely accesses the storage medium and is connected to the monitoring system;
[0099] 1. The storage system SDK obtains the parameter API.class, which is the interface class for connecting to the monitoring system;
[0100] 2. According to the current interface class, the storage system SDK obtains the corresponding thread class loader to load the interface class;
[0101] 3. Construct ServiceDiscover to construct the implementation class information of the corresponding interface class in service discovery;
[0102] 4. Construct LazyIterator, which is responsible for loading, instantiating and caching the ServiceDiscover class.
[0103] 5. A configuration file is set in the performance collection module, and the configuration file corresponding to the fully qualified API name under the class path is loaded.
[0104] 6. Use the method Class.forName() to obtain the implementation class information of the interface;
[0105] 7. Instantiate the implementation class of the interface and cache it.
[0106] According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits, or at least part of the functions of any one of them can be implemented in one module. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be split into multiple modules for implementation. According to the embodiments of the present invention, any one or more of the modules, submodules, units, and subunits can be at least partially implemented as hardware circuits, such as field programmable gate arrays (FPGAs), programmable logic arrays (PLAs), systems on chips, systems on substrates, systems on packages, application specific integrated circuits (ASICs), or can be implemented by hardware or firmware in any other reasonable way of integrating or packaging the circuit, or implemented in any one of the three implementation methods of software, hardware, and firmware, or in any appropriate combination of any of them. Alternatively, according to the embodiments of the present invention, one or more of the modules, submodules, units, and subunits can be at least partially implemented as computer program modules, and when the computer program modules are run, the corresponding functions can be performed.
[0107] Fig.11 A block diagram of an electronic device suitable for a docking method of a storage system SDK according to an embodiment of the present disclosure is schematically shown.
[0108] like Fig.11As shown, the electronic device 300 according to the embodiment of the present disclosure includes a processor 3001, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 3002 or the program loaded from the storage part 3008 to the random access memory (RAM) 3003. The processor 3001 may include, for example, a general-purpose microprocessor (such as a CPU), an instruction set processor and / or a related chipset and / or a special-purpose microprocessor (for example, an application-specific integrated circuit (ASIC)), etc. The processor 3001 may also include an onboard memory for caching purposes. The processor 3001 may include a single processing unit or multiple processing units for performing different actions of the method flow according to the embodiment of the present disclosure.
[0109] In RAM 3003, various programs and data required for the operation of electronic device 300 are stored. Processor 3001, ROM 3002 and RAM 3003 are connected to each other via bus 3004. Processor 3001 performs various operations of the method flow according to the embodiment of the present disclosure by executing the program in ROM 3002 and / or RAM 3003. It should be noted that the program can also be stored in one or more memories other than ROM 3002 and RAM 3003. Processor 3001 can also perform various operations of the method flow according to the embodiment of the present disclosure by executing the program stored in one or more memories.
[0110] According to an embodiment of the present disclosure, the electronic device 300 may further include an input / output (I / O) interface 3005, which is also connected to the bus 3004. The electronic device 300 may further include one or more of the following components connected to the I / O interface 3005: an input portion 3006 including a keyboard, a mouse, etc.; an output portion 3007 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage portion 3008 including a hard disk, etc.; and a communication portion 3009 including a network interface card such as a LAN card, a modem, etc. The communication portion 3009 performs communication processing via a network such as the Internet. A drive 3010 is also connected to the I / O interface 3005 as needed. A removable medium 3011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 3010 as needed, so that a computer program read therefrom is installed into the storage portion 3008 as needed.
[0111] The present disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or may exist independently without being assembled into the device / apparatus / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present disclosure is implemented.
[0112] According to an embodiment of the present disclosure, a computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, may include but is not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, an apparatus or a device. For example, according to an embodiment of the present disclosure, a computer-readable storage medium may include the ROM 3002 and / or RAM 3003 described above and / or one or more memories other than ROM 3002 and RAM 3003.
[0113] The embodiment of the present disclosure also includes a computer program product, which includes a computer program, and the computer program includes a program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the storage system SDK docking method provided by the embodiment of the present disclosure.
[0114] The above functions defined in the system / device of the embodiment of the present disclosure are performed when the computer program is executed by the processor 3001. According to the embodiment of the present disclosure, the system, device, module, unit, etc. described above can be implemented by a computer program module.
[0115] In one embodiment, the computer program may rely on tangible storage media such as optical storage devices, magnetic storage devices, etc. In another embodiment, the computer program may also be transmitted and distributed in the form of signals on a network medium, and downloaded and installed through the communication part 3009, and / or installed from the removable medium 3011. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.
[0116] In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 3009, and / or installed from the removable medium 3011. When the computer program is executed by the processor 3001, the above functions defined in the system of the embodiment of the present disclosure are performed. According to the embodiment of the present disclosure, the system, equipment, means, module, unit, etc. described above can be implemented by a computer program module.
[0117] According to an embodiment of the present disclosure, the program code for executing the computer program provided by the embodiment of the present disclosure can be written in any combination of one or more programming languages. Specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include, but are not limited to, Java, C++, python, "C" language or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on the remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect through the Internet).
[0118] The flow charts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0119] It will be appreciated by those skilled in the art that the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in the present disclosure. In particular, the features described in the various embodiments and / or claims of the present disclosure may be combined and / or combined in a variety of ways without departing from the spirit and teachings of the present disclosure. All of these combinations and / or combinations fall within the scope of the present disclosure.
[0120] The embodiments of the present disclosure are described above. However, these embodiments are only for illustrative purposes and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the various embodiments cannot be used in combination to advantage. The scope of the present disclosure is defined by the attached claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art may make a variety of substitutions and modifications, which should all fall within the scope of the present disclosure.
[0121] The specific embodiments described above further illustrate the purpose, technical solutions and beneficial effects of the present disclosure. It should be understood that the above description is only a specific embodiment of the present disclosure and is not intended to limit the present disclosure. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present disclosure should be included in the protection scope of the present disclosure.
Claims
1. A storage system SDK docking method, characterized in that: include: Get the interface class of the performance monitoring system; According to the interface class, traverse the preset interface classes in the preset configuration file, and when the interface class matches the preset interface class, obtain the preset implementation class information corresponding to the preset interface class; The step of traversing the preset interface classes in the preset configuration file according to the interface class also includes: When the interface class cannot match the preset interface class, construct a new interface class and corresponding new implementation class information corresponding to the interface class; Cache the new interface class and the new implementation class information to the preset configuration file; The preset configuration files are provided in plurality; The step of traversing the preset interface classes in the preset configuration file according to the interface class also includes: When the interface class cannot match the preset interface class, switching the preset configuration file; Traversing the preset interface classes in the switched preset configuration file until the interface class matches the preset interface class, otherwise continuing to switch the preset configuration file; Instantiate an object according to the preset implementation class information and obtain an interface docking method; According to the interface docking method, docking is performed with the performance monitoring system.
2. The storage system SDK docking method according to claim 1, characterized in that: According to the interface class, the step of traversing the preset interface class in the preset configuration file includes: According to the interface class, obtain the corresponding thread class loader; The preset interface classes in the preset configuration file are traversed through the thread class loader.
3. The storage system SDK docking method according to claim 1, characterized in that: After the step of docking with the performance monitoring system, the method further includes: The interface connection method is cached.
4. The storage system SDK docking method according to claim 1, characterized in that: After the step of docking with the performance monitoring system, the method further includes: Obtaining data collection requirements of the performance monitoring system; According to the data collection requirements, a storage system is accessed.
5. A storage system SDK docking device, characterized in that: include: Transmission module, used to obtain the interface class of the performance monitoring system; A configuration file module, used for traversing preset interface classes according to the interface class, and obtaining preset implementation class information corresponding to the preset interface class when the interface class matches the preset interface class; The step of traversing the preset interface classes in the preset configuration file according to the interface class also includes: When the interface class cannot match the preset interface class, construct a new interface class and corresponding new implementation class information corresponding to the interface class; Cache the new interface class and the new implementation class information to the preset configuration file; The preset configuration files are provided in plurality; The step of traversing the preset interface classes in the preset configuration file according to the interface class also includes: When the interface class cannot match the preset interface class, switching the preset configuration file; Traversing the preset interface classes in the switched preset configuration file until the interface class matches the preset interface class, otherwise continuing to switch the preset configuration file; A service discovery module, used to instantiate an object according to the preset implementation class information, obtain an interface docking method, and perform docking and collection with the performance monitoring system according to the interface docking method; and The service provider interface module is used to interface with the performance monitoring system according to the interface interface method.
6. An electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are caused to execute the method according to any one of claims 1 to 4.
7. A computer-readable storage medium, characterized in that: Executable instructions are stored thereon, and when the instructions are executed by a processor, the processor is caused to perform the method according to any one of claims 1 to 4.
8. A computer program product, characterized in that The invention comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 4.
Citation Information
Patent Citations
Plug-in scheduling process monitoring method implemented based on dynamic proxy
CN103927244A
Method for efficiently docking software with various mounting devices in intelligent lamp post system
CN113296747A