System for Providing Autonomous Remediation Within a Data Center
A system, method, and computer-readable medium for performing a data center monitoring and management operation. The data center monitoring and management operation includes: monitoring data center assets within a data center; identifying an issue within the data center, the issue being associated with an operational situation associated with a particular component of the data center; notifying an administrator of the issue within the data center; identifying a remediation task, the remediation task being designed to address the issue within the data center; and, generating a remediation rule to autonomously perform the remediation task.
Latest Dell Products L.P. Patents:
- Isolated environment provisioning in service mesh-based microservices systems
- Information handling system multi-stream cable throughput management
- Heater apparatus-integrated bezel for a computing device
- Heater apparatus and air circulation component-integrated bezel for a computing device
- Enabling dial home service requests from an application executing in an embedded environment
The present invention relates to information handling systems. More specifically, embodiments of the invention relate to performing a data center system monitoring and management operation.
Description of the Related ArtAs the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
SUMMARY OF THE INVENTIONIn one embodiment the invention relates to a method for performing a data center monitoring and management operation, comprising: monitoring data center assets within a data center; identifying an issue within the data center, the issue being associated with an operational situation associated with a particular component of the data center; notifying an administrator of the issue within the data center; identifying a remediation task, the remediation task being designed to address the issue within the data center; and, generating a remediation rule to autonomously perform the remediation task.
In another embodiment the invention relates to a system comprising: a processor; a data bus coupled to the processor; and a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for: monitoring data center assets within a data center; identifying an issue within the data center, the issue being associated with an operational situation associated with a particular component of the data center; notifying an administrator of the issue within the data center; identifying a remediation task, the remediation task being designed to address the issue within the data center; and, generating a remediation rule to autonomously perform the remediation task.
In another embodiment the invention relates to a computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for: monitoring data center assets within a data center; identifying an issue within the data center, the issue being associated with an operational situation associated with a particular component of the data center; notifying an administrator of the issue within the data center; identifying a remediation task, the remediation task being designed to address the issue within the data center; and, generating a remediation rule to autonomously perform the remediation task.
The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference number throughout the several figures designates a like or similar element.
A system, method, and computer-readable medium are disclosed for performing a data center system monitoring and management operation. Various aspects of the invention reflect an appreciation that it is common for a typical datacenter to monitor and manage many different assets, such as certain computing and networking devices, described in greater detail herein. Certain aspects of the invention likewise reflect an appreciation that such data center assets are typically implemented to work in combination with one another for a particular purpose. Likewise, various aspects of the invention reflect an appreciation that such purposes generally involve the performance of a wide variety of tasks, operations, and processes to service certain workloads. Accordingly, various aspects of the invention reflect an appreciation that efficient and effective monitoring and management of certain data center assets may assist in optimizing the availability, performance, and reliability of the services offered by a data center.
Various aspects of the invention reflect an appreciation that data center system administrators, beyond their day-to-day monitoring and management duties, often have the additional responsibility of remediating certain data center issues, described in greater detail herein. Certain aspects of the invention likewise reflect an appreciation that the complexity of remediating such data center issues generally grows in proportion to the number of data center assets that are being monitored and managed. Various aspects of the invention reflect an appreciation that certain data center issues may be remediated remotely from a data center monitoring and management console, described in greater detail herein, whereas others may require physical interaction with one or more data center assets to resolve a particular issue.
Certain aspects of the invention likewise reflect an appreciation that data center issue remediation processes often involve a data center administrator physically monitoring the data center environment and engaging with critical alerts and issues as they occur. Likewise, various aspects of the invention reflect an appreciation that a data center administrator may need to manually update firmware, reboot certain hardware, or even escalate the data center issue for remediation. Various aspects of the invention reflect an appreciation that the autonomous performance of certain data center remediation operations may result in utilizing data center personnel more efficiently certain data center issues being remediated more quickly, and as such, may lead to higher quality of service levels and user satisfaction.
For purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, or other purposes. For example, an information handling system may be a personal computer, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include random access memory (RAM), one or more processing resources such as a central processing unit (CPU) or hardware or software control logic, ROM, and/or other types of nonvolatile memory. Additional components of the information handling system may include one or more disk drives, one or more network ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communications between the various hardware components.
In certain embodiments, the data center monitoring and management console 118 may include a monitoring module 120, a management module 122, a user interface engine 124, and an autonomous remediation engine 126, or a combination thereof. In certain embodiments, the data center monitoring and management console 118 may be implemented to perform a data center monitoring and management operation. In certain embodiments, the data center monitoring and management operation may be performed during operation of an information handling system 100. In various embodiments, performance of the data center monitoring and management operation may result in the realization of improved monitoring and management of certain data center assets, as described in greater detail herein.
As used herein, a tangible data center asset 244 broadly refers to data center asset 244 having a physical substance, such as a computing or network device. Examples of computing devices may include personal computers (PCs), laptop PCs, tablet computers, servers, mainframe computers, Redundant Arrays of Independent Disks (RAID) storage units, their associated internal and external components, and so forth. Likewise, examples of network devices may include routers, switches, hubs, repeaters, bridges, gateways, and so forth. Other examples of a tangible data center asset 244 may include certain data center personnel, such as a data center system administrator, operator, or technician, and so forth. Other examples of a tangible data center asset 244 may include certain maintenance, repair, and operations (MRO) items, such as replacement and upgrade parts for a particular data center asset 244. In certain embodiments, such MRO items may be in the form of consumables, such as air filters, fuses, fasteners, and so forth.
As likewise used herein, an intangible data center asset 244 broadly refers to a data center asset 244 that lacks physical substance. Examples of intangible data center assets 244 may include software, firmware, and other non-physical, computer-based assets. Other examples of intangible data center assets 244 may include digital assets, such as structured and unstructured data of all kinds, still images, video images, audio recordings of speech, and other sounds, and so forth. Further examples of intangible data center assets 244 may include intellectual property, such as patents, trademarks, copyrights, trade names, franchises, goodwill, and knowledge resources, such as data center asset 244 documentation. Yet other examples of intangible data center assets 244 may include certain tasks, functions, operations, procedures, or processes performed by data center personnel. Those of skill in the art will recognize that many such examples of tangible and intangible data center assets 244 are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.
In certain embodiments, the value produced by a data center asset 244 may be tangible or intangible. As used herein, tangible value broadly refers to value that can be measured. Examples of tangible value may include return on investment (ROI), total cost of ownership (TCO), internal rate of return (IRR), increased performance, more efficient use of resources, improvement in sales, decreased customer support costs, and so forth. As likewise used herein, intangible value broadly refers to value that provides a benefit that may be difficult to measure. Examples of intangible value may include improvements in user experience, customer support, and market perception. Skilled practitioner of the art will recognize that many such examples of tangible and intangible value are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.
In certain embodiments, the data center monitoring and management environment 200 may include a data center monitoring and management console 118. In certain embodiments, the data center monitoring and management console 118 may be implemented to perform a data center monitoring and management operation. As used herein, a data center monitoring and management operation broadly refers to any task, function, procedure, or process performed, directly or indirectly, within a data center monitoring and management environment 200 to procure, deploy, configure, implement, operate, monitor, manage, maintain, or remediate a data center asset 244.
In certain embodiments, a data center monitoring and management operation may include a data center monitoring task. As used herein, a data center monitoring task broadly refers to any function, operation, procedure, or process performed, directly or indirectly, within a data center monitoring and management environment 200 to monitor the operational status of a particular data center asset 244. In various embodiments, a particular data center asset 244 may be implemented to generate an alert if its operational status exceeds certain parameters. In these embodiments, the definition of such parameters, and the method by which they may be selected, is a matter of design choice.
For example, an internal cooling fan of a server may begin to fail, which in turn may cause the operational temperature of the server to exceed its rated level. In this example, the server may be implemented to generate an alert, which provides notification of the occurrence of a data center issue. As used herein, a data center issue broadly refers to an operational situation associated with a particular component of a data monitoring and management environment 200, which if not corrected, may result in negative consequences. In certain embodiments, a data center issue may be related to the occurrence, or predicted occurrence, of an anomaly within the data center monitoring and management environment 200. In certain embodiments, the anomaly may be related to unusual or unexpected behavior of one or more data center assets 244.
In certain embodiments, a data center monitoring and management operation may include a data center management task. As used herein, a data center management task broadly refers to any function, operation, procedure, or process performed, directly or indirectly, within a data center monitoring and management environment 200 to manage a particular data center asset 244. In certain embodiments, a data center management task may include a data center deployment operation, a data center remediation operation, a data center remediation documentation operation, or a combination thereof.
As used herein, a data center deployment operation broadly refers to any function, task, procedure, or process performed, directly or indirectly, within a data center monitoring and management environment 200 to install a software file, such as a configuration file, a new software application, a version of an operating system, and so forth, on a data center asset 244. As likewise used herein, a data center remediation operation broadly refers to any function, task, procedure, or process performed, directly or indirectly, within a data center monitoring and management environment 200 to correct an operational situation associated with a component of a data monitoring and management environment 200, which if not corrected, may result in negative consequences. A data center remediation documentation operation, as likewise used herein, broadly refers to any function, task, procedure, or process performed, directly or indirectly, within a data center monitoring and management environment 200 to retrieve, generate, revise, update, or store remediation documentation that may be used in the performance of a data center remediation operation.
In certain embodiments, the data center monitoring and management console 118 may be implemented to receive an alert corresponding to a particular data center issue. In various embodiments, the data center monitoring and management console 118 may be implemented to receive certain information associated with the operation of a particular data center asset 244. In certain embodiments, such operational information may be received through the use of telemetry approaches familiar to those of skill in the art. In various embodiments, the data center monitoring console 118 may be implemented to process certain operational information received from a particular data center asset to determine whether a data center issue has occurred, is occurring, or is anticipated to occur.
In certain embodiments, the data center monitoring and management console 118 may be implemented to include a monitoring module 120, a management monitor 122, a user interface (UI) engine 124, and an autonomous remediation engine 126, or a combination thereof. In certain embodiments, the monitoring module 120 may be implemented to monitor the procurement, deployment, implementation, operation, management, maintenance, or remediation of a particular data center asset 244 at any point in its lifecycle. In certain embodiments, the management module 122 may be implemented to manage the procurement, deployment, implementation, operation, monitoring, maintenance, or remediation of a particular data center asset 244 at any point in its lifecycle. In various embodiments, the UI engine 124 may be implemented to generate a UI for the provision, or receipt, of certain information associated with the monitoring, or management, of a particular data center asset 244. In various embodiments, the autonomous remediation engine 126 may be implemented to perform an autonomous remediation operation, described in greater detail herein.
In certain embodiments, the data center monitoring and management environment 200 may include a repository of data center monitoring and management data 220. In certain embodiments, the repository of data center monitoring and management data 220 may be local to the information handling system 100 executing the data center monitoring and management console 118 or may be located remotely. In various embodiments, the repository of data center monitoring and management data 220 may include certain information associated with data center asset data 222, data center asset configuration rules 224, data center infrastructure data 226, data center remediation data 228, and data center personnel data 230.
As used herein, data center asset data 222 broadly refers to information associated with a particular data center asset 244, such as an information handling system 100, which can be read, measured, and structured into a usable format. For example, data center asset data 222 associated with a particular server may include the number and type of processors it can support, their speed and architecture, minimum and maximum amounts of memory supported, various storage configurations, the number, type, and speed of input/output channels and ports, and so forth. In various embodiments, the data center asset data 222 may likewise include certain performance and configuration information associated with a particular workload, as described in greater detail herein. In various embodiments, the data center asset data 222 may include certain public or proprietary information related to data center asset 244 configurations associated with a particular workload. In certain embodiments, the data center asset data 224 may include information associated with data center asset 244 types, quantities, locations, use types, optimization types, workloads, performance, support information, and cost factors, or a combination thereof, as described in greater detail herein. In certain embodiments, the data center asset data 224 may include information associated with data center asset 244 utilization patterns, likewise described in greater detail herein.
As likewise used herein, a data center asset configuration rule 224 broadly refers to a rule used to configure a particular data center asset 244. In certain embodiments, one or more data center asset configuration rules 224 may be used to verify that a particular data center asset 244 configuration is the most optimal for an associated location, or workload, or to interact with other data center assets 244, or a combination thereof, as described in greater detail herein. In certain embodiments, the data center asset configuration rule 224 may be used in the performance of a data center asset configuration verification operation, a data center remediation operation, or a combination of the two. In certain embodiments, the data center asset configuration verification operation, or the data center remediation operation, or both, may be performed by an asset configuration system 250. In certain embodiments, the asset configuration system 250 may be used in combination with the data center monitoring and management console 118 to perform a data center asset configuration operation, or a data center remediation operation, or a combination of the two.
As used herein, data center infrastructure 226 data broadly refers to any data associated with a data center infrastructure component. As likewise used herein, a data center infrastructure component broadly refers to any component of a data center monitoring and management environment 200 that may be involved, directly or indirectly, in the procurement, deployment, implementation, configuration, operation, monitoring, management, maintenance, or remediation of a particular data center asset 244. In certain embodiments, data center infrastructure components may include physical structures, such as buildings, equipment racks and enclosures, network and electrical cabling, heating, cooling, and ventilation (HVAC) equipment and associated ductwork, electrical transformers and power conditioning systems, water pumps and piping systems, smoke and fire suppression systems, physical security systems and associated peripherals, and so forth. In various embodiments, data center infrastructure components may likewise include the provision of certain services, such as network connectivity, conditioned airflow, electrical power, and water, or a combination thereof.
Data center remediation data 228, as used herein, broadly refers to any data associated with the performance of a data center remediation operation, described in greater details herein. In certain embodiments, the data center remediation data 228 may include information associated with the remediation of a particular data center issue, such as the date and time an alert was received indicating the occurrence of the data center issue. In certain embodiments, the data center remediation data 228 may likewise include the amount of elapsed time before a corresponding data center remediation operation was begun after receiving the alert, and the amount of elapsed time before it was completed. In various embodiments, the data center remediation data 228 may include information related to certain data center issues, the frequency of their occurrence, their respective causes, error codes associated with such data center issues, the respective location of each data center asset 244 associated with such data center issues, and so forth.
In various embodiments, the data center remediation data 228 may include information associated with data center asset 244 replacement parts, or upgrades, or certain third party services that may need to be procured in order to perform the data center remediation operation. Likewise, in certain embodiments, related data center remediation data 228 may include the amount of elapsed time before the replacement parts, or data center asset 244 upgrades, or third party services were received and implemented. In certain embodiments, the data center remediation data 228 may include information associated with data center personnel who may have performed a particular data center remediation operation. Likewise, in certain embodiments, related data center remediation data 228 may include the amount of time the data center personnel actually spent performing the operation, issues encountered in performing the operation, and the eventual outcome of the operation that was performed.
In certain embodiments, the data center remediation data 228 may include remediation documentation associated with a particular data center asset 244. In various embodiments, such remediation documentation may include information associated with certain attributes, features, characteristics, functional capabilities, operational parameters, and so forth, of a particular data center asset 244. In certain embodiments, such remediation documentation may likewise include information, such as step-by-step procedures and associated instructions, video tutorials, diagnostic routines and tests, checklists, and so forth, associated with remediating a particular data center issue.
In certain embodiments, the data center remediation data 228 may include information associated with any related remediation dependencies, such as other data center remediation operations that may need to be performed beforehand. In certain embodiments, the data center remediation data 228 may include certain time restrictions when a data center remediation operation, such as rebooting a particular server, may be performed. In various embodiments, the data center remediation data 228 may likewise include certain autonomous remediation rules, described in greater detail herein. In various embodiments, certain of these autonomous remediation rules may be used in the performance of an autonomous remediation operation, described in greater detail herein. Those of skill in the art will recognize that many such examples of data center remediation data 228 are possible. Accordingly, the foregoing is not intended to limit the spirit, scope, or intent of the invention.
Data center personnel data 230, as used herein, broadly refers to any data associated with data center personnel who may be directly, or indirectly, involved in the procurement, deployment, configuration, implementation, operation, monitoring, management, maintenance, or remediation of a particular data center asset 244. In various embodiments, the data center personnel data 230 may include job title, work assignment, or responsibility information corresponding to certain data center personnel. In various embodiments, the data center personnel data 230 may include information related to the type, and number, of data center remediation operations currently being, or previously, performed by certain data center personnel. In various embodiments, the data center personnel data 230 may include historical information, such as success metrics, associated with data center remediation operations performed by certain data center personnel, such as data center administrators, operators, and technicians. In these embodiments, the data center personnel data 230 may be updated as individual data center personnel complete each data center remediation task, described in greater detail herein, they are assigned.
In various embodiments, the data center personnel data 230 may likewise include education, certification, and skill level information corresponding to certain data center personnel. Likewise, in various embodiments, the data center personnel data 230 may include security-related information, such as security clearances, user IDs, passwords, security-related biometrics, authorizations, and so forth, corresponding to certain data center personnel. Those of skill in the art will recognize that many such examples of data center personnel data 230 are possible. Accordingly, the foregoing is not intended to limit the spirit, scope, or intent of the invention.
In certain embodiments, various data center assets 244 within a data center monitoring and management environment 200 may have certain interdependencies. As an example, a data center monitoring and management environment 200 may have multiple servers interconnected by a storage area network (SAN) providing block-level access to various disk arrays and tape libraries. In this example, the servers, various physical and operational elements of the SAN, as well the disk arrays and tape libraries, are interdependent upon one another.
In certain embodiments, each data center asset 244 in a data center monitoring and management environment 200 may be treated as a separate data center asset 244 and depreciated individually according to their respective attributes. As an example, a particular rack of servers in a data center monitoring and management environment 200 may be made up of a variety of individual servers, each of which may have a different depreciation schedule. To continue the example, certain of these data center assets 244 may be implemented in different combinations to produce an end result. To further illustrate the example, a particular server in the rack of servers may initially be implemented to query a database of customer records. As another example, the same server may be implemented at later time perform a sales analysis of sales associated with those same customer records.
In certain embodiments, each data center asset 244 in a data center monitoring and management environment 200 may have an associated maintenance schedule and service contract. For example, a data center monitoring and management environment 200 may include a wide variety of servers and storage arrays, which may respectively be manufactured by a variety of manufacturers. In this example, the frequency and nature of scheduled maintenance, as well as service contract terms and conditions, may be different for each server and storage array. In certain embodiments, the individual data center assets 244 in a data center monitoring and management environment 200 may be configured differently, according to their intended use. To continue the previous example, various servers may be configured with faster or additional processors for one intended workload, while other servers may be configured with additional memory for other intended workloads. Likewise, certain storage arrays may be configured as one RAID configuration, while others may be configured as a different RAID configuration.
In certain embodiments, the data center monitoring and management environment 200 may likewise be implemented to include an asset configuration system 250, a product configuration system 252, a product fabrication system 254, and a supply chain system 256, or a combination thereof. In various embodiments, the asset configuration system 250 may be implemented to perform certain data center asset 244 configuration operations. In certain embodiments, the data center asset 244 configuration operation may be performed to configure a particular data center asset 244 for a particular purpose. In certain embodiments, the data center monitoring and management console 118 may be implemented to interact with the asset configuration system 250 to perform a particular data center asset 244 configuration operation. In various embodiments, the asset configuration system 250 may be implemented to generate, manage, and provide, or some combination thereof, data center asset configuration rules 224. In certain of these embodiments, the data center asset configuration rules 224 may be used to configure a particular data center asset 244 for a particular purpose.
In certain embodiments, a user 202 may use a user device 204 to interact with the data center monitoring and management console 118. As used herein, a user device 204 refers to an information handling system such as a personal computer, a laptop computer, a tablet computer, a personal digital assistant (PDA), a smart phone, a mobile telephone, or other device that is capable of processing and communicating data. In certain embodiments, the communication of the data may take place in real-time or near-real-time. As used herein, real-time broadly refers to processing and providing information within a time interval brief enough to not be discernable by a user 202.
In certain embodiments, a user device 204 may be implemented with a camera 206, such as a video camera known to skilled practitioners of the art. In certain embodiments, the camera 206 may be integrated into the user device 204. In certain embodiments, the camera 206 may be implemented as a separate device configured to interoperate with the user device 204. As an example, a webcam familiar to those of skill in the art may be implemented receive and communicate various image and audio signals to a user device 204 via a Universal Serial Bus (USB) interface.
In certain embodiments, the user device 204 may be configured to present a data center monitoring and management console user interface (UI) 240. In certain embodiments, the data center monitoring and management console UI 240 may be implemented to present a graphical representation 242 of data center asset monitoring and management information, which is automatically generated in response to interaction with the data center monitoring and management console 118. In certain embodiments, the UI engine 124 may be implemented to generate the data center monitoring and management console UI 240, or the graphical representation 242 presented therein, or both.
In certain embodiments, a data center monitoring and management application 238 may be implemented on a particular user device 204. In various embodiments, the data center monitoring and management application 238 may be implemented on a mobile user device 204. such as a laptop computer, a tablet computer, a smart phone, a dedicated-purpose mobile device, and so forth. In certain of these embodiments, the mobile user device 204 may be used at various locations within the data center monitoring and management environment 200 by the user 202 when performing a data center monitoring and management operation, described in greater detail herein.
In various embodiments, the data center monitoring and management application 238 may be implemented to facilitate a user 202, such as a data center administrator, operator, or technician, to perform a particular data center remediation operation. In various embodiments, such facilitation may include using the data center monitoring and management application 238 to receive a notification of a data center remediation task, described in greater detail herein, being assigned to the user. In certain embodiments, the data center monitoring and management console 118 may be implemented to generate the notification of the data center remediation task assignment, and assign it to the user, as likewise described in greater detail herein. In certain embodiments, the data center monitoring and management console 118 may be implemented to generate the data center remediation task, and once generated, provide it to the data center monitoring and management application 238 associated with the assigned user 202.
In certain embodiments, such facilitation may include using the data center monitoring and management application 238 to receive the data center remediation task from the data center monitoring and management console 118. In various embodiments, such facilitation may include using the data center monitoring and management application 238 to confirm that the user 202 is at the correct physical location of a particular data center asset 244 associated with a corresponding data center issue. In certain of these embodiments, the data center monitoring and management application 238 may be implemented to include certain Global Positioning System (GPS) capabilities, familiar to those of skill in the art, which may be used to determine the physical location of the user 202 in relation to the physical location of a particular data center asset 244.
In various embodiments, such facilitation may include using the data center monitoring and management application 238 to ensure the user 202 is aware of, or is provided the location of, or receives, or a combination thereof, certain remediation resources, described in greater detail herein, that may be needed to perform a particular data center remediation operation. In various embodiments, such facilitation may include using the data center monitoring and management application 238 to view certain remediation documentation, or augmented instructions, related to performing a particular data center remediation operation. In various embodiments, such facilitation may include using the data center monitoring and management application 238 to certify that a particular data center remediation operation has been performed successfully.
In certain embodiments the UI window 240 may be implemented as a UI window of the data center monitoring and management application 238. In various embodiments, the data center monitoring and management application 238 may be implemented to include, in part or in whole, certain functionalities associated with the data center monitoring and management console 118. In certain embodiments, the data center monitoring and management application 238 may be implemented to interact in combination with the data center monitoring and management console 118, and other components of the data center monitoring and management environment 200, to perform a data center monitoring and management operation.
In certain embodiments, the user device 204 may be used to exchange information between the user 202 and the data center monitoring and management console 118, the data center monitoring and management application 238, the asset configuration system 250, the product configuration system 252, the product fabrication system 254, and the supply chain system 256, or a combination thereof, through the use of a network 140. In various embodiments, the asset configuration system 250 may be implemented to configure a particular data center asset 244 to meet certain performance goals. In various embodiments, the asset configuration system 250 may be implemented to use certain data center monitoring and management data 220, certain data center asset configuration rules 226 it may generate or manage, or a combination thereof, to perform such configurations.
In various embodiments, the product configuration system 252 may be implemented to use certain data center monitoring and management data 220 to optimally configure a particular data center asset 244, such as a server, for an intended workload. In various embodiments, the data center monitoring and management data 220 used by the product configuration system 252 may have been generated as a result of certain data center monitoring and management operations, described in greater detail herein, being performed by the data center monitoring and management console 118. In various embodiments, the product configuration system 252 may be implemented to provide certain product configuration information to a product fabrication system 254. In various embodiments, the product fabrication system 254 may be implemented to provide certain product fabrication information to a product fabrication environment (not shown). In certain embodiments, the product fabrication information may be used by the product fabrication environment to fabricate a product, such as a server, to match a particular data center asset 244 configuration.
In various embodiments, the data center monitoring and management console UI 240 may be presented via a website (not shown). In certain embodiments, the website may be provided by one or more of the data center monitoring and management console 118, the asset configuration system 250, the product configuration system 252, the product fabrication system 254, or the supply chain system 256. In certain embodiments, the supply chain system 256 may be implemented to manage the provision, fulfillment, or deployment of a particular data center asset 244 produced in the product fabrication environment. For the purposes of this disclosure a website may be defined as a collection of related web pages which are identified with a common domain name and is published on at least one web server. A website may be accessible via a public IP network or a private local network.
A web page is a document which is accessible via a browser which displays the web page via a display device of an information handling system. In various embodiments, the web page also includes the file which causes the document to be presented via the browser. In various embodiments, the web page may comprise a static web page, which is delivered exactly as stored and a dynamic web page, which is generated by a web application that is driven by software that enhances the web page via user input 208 to a web server.
In certain embodiments, the data center monitoring and management console 118 may be implemented to interact with the asset configuration system 250, the product configuration system 252, the product fabrication system 254, and the supply chain or fulfillment system 256, or a combination thereof, each of which in turn may be executing on a separate information handling system 100. In certain embodiments, the data center monitoring and management console 118 may be implemented to interact with the asset configuration system 250, the product configuration system 252, the product fabrication system 254, and the supply chain or fulfillment system 256, or a combination thereof, to perform a data center monitoring and management operation, as described in greater detail herein.
As described in greater detail herein, the data center monitoring and management console 118 may be implemented in certain embodiments to perform a data center monitoring and management operation. In certain embodiments, the data center monitoring and management console 118 may be implemented to provide a unified framework for the performance of a plurality of data center monitoring and management operations, by a plurality of users, within a common user interface (UI). In certain embodiments, the data center monitoring and management console 118, and other components of the data center monitoring environment 200, such as the asset configuration system 250, may be implemented to be used by a plurality of users, such as users ‘A’ 302 through ‘x’ 312 shown in
In certain embodiments, such interactions may be respectively presented to users ‘A’ 302 through ‘x’ 312 within a user interface (UI) window 306 through 316, corresponding to user devices ‘A’ 304 through ‘x’ 314. In certain embodiments the UI window 306 through 316 may be implemented in a window of a web browser, familiar to skilled practitioners of the art. In certain embodiments, a data center monitoring and management application 310 through 320, described in greater detail herein, may be respectively implemented on user devices ‘A’ 304 through ‘x’ 314. In certain embodiments the UI window 306 through 316 may be respectively implemented as a UI window of the data center monitoring and management application 310 through 320. In certain embodiments, the data center monitoring and management application 310 through 320 may be implemented to interact in combination with the data center monitoring and management console 118, and other components of the data center monitoring and management environment 200, to perform a data center monitoring and management operation.
In certain embodiments, the interactions with the data center monitoring and management console 118, and other components of the data center monitoring and management environment 200, may respectively be presented as a graphical representation 308 through 318 within UI windows 306 through 316. In various embodiments, such interactions may be presented to users ‘A’ 302 through ‘x’ 312 via a display device 324, such as a projector or large display screen. In certain of these embodiments, the interactions may be presented to users ‘A’ 302 through ‘x’ 312 as a graphical representation 338 within a UI window 336.
In certain embodiments, the display device 324 may be implemented in a command center 350, familiar to those of skill in the art, such as a command center 350 typically found in a data center or a network operations center (NOC). In various embodiments, one or more of the users ‘A’ 302 through ‘x’ 312 may be located within the command center 350. In certain of these embodiments, the display device 324 may be implemented to be generally viewable by one or more of the users ‘A’ 302 through ‘x’ 312.
In certain embodiments, the data center monitoring and management operation may be performed to identify the location 350 of a particular data center asset 244. In certain embodiments, the location 350 of a data center asset 244 may be physical, such as the physical address of its associated data center, a particular room in a building at the physical address, a particular location in an equipment rack in that room, and so forth. In certain embodiments, the location 350 of a data center asset 244 may be non-physical, such as a network address, a domain, a Uniform Resource Locator (URL), a file name in a directory, and so forth.
Certain embodiments of the invention reflect an appreciation that it is not uncommon for large organization to have one or more data centers, such as data centers ‘1’ 346 through ‘n’ 348. Certain embodiments of the invention reflect an appreciation that it is likewise not uncommon for such data centers to have multiple data center system administrators and data center technicians. Likewise, various embodiments of the invention reflect an appreciation that it is common for a data center system administrator to be responsible for planning, initiating, and overseeing the execution of certain data center monitoring and management operations. Certain embodiments of the invention reflect an appreciation that it is common for a data center system administrator, such as user ‘A’ 302, to assign a particular data center monitoring and management operation to a data center technician, such as user ‘x’ 312, as a task to be executed.
Certain embodiments of the invention reflect an appreciation that it is likewise common for a data center administrator, such as user ‘A’ 302, to assume responsibility for performing a particular data center monitoring and management operation. As an example, a data center administrator may receive a stream of data center alerts, each of which is respectively associated with one or more data center issues. To continue the example, several of the alerts may have an initial priority classification of “critical.” However, the administrator may notice that one such alert may be associated with a data center issue that is more critical, or time sensitive, than the others and should be remediated as quickly as possible. Accordingly, the data center administrator may elect to assume responsibility for remediating the data center issue, and as a result, proceed to perform an associated data center remediation operation at that time instead of assigning it to other data center personnel.
Certain embodiments of the invention reflect an appreciation that the number of data center assets 244 in a particular data center ‘1’ 346 through ‘n’ 348 may be quite large. Furthermore, it is not unusual for such data center assets 244 to be procured, deployed, configured, and implemented on a scheduled, or as needed, basis. It is likewise common for certain existing data center assets 244 to be replaced, upgraded, reconfigured, maintained, or remediated on a scheduled, or as-needed, basis. Likewise, certain embodiments of the invention reflect an appreciation that such replacements, upgrades, reconfigurations, maintenance, or remediation may be oriented towards hardware, firmware, software, connectivity, or a combination thereof.
For example, a data center system administrator may be responsible for the creation of data asset 244 procurement, deployment, configuration, and implementation templates, firmware update bundles, operating system (OS) and software application stacks, and so forth. Likewise, a data center technician may be responsible for receiving a procured data center asset 244, transporting it to a particular data asset location 350 in a particular data center ‘1’ 346 through ‘n’ 348, and implementing it in that location 350. The same, or another, data center technician may then be responsible for configuring the data center asset 244, establishing network connectivity, applying configuration files, and so forth. To continue the example, the same, or another, data center administrator or technician may be responsible for remediating hardware issues, such as replacing a disc drive in a server or Redundant Array of Independent Disks (RAID) array, or software issues, such as updating a hardware driver or the version of a server's operating system. Accordingly, certain embodiments of the invention reflect an appreciation that a significant amount of coordination may be needed between data center system administrators and data center technicians to assure efficient and reliable operation of a data center.
In various embodiments, certain data center monitoring and management operations may include a data center remediation operation, described in greater detail herein. In certain embodiments, a data center remediation operation may be performed to remediate a particular data asset 244 issue at a particular data asset location 350 in a particular data center ‘1’ 346 through ‘n’ 348. In certain embodiments, the data center remediation operation may be performed to ensure that a particular data center asset location 350 in a particular data center ‘1’ 346 through ‘n’ 348 is available for the replacement or upgrade of an existing data center asset 244. As an example, a data center remediation operation may involve deployment of a replacement server that occupies more rack space than the server it will be replacing.
In various embodiments, the data center monitoring and management console 118, or the data center monitoring and management application 310 through 320, or a combination of the two, may be implemented in a failure tracking mode to capture certain data center asset 244 telemetry. In various embodiments, the data center asset 244 telemetry may include data associated with the occurrence of certain events, such as the failure, or anomalous performance, of a particular data center asset 244 in whole, or in part. In certain embodiments, the data center asset 244 telemetry may be captured incrementally to provide a historical perspective of the occurrence, and evolution, of an associated data center issue.
In various embodiments, the data center monitoring and management console 118 may likewise be implemented generate certain remediation operation notes. For example, the data center monitoring and management console 118 may enter certain data center asset 244 remediation instructions in the data center remediation operation notes. In various embodiments, the data center remediation operation notes may be implemented to contain information related to data center asset 244 replacement or upgrade parts, data center asset 244 files that may be needed, installation and configuration instructions related to such files, the physical location 350 of the data center asset 244, and so forth. In certain embodiments, a remediation task 344 may be generated by associating the previously-generated data center remediation operation notes with the remediation documentation, data center asset files, or other remediation resources 342 most pertinent to the data center issue, and the administrator, and any data center personnel selected or its remediation. As used herein, a data center remediation task 344 broadly refers to one or more data center remediation operations, described in greater detail herein, that can be assigned to one or more users ‘A’ 302 through ‘x’ 312.
Certain embodiments of the invention reflect an appreciation that a group of data center personnel, such as users ‘A’ 302 through ‘x’ 312, will likely possess different skills, certifications, levels of education, knowledge, experience, and so forth. As a result, remediation documentation that is suitable for certain data center personnel may not be suitable for others. For example, a relatively inexperienced data center administrator may be overwhelmed by a massive volume of detailed and somewhat arcane minutiae related to the configuration and administration of multiple virtual machines (VMs) on a large server. However, such remediation documentation may be exactly what a highly skilled and experienced data center administrator needs to remediate subtle server and VM configuration issues.
Conversely, the same highly skilled and experienced data center administrator may be hampered, or slowed down, by being provided remediation documentation that is too simplistic, generalized, or high-level for the data center issue they may be attempting to remediate. Likewise, an administrator who is moderately skilled in configuring VMs may benefit from having step-by-step instructions, and corresponding checklists, when remediating a VM-related data center issue. Accordingly, as used herein, pertinent remediation documentation broadly refers to remediation documentation applicable to a corresponding data center issue that is most suited to the skills, certifications, level of education, knowledge, experience, and so forth of the data center personnel assigned to its remediation.
In various embodiments, the data center monitoring and management console 118 may be implemented to generate a corresponding notification of the remediation task 344. In certain embodiments, the resulting notification of the remediation task 344 assignment may be provided to the one or more users ‘A’ 302 through ‘x’ 312 assigned to perform the remediation task 344. In certain embodiments, the notification of the remediation task 344 assignment may be respectively provided to the one or more users ‘A’ 302 through ‘x’ 312 within the UI 306 through 316 of their respective user devices ‘A’ 304 through ‘x’ 314. In certain embodiments, the notification of the remediation task 344 assignment, and the remediation task 344 itself, may be implemented such that they are only visible to the users ‘A’ 302 through ‘x’ 312 to which it is assigned.
In certain embodiments, the data center monitoring and management console 118 may be implemented to operate in a monitoring mode. As used herein, monitoring mode broadly refers to a mode of operation where certain monitoring information provided by the monitoring and management console 118 is available for use by one or more users ‘A’ 302 through ‘x’ 312. In certain embodiments, one or more of the users ‘A’ 302 through ‘x’ 312 may be command center 350 users. In certain embodiments, the data center monitoring and management console 118 may be implemented to operate in a management mode. As used herein, management mode broadly refers to a mode of operation where certain operational functionality of the data center monitoring and management console 118 is available for use by a user, such as users ‘A’ 302 through ‘x’ 312.
As used herein, a manual remediation mode of operation broadly refers to a mode of operation where one or more data center personnel are prompted by the data center monitoring and management console to manually perform each step of an autonomous remediation operation it has provided. In various embodiments, the data center monitoring and management console may be implemented to provide one or more candidate autonomous remediation operations that may be performed in a manual remediation mode of operation to remediate a particular data center issue. In these embodiments, the decision regarding which of the candidate autonomous remediation operations are selected to be performed, and the order in which they may be performed, is a matter of design choice. In various embodiments, the data center monitoring and management console may likewise be implemented to collect certain information associated with each step of a candidate autonomous remediation operation as it is performed to determine the effect it may have on remediating the data center issue.
In various embodiments, completion of all steps associated with a candidate autonomous remediation being performed in a manual remediation mode of operation may not result in successful remediation of a particular data center issue. In certain of these embodiments, the data center personnel performing the autonomous remediation operation in a manual remediation mode of operation may elect to manually perform additional data center remediation operations. In certain of these embodiments, information associated with the additional data center remediation operations may be collected and incorporated into a new autonomous remediation operation if their performance results in a successful remediation of the data center issue. In these embodiments, the decision regarding which additional data center remediation operations may be selected to be performed, and whether or not to incorporate them into a new autonomous remediation operation, is a matter of design choice.
As likewise used herein, a semi-automated remediation mode of operation broadly refers to a mode of operation where one or more data center personnel may elect to have certain steps of an autonomous remediation operation be performed automatically by the data center monitoring and management console that provided it, and perform other steps manually. In various embodiments, the data center monitoring and management console may be implemented to allow one or more data center personnel to decide which steps of a particular autonomous remediation operation are performed automatically and which are performed manually. In certain of these embodiments, the configuration of which steps of a particular autonomous remediation operation are performed automatically, and which are performed manually, may be defined, and saved, as a new semi-automated remediation mode of operation.
An automated remediation mode of operation, as used herein, broadly refers to a mode of operation where all steps of an autonomous remediation operation can be performed automatically by the data center monitoring and management console that provided it. In various embodiments, an autonomous remediation operation may be performed in an automated remediation mode of operation without the involvement of data center personnel. In certain of these embodiments, the autonomous remediation operation may be performed in an automated remediation mode of operation if the conditions of an autonomous remediation rule, described in greater detail herein, corresponding to a particular data center issue, are met. Skilled practitioners of the art will recognize that many such embodiments of an autonomous remediation operation, and its corresponding remediation mode of operation, are possible. Accordingly, the foregoing is not intended to limit the spirit, scope, or intent of the invention.
In various embodiments, certain data center issue input data 402 associated with a data center monitoring and management environment, described in greater detail herein, may be used in the performance of ongoing data center monitoring operation to detect 410 a data center issue, as likewise described in greater detail herein. In various embodiments, the data center issue input data 402 may include certain telemetry 404 data, historical 406 data, and target value 408 data associated with a particular data center asset. In certain embodiments, the telemetry 404 data may include information corresponding to the operational status of a particular data center asset. In certain embodiments, the historical 406 data may include information corresponding to a particular data center asset's lifecycle and remediation history. In certain embodiments, the target value 408 data may include information corresponding to certain optimum performance metrics, operating parameters, replacement or maintenance intervals, and so forth.
As an example, the telemetry 404 data may indicate the operating temperature of a server is approaching its upper limit. To continue the example, the historical 406 data may likewise indicate one or more fans within the server may be approaching their mean time before failure (MTBF) specification. To continue the example further, the target value 408 data may provide information related to the optimum operational temperature for the server as well as a preferred service interval for proactively replacing its fans.
In certain embodiments, the detection 410 of a data center issue may relate to the detection of an anomalous 412 event within a data center monitoring and management environment, described in greater detail herein. As an example, ten servers, each of which is of the same make, model, and configuration, receive a driver update. As a result, one of the servers crashes, while the other nine do not. In this example, the server that crashes is an anomalous 412 event.
In certain embodiments, the detection 410 of a data center issue may relate to recognizing the pattern 414 of a particular data center issue. As an example, the operational throughput of a server may decline more than twenty percent whenever an associated workflow utilizes more than ninety percent of its currently available memory. In this example, the correlation of the server's throughput to the utilization of its available memory establishes a recognizable pattern 414.
In certain embodiments, the detection 410 of a data center issue may relate to the detection of new data center issues 418 as they occur within a data center monitoring and management environment. As an example, a router port assigned to a particular server running a particular workload may have performed as expected for nine months, only to unexpectedly begin passing traffic intermittently. Furthermore, the ports of other routers of the same make, model, and configuration do not exhibit the same behavior. In this example, the unexpected intermittent performance of a router port that has been operating properly for an extended period of time is a new issue 416.
In certain embodiments, the detection 410 of a data center issue may relate to the detection of low visibility data center issues 418 as they occur within a data center monitoring and management environment. As an example, an individual disk drive in a redundant array of independent disks (RAID) may log infrequent read errors (e.g., an average of three a day). Since the disk drive is part of a RAID array, the other disk drives in the array tend to mask its erratic performance. However, the fact that the read errors are occurring on a regular basis indicate that the disk drive may fail at some point in the future. In this example, the infrequent read errors represent a low visibility issue 418.
In certain embodiments, the detection 410 of a data center issue may relate to the detection of ongoing unresolved data center issues 420 as they occur within a data center monitoring and management environment. As an example, a compressor in a cooling unit may cycle off for short periods of time at random intervals. However, despite best efforts by data center personnel, the cause for its behavior cannot be determined. In this example, the erratic behavior of the compressor is an ongoing unresolved issue 420.
In various embodiments, detection 410 of a data center issue may lead to the performance of a preliminary analysis of the issue to assign 422 it a data center issue priority level. In certain of these embodiments, the prioritization of a particular data center issue to be remediated may be established by assigning 422 a data center issue priority level value, such as ‘1’, ‘2’, ‘3’, ‘4’, and ‘5’. As an example, a particular data center issue may be assigned 422 a priority level value of ‘1’, which is the highest priority. In these embodiments, the method by which the prioritization level of a data center issue is determined, the method by which such prioritization is characterized and notated, and the method by which it is associated with a particular data center issue, is a matter of design choice.
In certain embodiments, the detected data center issue may be compared to the same, or substantively similar, data center issues that have been successfully remediated in the past to determine possible data center remediation operations to perform. In various embodiments, information associated with such similar, or substantively similar, data center issues, and the data center remediation operation used to successfully remediate them, may be used to identify 424 a data center remediation pattern. Accordingly, as used herein, a data center remediation pattern broadly refers to one or more data center remediation operations, performed individually, or in a particular sequence, or in parallel, or a combination thereof, that have proven to successfully remediate an associated data center issue.
In certain embodiments, the data center remediation operation used to successfully remediate the same, or substantively similar, data center issues in the past may be presented in ranked order of their respective efficacy. As an example, those data center remediation operations that are more likely to remediate a particular data center issue may have a higher ranking than those that are less likely to. In these embodiments, the method by which the efficacy of such data center remediation operations are determined, the method by which they are ranked, and the criteria by which the ranking is determined, is a matter of design choice. In various embodiments, identification 424 of a particular data center remediation pattern may likewise result in identifying 426 one or more associated autonomous remediation rules 434 whose use may be invoked as a result.
As used herein, an autonomous remediation rule 434 broadly refers to any information processing rule, familiar to skilled practitioners of the art, that can be used, directly or indirectly, in the performance of an autonomous data center remediation operation, described in greater detail herein. In various embodiments, one or more autonomous remediation rules 434 may be implemented to determine under what predefined conditions one or more autonomous remediation operations, and their respective remediation operation modes, may be used to remediate a particular data center issue. In these embodiments, the method by which an autonomous remediation rule 434 is defined, generated, invoked, applied, or otherwise used in the performance of one or more autonomous remediation operations, is a matter of design choice.
To continue a prior example, a data center cooling unit may have an inoperative compressor that needs to be replaced. In this example, the detected data center issue may have an associated data center issue remediation pattern of physically replacing the cooling unit's compressor. Accordingly, the identification 424 of the data center issue remediation pattern may result in the identification 426 of an associated autonomous remediation rule whose conditions include the condition that the autonomous remediation operation associated with replacing the compressor be performed in a manual remediation mode of operation. To continue the example, the conditions of the associated autonomous remediation rule may also include the condition that step-by-step instructions be provided regarding how the compressor is to be replaced, and that an acknowledgement of completion of each step is received before the next step is provided.
As another example, a router may be exhibiting occasional connection errors. In this example, the detected data center issue of occasional router connection errors may have an associated data center issue remediation pattern of remotely resetting the router. Accordingly, the identification 424 of the data center issue remediation pattern may trigger 426 an associated autonomous remediation rule whose conditions include the condition that the autonomous remediation operation associated with remotely resetting the router be performed in an automated remediation mode of operation. To continue the example, the conditions of the autonomous remediation rule may also include the condition that the data center issue's associated priority level be no higher than a value of ‘3’.
In certain embodiments, a user, such as a data center administrator or technician, may define 428 a particular remediation mode of operation, as described in greater detail herein. In certain embodiments, the defined 428 remediation mode of operation may be stored in a repository of remediation data, likewise described in greater detail herein, for future use. In these embodiments, the method by which a particular remediation mode of operation is defined, or stored, or retrieved for use in the future, is a matter of design choice.
In certain embodiments, a user, such as a data center administrator or technician, may select 430 a particular remediation mode of operation to be used in the performance of an associated autonomous remediation operation. In certain embodiments, a data center monitoring and management console, described in greater detail herein, may be implemented to select 430 a particular remediation mode of operation according to the conditions of a particular autonomous remediation rule 434 associated with a particular data center remediation operation, likewise described in greater detail. In various embodiments, a selected 432 remediation mode of operation may be used in accordance with a particular autonomous remediation rule 434 to perform one or more associated autonomous remediation operations.
In certain of these embodiments, a determination 436 may be made whether the selected 432 remediation mode of operation is an automated remediation mode of operation, and if so, whether it has a matching autonomous remediation rule 434 and data center remediation pattern. If so, then the data center remediation pattern is performed 438 according to the conditions of its matching autonomous remediation rule 434 in an automated remediation mode of operation. Once the data center remediation pattern has been performed, the user, such as a data center administrator or technician, is notified 440 of its outcome. In these embodiments, the method by which the user is notified of the completion of the data center remediation pattern, and its associated outcome, is a matter of design choice.
However, if may be determined 436 that the selected 432 remediation mode of operation is not an automated remediation mode of operation, or there is no matching autonomous remediation rule 434, or no matching data center remediation pattern. If so, then a data center remediation task, described in greater detail herein, is generated 442 and presented to the user. In turn, the user uses a manual or semi-automated remediation mode of operation to remediate the associated data center issue.
In various embodiments, certain steps of the autonomous remediation operation performed by the user may be captured as they are performed. In certain of these embodiments, the steps of the autonomous remediation operation may be captured manually by the user who performed them, or captured automatically by a data center monitoring and management console, or a combination of the two. In certain embodiments, the captured steps of the data center remediation operation may then be processed to generate a new autonomous remediation operation (not shown).
In certain embodiments, an analysis 446 of the manual or semi-automated performance 444 of the autonomous remediation operation may be performed. In various embodiments, certain remediation operation input data 448 may be used to perform the analysis 446. In various embodiments, the remediation operation input data 448 may include certain data center issue 450 data, autonomous remediation operation workflow 452 data, data center personnel emotional state 454 data, data center asset telemetry 456 data, data center issue prioritization 458 data, or a combination thereof.
In certain embodiments, the results of the analysis 446 of the performance 444 of the autonomous remediation operation may be used to generate 460 a new autonomous remediation rule 434. In certain embodiments, a determination 462 may be made to delete 464 that autonomous remediation rule 434. If so, then it is deleted 464. However, it may be determined 462 that the new autonomous remediation rule should be added 466 to existing autonomous remediation rules 434. If so, then it is added 466. In these embodiments the method by which a newly-generated autonomous remediation rule 434 is deleted, or added, as well as where an added autonomous remediation rule 434 may be stored for future use, is a matter of design choice.
As will be appreciated by one skilled in the art, the present invention may be embodied as a method, system, or computer program product. Accordingly, embodiments of the invention may be implemented entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in an embodiment combining software and hardware. These various embodiments may all generally be referred to herein as a “circuit,” “module,” or “system.” Furthermore, the present invention may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium.
Any suitable computer usable or computer readable medium may be utilized. The computer-usable or computer-readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, or a magnetic storage device. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
Computer program code for carrying out operations of the present invention may be written in an object oriented programming language such as Java, Smalltalk, C++ or the like. However, the computer program code for carrying out operations of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Embodiments of the invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
The present invention is well adapted to attain the advantages mentioned as well as others inherent therein. While the present invention has been depicted, described, and is defined by reference to particular embodiments of the invention, such references do not imply a limitation on the invention, and no such limitation is to be inferred. The invention is capable of considerable modification, alteration, and equivalents in form and function, as will occur to those ordinarily skilled in the pertinent arts. The depicted and described embodiments are examples only, and are not exhaustive of the scope of the invention.
Consequently, the invention is intended to be limited only by the spirit and scope of the appended claims, giving full cognizance to equivalents in all respects.
Claims
1. A computer-implementable method for performing a data center monitoring and management operation, comprising:
- monitoring data center assets within a data center, the monitoring using issue input data, the issue input data including telemetry data, historical data and target value data, the telemetry data comprising information corresponding to an operational status of a particular data center asset, the historical data comprising information corresponding to a lifecycle and remediation history of the particular data center asset and the target value data comprising information corresponding to one or more of performance metrics, operating parameters, and replacement or maintenance intervals;
- identifying an issue within the data center based upon the issue input data, the issue being associated with an operational situation associated with a particular component of the data center;
- notifying an administrator of the issue within the data center;
- identifying a remediation task, the remediation task being designed to address the issue within the data center; and,
- generating a remediation rule to autonomously perform the remediation task, the remediation rule comprising an information processing rule that is used in performance of an autonomous data center remediation operation, the remediation rule determining under what predefined conditions the autonomous remediation operation may be used to remediate a particular data center issue.
2. The method of claim 1, further comprising:
- defining a plurality of remediation modes of operation.
3. The method of claim 2, wherein:
- the plurality of remediation modes of operation comprise a manual remediation mode of operation, a semi-automated remediation mode of operation and an automated remediation mode of operation.
4. The method of claim 2, further comprising:
- selecting one of the plurality of remediation modes of operation; and,
- the generating the remediation rule to autonomously perform the remediation task takes into account the one of the plurality of remediation modes of operation.
5. The method of claim 1, further comprising:
- identifying a remediation pattern associated with the issue, the remediation pattern comprising a plurality of data center remediation operations that have proven to successfully remediate an associated data center issue.
6. The method of claim 5, further comprising:
- determining whether a rule exists for the remediation pattern;
- performing an autonomous remediation action when the rule exists; and,
- adding the remediation task to a remediation queue when the rules does not exist.
7. A system comprising:
- a processor;
- a data bus coupled to the processor; and
- a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for: monitoring data center assets within a data center, the monitoring using issue input data, the issue input data including telemetry data, historical data and target value data, the telemetry data comprising information corresponding to an operational status of a particular data center asset, the historical data comprising information corresponding to a lifecycle and remediation history of the particular data center asset and the target value data comprising information corresponding to one or more of performance metrics, operating parameters, and replacement or maintenance intervals; identifying an issue within the data center based upon the issue input data, the issue being associated with an operational situation associated with a particular component of the data center; notifying an administrator of the issue within the data center; identifying a remediation task, the remediation task being designed to address the issue within the data center; and, generating a remediation rule to autonomously perform the remediation task, the remediation rule comprising an information processing rule that is used in performance of an autonomous data center remediation operation, the remediation rule determining under what predefined conditions the autonomous remediation operation may be used to remediate a particular data center issue.
8. The system of claim 7, wherein the instructions executable by the processor are further configured for:
- defining a plurality of remediation modes of operation.
9. The system of claim 8, wherein:
- the plurality of remediation modes of operation comprise a manual remediation mode of operation, a semi-automated remediation mode of operation and an automated remediation mode of operation.
10. The system of claim 8, wherein the instructions executable by the processor are further configured for:
- selecting one of the plurality of remediation modes of operation; and,
- the generating the remediation rule to autonomously perform the remediation task takes into account the one of the plurality of remediation modes of operation.
11. The system of claim 7, wherein the instructions executable by the processor are further configured for:
- identifying a remediation pattern associated with the issue, the remediation pattern comprising a plurality of data center remediation operations that have proven to successfully remediate an associated data center issue.
12. The system of claim 11, wherein the instructions executable by the processor are further configured for:
- determining whether a rule exists for the remediation pattern;
- performing an autonomous remediation action when the rule exists; and,
- adding the remediation task to a remediation queue when the rules does not exist.
13. A non-transitory, computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for:
- monitoring data center assets within a data center, the monitoring using issue input data, the issue input data including telemetry data, historical data and target value data, the telemetry data comprising information corresponding to an operational status of a particular data center asset, the historical data comprising information corresponding to a lifecycle and remediation history of the particular data center asset and the target value data comprising information corresponding to one or more of performance metrics, operating parameters, and replacement or maintenance intervals;
- identifying an issue within the data center based upon the issue input data, the issue being associated with an operational situation associated with a particular component of the data center;
- notifying an administrator of the issue within the data center;
- identifying a remediation task, the remediation task being designed to address the issue within the data center; and,
- generating a remediation rule to autonomously perform the remediation task, the remediation rule comprising an information processing rule that is used in performance of an autonomous data center remediation operation, the remediation rule determining under what predefined conditions the autonomous remediation operation may be used to remediate a particular data center issue.
14. The non-transitory, computer-readable storage medium of claim 13, wherein the computer executable instructions are further configured for:
- defining a plurality of remediation modes of operation.
15. The non-transitory, computer-readable storage medium of claim 14, wherein:
- the plurality of remediation modes of operation comprise a manual remediation mode of operation, a semi-automated remediation mode of operation and an automated remediation mode of operation.
16. The non-transitory, computer-readable storage medium of claim 14, wherein the computer executable instructions are further configured for:
- selecting one of the plurality of remediation modes of operation; and,
- the generating the remediation rule to autonomously perform the remediation task takes into account the one of the plurality of remediation modes of operation.
17. The non-transitory, computer-readable storage medium of claim 13, wherein the computer executable instructions are further configured for:
- identifying a remediation pattern associated with the issue, the remediation pattern comprising a plurality of data center remediation operations that have proven to successfully remediate an associated data center issue.
18. The non-transitory, computer-readable storage medium of claim 17, wherein the computer executable instructions are further configured for:
- determining whether a rule exists for the remediation pattern;
- performing an autonomous remediation action when the rule exists; and,
- adding the remediation task to a remediation queue when the rules does not exist.
19. The non-transitory, computer-readable storage medium of claim 13, wherein:
- the computer executable instructions are deployable to a client system from a server system at a remote location.
20. The non-transitory, computer-readable storage medium of claim 13, wherein:
- the computer executable instructions are provided by a service provider to a user on an on-demand basis.
Type: Application
Filed: Jun 3, 2021
Publication Date: Dec 8, 2022
Applicant: Dell Products L.P. (Round Rock, TX)
Inventors: Carlin Mendonca (Austin, TX), Saurav Shrestha (Round Rock, TX), Jeffrey M. Lairsey (Round Rock, TX), Margaret Patton (Austin, TX)
Application Number: 17/337,508
