CN113849373A - Server supervision method and device and storage medium - Google Patents
Server supervision method and device and storage medium Download PDFInfo
- Publication number
- CN113849373A CN113849373A CN202111135522.9A CN202111135522A CN113849373A CN 113849373 A CN113849373 A CN 113849373A CN 202111135522 A CN202111135522 A CN 202111135522A CN 113849373 A CN113849373 A CN 113849373A
- Authority
- CN
- China
- Prior art keywords
- key name
- server
- private key
- supervised
- name
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 43
- 241001290266 Sciaenops ocellatus Species 0.000 claims abstract description 51
- 230000001105 regulatory effect Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 7
- 238000012544 monitoring process Methods 0.000 description 6
- 238000011161 development Methods 0.000 description 3
- 230000036541 health Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000003058 natural language processing Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 230000003044 adaptive effect Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
- G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Computing Systems (AREA)
- Quality & Reliability (AREA)
- Computer And Data Communications (AREA)
Abstract
The present disclosure provides a server supervision method, apparatus and storage medium, wherein the method comprises: setting a private key name corresponding to a redfish resource of a server; setting a standard key name corresponding to a supervision item of the server; establishing a corresponding relation between the private key name and the standard key name; and obtaining the matching relation between the private key name and the standard key name of the supervision item of the server to be supervised based on the corresponding relation, so as to obtain the access information of the supervision item of the server to be supervised and supervise the access information. The method, the device and the storage medium can solve the problem that the redfish protocols of different brands and different models of servers are different, can eliminate the delay time of bringing a new model of server into supervision in actual use, can eliminate the system instability risk caused by modifying a source code, greatly improve the use efficiency and avoid the dependence on developers.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a server monitoring method, an apparatus, and a storage medium.
Background
The out-of-band supervision of the server is of great significance to machine room management, particularly large data center machine rooms. The Redfish protocol is simple to use and comprehensive in function, all server manufacturers basically provide support for Redfish, and application of a Redfish supervision server becomes the mainstream trend of the current industry. However, the redfish protocol does not specify the URI and json key name in detail, and the implementations of manufacturers differ, and servers of different models of the same manufacturer differ. At present, a solution to the problem of implementing different redfish protocols by a supervisory system developer for various manufacturers is to provide different modules for servers of different manufacturers and different models on a source code level, and when a new-model server needs to be brought into supervision, the developer modifies a source code and adds an adaptive module. Therefore, when a new-model server needs to be supervised, the existing supervision system needs certain development and test time and has long delay.
Disclosure of Invention
In view of the above, an object of the present invention is to provide a server monitoring method, apparatus and storage medium.
According to a first aspect of the present disclosure, there is provided a server supervision method, including: setting a private key name corresponding to a redfish resource of a server; setting a standard key name corresponding to a supervision item of the server; establishing a corresponding relation between the private key name and the standard key name; and obtaining the matching relation between the private key name and the standard key name of the supervision item of the server to be supervised based on the corresponding relation so as to obtain the access information of the supervision item of the server to be supervised and supervise the access information.
Optionally, the setting a private key name corresponding to a redfish resource of the server includes: constructing a resource tree corresponding to the redfish resource; wherein the URI and json key name of each node in the resource tree are unique; if the json key name is not unique in the resource tree, generating a new key name of the json key name based on a preset renaming rule so as to enable the new key name to be unique in the resource tree; setting the json key name or the new key name unique in the resource tree as the private key name.
Optionally, the renaming rule includes: and combining the json key name with the name of the node where the json key name is located, and combining the json key name with the name of the node on the json key name.
Optionally, the setting a standard key name corresponding to a supervision item of the server includes: and setting the corresponding standard key name for each supervision item of the server based on the private key name.
Optionally, the obtaining, based on the correspondence, a matching relationship between the private key name of the supervision item of the server to be supervised and the standard key name includes: when the server to be supervised is brought into supervision, acquiring all private key names of the server to be supervised; and establishing a matching relation between each private key name of the server to be supervised and the standard key name.
Optionally, a corresponding relationship between each private key name of the server to be supervised and the standard key name is established based on the matching relationship.
Optionally, if the private key name of the server to be supervised is not unique in the resource tree corresponding to the redfish resource of the server to be supervised, generating a new key name corresponding to the private key name of the server to be supervised based on the renaming rule.
According to a second aspect of the present disclosure, there is provided a server supervision apparatus, comprising: the private key name setting module is used for setting a private key name corresponding to the redfish resource of the server; the standard key name setting module is used for setting a standard key name corresponding to the supervision item of the server; the corresponding relation establishing module is used for establishing the corresponding relation between the private key name and the standard key name; and the access information acquisition module is used for acquiring the matching relation between the private key name and the standard key name of the supervision item of the server to be supervised based on the corresponding relation, and is used for acquiring the access information of the supervision item of the server to be supervised and supervising the access information.
Optionally, the private key name setting module is configured to construct a resource tree corresponding to the redfish resource; wherein the URI and json key name of each node in the resource tree are unique; if the json key name is not unique in the resource tree, generating a new key name of the json key name based on a preset renaming rule so as to enable the new key name to be unique in the resource tree; setting the json key name or the new key name unique in the resource tree as the private key name.
Optionally, the renaming rule includes: and combining the json key name with the name of the node where the json key name is located, and combining the json key name with the name of the node on the json key name.
Optionally, the standard key name setting module is configured to set the corresponding standard key name for each supervision item of the server based on the private key name.
Optionally, the access information obtaining module is configured to obtain all private key names of the servers to be supervised when the servers to be supervised are under supervision; and establishing a matching relation between each private key name of the server to be supervised and the standard key name.
Optionally, the access information obtaining module is further configured to establish a corresponding relationship between each private key name of the server to be supervised and the standard key name based on the matching relationship.
Optionally, the access information obtaining module is further configured to generate a new key name corresponding to the private key name of the server to be supervised based on the renaming rule if the private key name of the server to be supervised is not unique in the resource tree corresponding to the redfish resource of the server to be supervised.
According to a third aspect of the present disclosure, there is provided a server supervision apparatus comprising: a memory; and a processor coupled to the memory, the processor configured to perform the method of any of the above based on instructions stored in the memory.
According to a fourth aspect of the present disclosure, there is provided a computer readable storage medium storing computer instructions for execution by a processor to perform the method as described above.
According to the server supervision method, device and storage medium, the problem that the redfish protocols of servers of different brands and different models are different can be solved through different redfish resources of the intelligent adaptation server, source codes do not need to be modified, delay time for bringing a new model server into supervision can be eliminated in actual use, system instability risks caused by modifying the source codes can be eliminated, the use efficiency is greatly improved, meanwhile, dependence on developers is avoided, and the use experience of users is improved.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and other drawings can be obtained by those skilled in the art without inventive exercise.
FIG. 1 is a schematic diagram of a tree structure of redfish;
FIG. 2 is a schematic flow chart diagram illustrating one embodiment of a server policing method according to the present disclosure;
FIG. 3 is a schematic flow chart diagram illustrating the construction of private key names in one embodiment of a server policing method according to the present disclosure;
FIG. 4 is a schematic flow chart diagram illustrating matching of standard key names and private key names in one embodiment of a server policing method according to the present disclosure;
FIG. 5 is a block diagram illustration of one embodiment of a server administration apparatus according to the present disclosure;
fig. 6 is a block diagram of another embodiment of a server administration apparatus according to the present disclosure.
Detailed Description
The present disclosure now will be described more fully hereinafter with reference to the accompanying drawings, in which exemplary embodiments of the disclosure are shown. The technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments disclosed herein without making any creative effort, shall fall within the protection scope of the present disclosure.
Redfish is a management standard based on HTTPs service, and equipment management is realized by utilizing a RESTful interface. Each http operation submits or returns a resource or result in UTF-8 encoded JSON format, as a Web application returns HTML to a browser. The technology has the advantages of reducing development complexity, being easy to implement and use, providing expandability and reserving space for design flexibility.
In redfish, each URL represents a resource, a service or a group of resources. According to the REST principle, a Uniform Resource Identifier (URI) is used to point to a resource, and a client interacts with the resource. The format of the resource is defined according to a redfish architecture, and the client determines correct semantics according to the redfish architecture. In redfish, all resources are linked from the service entry point (root).
Redfish is based on a RESTful interface, data is regarded as resources, and each resource is given a unique identification URI. URIs are similar to multi-level paths, for example: "/redfish/v 1/Dell/Chassis/System. Embedded.1/Power Supplies/DellPowerSupply/PSU. Slot.1". All resources constitute a tree structure as shown in fig. 1.
The redfish resources are organized and represented by json-formatted data. There are the following resources (parts) under the above path: "Id": PSU.Slot.1"," IsSwitchingsupply ": true; wherein "Id" and "isswitchingpupply" are called key names, and "psu. The supervision system accesses the key value through the URI of the REST and the key name of the json to realize the supervision of the server. However, the redfish protocol does not specify the URI and json key name in detail, and the implementations of manufacturers differ, and servers of different models of the same manufacturer differ.
At present, the different solutions implemented by the monitoring system developer to the redfish protocol of each manufacturer are: different modules are provided for servers of different manufacturers and different models on the source code level, and developers modify source codes and add adaptive modules whenever new-model servers need to be brought into supervision. A certain development and test time is needed, the system is suitable for a new server and has a long delay, and even if the modified system passes the test, unstable factors caused by source code modification cannot be avoided; moreover, the whole life cycle of the system depends on developers seriously, and great uncertainty exists.
Fig. 2 is a schematic flow chart diagram of an embodiment of a server supervision method according to the present disclosure, as shown in fig. 2:
And 204, acquiring a matching relation between the private key name and the standard key name of the supervision item of the server to be supervised based on the corresponding relation, so as to acquire access information of the supervision item of the server to be supervised and supervise the access information.
The server supervision method can enable the supervision system to be intelligently adapted to the redfish protocols of servers of different brands and different models, and can be suitable for new servers without modifying source codes.
In one embodiment, setting the private key name corresponding to the redfish resource of the server may employ a variety of methods. For example, a resource tree corresponding to the redfish resource is constructed; wherein the URI and json key name of each node in the resource tree are unique.
And if the json key name is not unique in the resource tree, generating a new key name of the json key name based on the renaming rule so that the new key name is unique in the resource tree, and setting the unique json key name or the new key name in the resource tree as the private key name. The renaming rules include: combining the json key name with the name of the node where the json key name is located, combining the json key name with the name of the node on the json key name, and the like; the upper nodes comprise father nodes, grandfather nodes and the like.
As shown in fig. 1, all resources of redfish form a tree, and according to the REST rule, the URI of each node in the tree is unique. The json key name is also unique in each node. In practice, most json key names are unique not only in the node, but also in all nodes of the full tree.
For a few key names which are not unique in the whole tree, a new key name can be formed by selecting the combination of the json key name and the name of the node where the key is located, and if the key names are still not unique, the name combination of the father node and the grandfather node is continuously used until the names are unique.
Since the URI is unique to each node, it is always possible to find such combinations that the new key name is unique throughout the tree, most extremely up to the root node. In practical application, 2 nodes are generally selected to form a unique key name of the whole tree. For example, under the URI "/redfish/v1/Dell/Systems/system. "Health": OK "; the json key name "Health" is unique in this node, but not unique in the full tree. The node names "dimm. socket.a1" and "Health" where the key is located can be combined to form a new key name "dimm. socket.a 1-Health" which is unique in the full tree.
The construction of the new key name can be constructed according to the following principles: 1. if the json key name is already unique, then the json key name is used; 2. if the json key name is not unique, then the smallest combinations are used to construct a new key name that is unique to the full tree. The new key name composed in each server redfish and the json key name which is unique in the whole tree originally are uniformly defined as private key names. Since each server manufacturer pays attention to easy access to natural language and vocabulary in defining json key name and allocating resource URI, so as to be convenient for understanding and memorizing, the private key names constructed according to the above principle are similar to each other although the key names of each manufacturer are different.
Fig. 3 is a schematic flowchart of a process of constructing a private key name in an embodiment of a server supervision method according to the present disclosure, as shown in fig. 3:
in step 301 all json key names of the server redfish are read.
And step 304, combining the node name with the node name to form a new key name.
And 305, judging whether the new key name conflicts with other key names, if so, entering step 306, and if not, entering step 308.
And 308, judging whether all the keys are processed completely, if so, ending, and if not, entering the step 302.
In one embodiment, setting the standard key name corresponding to the administrative item of the server may take a variety of approaches. And setting corresponding standard key names for all the supervision items of the server based on the private key names. For example, with reference to the known private key names of multiple servers, a standard key name is defined for each supervisory item that is closer to the private key name.
Establishing a corresponding relation between a standard key name and a private key name, and maintaining a relation table by a system, wherein the table shows the corresponding relation among a supervision item, a server model (the model comprises manufacturer brand information), the standard key name, the private key name and a URI (Uniform resource identifier), and the following table 1 shows that:
TABLE 1-correspondence Table of Standard and private Key names
In one embodiment, the administrative items and standard key names are stored in advance in table 1 above. When a server to be supervised is brought into supervision, acquiring all private key names of the server to be supervised; and establishing a matching relation between each private key name and the standard key name of the server to be supervised. And if the private key name of the server to be supervised is not unique in the resource tree corresponding to the redfish resource of the server to be supervised, generating a new key name corresponding to the private key name of the server to be supervised based on the renaming rule. And establishing a corresponding relation between each private key name and the standard key name of the server to be supervised based on the matching relation.
When a new-model server (a server to be supervised) is to be brought into supervision, enumerating all private key names of the server, and establishing matching of the standard key names and the private key names by using the existing word embedding vector method of multiple NLPs (natural language processing). Due to the characteristics of redfish and the method of forming the private key names, the private key names of the supervision items of the factory server, and the private key names and the standard key names are similar to each other although they may be different, so that automatic matching can be realized in most cases. If there are few private key names that cannot be matched, the matching can be done manually.
For example, the supervision term "power" and DELL server DELL R7425, huaji server huabei 2288H V5 are illustrated. The standard key defined in advance for the supervision item "power" is named "PowerSupply". The system stores "power supply" and "PowerSupply" in advance in a table.
When server DELL R7425 newly incorporates supervision, the system enumerates all its redfish private key names. If the json inherent key name is unique in the whole tree, the inherent key name is used as the private key name, and if not, the combined key name is constructed as the private key name according to the renaming rule.
The system uses the existing NLP method to find the private key name 'DellPowerSuplyView' which is closest to the standard key name 'PowerSuplyView' in all the private key names, and the two can be matched. The system fills the table with "DellPowerSuplyView" and its URI "redfish/v 1/Dell/Chassis/System. Embedded.1/Power/PowerSupplies". Based on the same processing method, when the hua-server huabei 2288H V5 newly incorporates supervision, the system can fill corresponding contents into the table. When the system monitors the 'power supply', the access method of each server monitoring item can be obtained through table lookup, and the monitoring value is read and written to realize monitoring.
Fig. 4 is a schematic flow chart of matching a standard key name and a private key name in an embodiment of a server supervision method according to the present disclosure, as shown in fig. 4:
in step 401, the system reads in all json key names of the server.
At step 402, the system composes a private key name.
In step 403, the system matches the standard key name and the private key name.
In one embodiment, as shown in fig. 5, the present disclosure provides a server supervising apparatus 50 including a private key name setting module 51, a standard key name setting module 52, a correspondence relationship establishing module 53, and an access information acquiring module 54. The private key name setting module 51 sets a private key name corresponding to a redfish resource of the server. The standard key name setting module 52 sets a standard key name corresponding to the supervision item of the server.
The correspondence relationship establishing module 53 establishes a correspondence relationship between the private key name and the standard key name. The access information obtaining module 54 obtains the matching relationship between the private key name and the standard key name of the supervision item of the server to be supervised based on the corresponding relationship, so as to obtain the access information of the supervision item of the server to be supervised and supervise the access information.
In one embodiment, the private key name setting module 51 constructs a resource tree corresponding to the redfish resource; wherein the URI and json key name of each node in the resource tree are unique. If the json key name is not unique in the resource tree, the private key name setting module 51 generates a new key name of the json key name based on a preset renaming rule so that the new key name is unique in the resource tree. The private key name setting module 51 sets a json key name or a new key name unique in the resource tree as a private key name. The renaming rule includes combining the json key name with the name of the node where the json key name is located, combining the json key name with the name of the node on the top of the json key name, and the like.
The standard key name setting module 52 sets corresponding standard key names for the respective supervision items of the server based on the private key names. The access information obtaining module 54 obtains all the private key names of the servers to be supervised when the servers to be supervised are brought into supervision; the access information obtaining module 54 establishes a matching relationship between each private key name and a standard key name of the server to be supervised.
If the private key name of the server to be supervised is not unique in the resource tree corresponding to the redfish resource of the server to be supervised, the access information acquisition module 54 generates a new key name corresponding to the private key name of the server to be supervised based on the renaming rule. The access information obtaining module 54 establishes a corresponding relationship between each private key name of the server to be supervised and the standard key name based on the matching relationship.
In one embodiment, the present disclosure provides a server administration apparatus, as shown in fig. 6, which may include a memory 61, a processor 62, a communication interface 63, and a bus 64. The memory 61 is used for storing instructions, the processor 62 is coupled to the memory 61, and the processor 62 is configured to execute the server supervision method implemented above based on the instructions stored in the memory 61.
The memory 61 may be a high-speed RAM memory, a non-volatile memory (non-volatile memory), or the like, and the memory 61 may be a memory array. The storage 61 may also be partitioned and the blocks may be combined into virtual volumes according to certain rules. The processor 62 may be a central processing unit CPU, or an application Specific Integrated circuit asic, or one or more Integrated circuits configured to implement the server policing method of the present disclosure.
In one embodiment, the present disclosure provides a computer-readable storage medium storing computer instructions that, when executed by a processor, implement a method as in any one of the above embodiments.
According to the server supervision method, the server supervision device and the storage medium in the embodiment, the problem that the redfish protocols of servers of different brands and different models are different can be solved through intelligently adapting different redfish resources of the servers, source codes do not need to be modified, delay time for bringing a new model server into supervision can be eliminated in actual use, system instability risk caused by modifying the source codes can be eliminated, the use efficiency is greatly improved, meanwhile, dependence on developers is avoided, and the use experience of users is improved.
The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
The description of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to practitioners skilled in this art. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.
Claims (16)
1. A server policing method, comprising:
setting a private key name corresponding to a redfish resource of a server;
setting a standard key name corresponding to a supervision item of the server;
establishing a corresponding relation between the private key name and the standard key name;
and obtaining the matching relation between the private key name and the standard key name of the supervision item of the server to be supervised based on the corresponding relation so as to obtain the access information of the supervision item of the server to be supervised and supervise the access information.
2. The method of claim 1, the setting the private key name corresponding to the redfish resource of the server comprising:
constructing a resource tree corresponding to the redfish resource; wherein the URI and json key name of each node in the resource tree are unique;
if the json key name is not unique in the resource tree, generating a new key name of the json key name based on a preset renaming rule so as to enable the new key name to be unique in the resource tree;
setting the json key name or the new key name unique in the resource tree as the private key name.
3. The method of claim 2, wherein,
the renaming rule comprises: and combining the json key name with the name of the node where the json key name is located, and combining the json key name with the name of the node on the json key name.
4. The method of claim 2, the setting a standard key name corresponding to a regulatory term of a server comprising:
and setting the corresponding standard key name for each supervision item of the server based on the private key name.
5. The method of claim 2, wherein the obtaining a matching relationship between the private key name and the standard key name of the administrative item of the server to be supervised based on the correspondence comprises:
when the server to be supervised is brought into supervision, acquiring all private key names of the server to be supervised;
and establishing a matching relation between each private key name of the server to be supervised and the standard key name.
6. The method of claim 5, further comprising:
and establishing a corresponding relation between each private key name of the server to be supervised and the standard key name based on the matching relation.
7. The method of claim 5, further comprising:
and if the private key name of the server to be supervised is not unique in the resource tree corresponding to the redfish resource of the server to be supervised, generating a new key name corresponding to the private key name of the server to be supervised based on the renaming rule.
8. A server supervision apparatus comprising:
the private key name setting module is used for setting a private key name corresponding to the redfish resource of the server;
the standard key name setting module is used for setting a standard key name corresponding to the supervision item of the server;
the corresponding relation establishing module is used for establishing the corresponding relation between the private key name and the standard key name;
and the access information acquisition module is used for acquiring the matching relation between the private key name and the standard key name of the supervision item of the server to be supervised based on the corresponding relation, and is used for acquiring the access information of the supervision item of the server to be supervised and supervising the access information.
9. The apparatus of claim 8, wherein,
the private key name setting module is used for constructing a resource tree corresponding to the redfish resource; wherein the URI and json key name of each node in the resource tree are unique; if the json key name is not unique in the resource tree, generating a new key name of the json key name based on a preset renaming rule so as to enable the new key name to be unique in the resource tree; setting the json key name or the new key name unique in the resource tree as the private key name.
10. The apparatus of claim 9, wherein,
the renaming rule comprises: and combining the json key name with the name of the node where the json key name is located, and combining the json key name with the name of the node on the json key name.
11. The apparatus of claim 9, wherein,
and the standard key name setting module is used for setting the corresponding standard key name for each supervision item of the server based on the private key name.
12. The apparatus of claim 9, wherein,
the access information acquisition module is used for acquiring all private key names of the server to be supervised when the server to be supervised is brought into supervision; and establishing a matching relation between each private key name of the server to be supervised and the standard key name.
13. The apparatus of claim 12, wherein,
the access information acquisition module is further configured to establish a corresponding relationship between each private key name of the server to be supervised and the standard key name based on the matching relationship.
14. The apparatus of claim 12, wherein,
the access information obtaining module is further configured to generate a new key name corresponding to the private key name of the server to be supervised based on the renaming rule if the private key name of the server to be supervised is not unique in the resource tree corresponding to the redfish resource of the server to be supervised.
15. A server supervision apparatus comprising:
a memory; and a processor coupled to the memory, the processor configured to perform the method of any of claims 1-7 based on instructions stored in the memory.
16. A computer-readable storage medium having stored thereon computer instructions for execution by a processor of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111135522.9A CN113849373A (en) | 2021-09-27 | 2021-09-27 | Server supervision method and device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111135522.9A CN113849373A (en) | 2021-09-27 | 2021-09-27 | Server supervision method and device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113849373A true CN113849373A (en) | 2021-12-28 |
Family
ID=78979969
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111135522.9A Pending CN113849373A (en) | 2021-09-27 | 2021-09-27 | Server supervision method and device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113849373A (en) |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150089061A1 (en) * | 2012-12-24 | 2015-03-26 | Telefonaktiebolaget L M Ericsson (Publ) | Enabling external access to multiple services on a local server |
| CN105141672A (en) * | 2015-08-03 | 2015-12-09 | 广州神马移动信息科技有限公司 | Method, device and system for data storage |
| CN107547671A (en) * | 2016-06-29 | 2018-01-05 | 中兴通讯股份有限公司 | A kind of URL matching process and device |
| CN109245928A (en) * | 2018-09-12 | 2019-01-18 | 广州视源电子科技股份有限公司 | Configuration information setting method and device and terminal management system |
| CN110555041A (en) * | 2018-03-30 | 2019-12-10 | 腾讯科技（深圳）有限公司 | Data processing method, data processing device, computer equipment and storage medium |
| CN110781356A (en) * | 2019-09-25 | 2020-02-11 | 苏州浪潮智能科技有限公司 | Hardware query method, equipment and storage medium based on management platform |
| CN110995806A (en) * | 2019-11-24 | 2020-04-10 | 济南浪潮数据技术有限公司 | Resource state conversion method, device, equipment and storage medium |
| CN111147312A (en) * | 2019-12-31 | 2020-05-12 | 深圳云天励飞技术有限公司 | Resource allocation management method and device, resource allocation cache management method and device, and allocation management system |
| CN111212154A (en) * | 2019-12-31 | 2020-05-29 | 瑞庭网络技术（上海）有限公司 | Service binding method, device, terminal, server and storage medium |
| CN111447109A (en) * | 2020-03-23 | 2020-07-24 | 京东方科技集团股份有限公司 | Monitoring management apparatus and method, computer readable storage medium |
| CN112199197A (en) * | 2020-10-23 | 2021-01-08 | 网易（杭州）网络有限公司 | Server management method and system |
| CN113382282A (en) * | 2021-06-08 | 2021-09-10 | 南京炫佳网络科技有限公司 | Page resource access method and device, electronic equipment and storage medium |
-
2021
- 2021-09-27 CN CN202111135522.9A patent/CN113849373A/en active Pending
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150089061A1 (en) * | 2012-12-24 | 2015-03-26 | Telefonaktiebolaget L M Ericsson (Publ) | Enabling external access to multiple services on a local server |
| CN105075225A (en) * | 2012-12-24 | 2015-11-18 | 瑞典爱立信有限公司 | Enabling external access to multiple services on a local server |
| CN105141672A (en) * | 2015-08-03 | 2015-12-09 | 广州神马移动信息科技有限公司 | Method, device and system for data storage |
| CN107547671A (en) * | 2016-06-29 | 2018-01-05 | 中兴通讯股份有限公司 | A kind of URL matching process and device |
| CN110555041A (en) * | 2018-03-30 | 2019-12-10 | 腾讯科技（深圳）有限公司 | Data processing method, data processing device, computer equipment and storage medium |
| CN109245928A (en) * | 2018-09-12 | 2019-01-18 | 广州视源电子科技股份有限公司 | Configuration information setting method and device and terminal management system |
| CN110781356A (en) * | 2019-09-25 | 2020-02-11 | 苏州浪潮智能科技有限公司 | Hardware query method, equipment and storage medium based on management platform |
| CN110995806A (en) * | 2019-11-24 | 2020-04-10 | 济南浪潮数据技术有限公司 | Resource state conversion method, device, equipment and storage medium |
| CN111147312A (en) * | 2019-12-31 | 2020-05-12 | 深圳云天励飞技术有限公司 | Resource allocation management method and device, resource allocation cache management method and device, and allocation management system |
| CN111212154A (en) * | 2019-12-31 | 2020-05-29 | 瑞庭网络技术（上海）有限公司 | Service binding method, device, terminal, server and storage medium |
| CN111447109A (en) * | 2020-03-23 | 2020-07-24 | 京东方科技集团股份有限公司 | Monitoring management apparatus and method, computer readable storage medium |
| CN112199197A (en) * | 2020-10-23 | 2021-01-08 | 网易（杭州）网络有限公司 | Server management method and system |
| CN113382282A (en) * | 2021-06-08 | 2021-09-10 | 南京炫佳网络科技有限公司 | Page resource access method and device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110474896B (en) | Data communication method based on Modbus protocol standard and related equipment | |
| CN110276074B (en) | Distributed training method, device, equipment and storage medium for natural language processing | |
| US9594548B2 (en) | Dynamically updating templated applications | |
| US20080250055A1 (en) | Method and Device for Coding a Hierarchized Document | |
| CN111209005A (en) | Method and apparatus for compiling program file, and computer-readable storage medium | |
| US11579931B2 (en) | Resource determination based on resource definition data | |
| CN111064626B (en) | Configuration updating method, device, server and readable storage medium | |
| US11263542B2 (en) | Technologies for auto discover and connect to a rest interface | |
| CN110321283A (en) | Interface testing case generation method, device, computer installation and storage medium | |
| CN111061464A (en) | Analysis code generation method, device, equipment and storage medium | |
| WO2023029881A1 (en) | Device control method and apparatus | |
| CN113535141A (en) | Database operation code generation method and device | |
| US20070092069A1 (en) | Method and system for testing enterprise applications | |
| CN112463261B (en) | Interface calling method, device, electronic equipment, medium and product | |
| US8959191B2 (en) | Script modification suggestion | |
| CN106484488B (en) | Integrated cloud Compilation Method and system | |
| JP7509886B2 (en) | Method and apparatus for pushing subscription data in the internet of things, and devices and storage media thereof | |
| CN112579682B (en) | Method and device for notifying change of data model, electronic equipment and storage medium | |
| CN113268232B (en) | Page skin generation method and device and computer readable storage medium | |
| CN116628141B (en) | Information processing method, device, equipment and storage medium | |
| CN113849373A (en) | Server supervision method and device and storage medium | |
| CN113282489B (en) | Interface testing method and device | |
| US11579930B2 (en) | Resource determination based on resource definition data | |
| CN115935909A (en) | File generation method and device and electronic equipment | |
| CN113708971A (en) | Openstack cloud platform deployment method and related device |
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 |