Abstract: Monitoring the health of a computer system and suggesting an order of repair when problems within the computer system have been identified. Problem(s) and problem entity(s) within the computer system are identified during monitoring. Relationship(s) of the problem entities with other entities in the computer system are identified. A relationship type for each of the identified relationship(s) is determined. A combination of the identified problem(s), the identified problem entity(s), and the determined relationship type(s) is analyzed to determine an order in which repairs of one or more user-visible entities of the computing system should occur in order to address the identified problem(s). An alert comprising the determined order of the repairs is then presented to a user.

Abstract: Aspects extend to methods, systems, and computer program products for intent-based interactions with cluster resources. One or more computer systems are joined in a computer system cluster to provide defined computing functionality (e.g., storage, compute, network, etc.) to an external system. In one aspect, a data collection intent facilitates collection and aggregation of data to form a health report for one or more components of the computer system cluster. In another aspect, a command intent facilitates implementing a command at one or more components of the computer system cluster. Services span machines of the computer system cluster to abstract lower level aspects of data collection and aggregation and command implementation for higher level aspects of data collection and aggregation and command implementation. Services can be integrated into an operating system to relieve users from having to have operating system knowledge.

Abstract: Aspects extend to methods, systems, and computer program products for intent-based interactions with cluster resources. One or more computer systems are joined in a computer system cluster to provide defined computing functionality (e.g., storage, compute, network, etc.) to an external system. In one aspect, a data collection intent facilitates collection and aggregation of data to form a health report for one or more components of the computer system cluster. In another aspect, a command intent facilitates implementing a command at one or more components of the computer system cluster. Services span machines of the computer system cluster to abstract lower level aspects of data collection and aggregation and command implementation for higher level aspects of data collection and aggregation and command implementation. Services can be integrated into an operating system to relieve users from having to have operating system knowledge.

Abstract: Monitoring the health of a computer system and suggesting an order of repair when problems within the computer system have been identified. Problem(s) and problem entity(s) within the computer system are identified during monitoring. Relationship(s) of the problem entities with other entities in the computer system are identified. A relationship type for each of the identified relationship(s) is determined. A combination of the identified problem(s), the identified problem entity(s), and the determined relationship type(s) is analyzed to determine an order in which repairs of one or more user-visible entities of the computing system should occur in order to address the identified problem(s). An alert comprising the determined order of the repairs is then presented to a user.

Abstract: Monitoring the health of a computer system based on the relationships of entities, and the intelligent presentation of alerts based thereon. A rule-based engine may perform the monitoring and alerting. Problem(s) and problem entity(s) within a computing system are identified during the monitoring. Relationship(s) of the problem entity(s) with other entities in the computer system are then identified. A relationship type for each of the identified relationship(s) is determined. A combination of the identified problem(s), the identified problem entity(s), and the determined relationship type(s) are analyzed to determine root cause(s) of the problem(s). Based on the root cause(s), an alert is presented to a user comprising one or more actions the user can take regarding one or more user-visible entities of the computer system to fix the identified problem(s). The alerts may be fewer in number and more intuitive due to the analysis.