Abstract: This disclosure is directed to generating one or more presence-event notifications at one or more user devices associated with a user, and transmitting those presence-event notifications to one or more presence server(s). At the presence server(s) a stream of presence-event notifications may be filtered according to any number of predefined criteria, and then the presence-event notifications that have filtered through may be applied to presence plug-ins to generate presence information associated with user(s) for whom presence-event notifications were received. The presence-event notifications may be provided as a stream of presence information to one or more consumers of presence information and/or stored in a presence datastore. A consumer of presence information, such as a service provider, may request presence information associated with one or more users.

Abstract: This disclosure is directed to generating one or more presence-event notifications at one or more user devices associated with a user, and transmitting those presence-event notifications to one or more presence server(s). At the presence server(s) a stream of presence-event notifications may be filtered according to any number of predefined criteria, and then the presence-event notifications that have filtered through may be applied to presence plug-ins to generate presence information associated with user(s) for whom presence-event notifications were received. The presence-event notifications may be provided as a stream of presence information to one or more consumers of presence information and/or stored in a presence datastore. A consumer of presence information, such as a service provider, may request presence information associated with one or more users.

Abstract: This disclosure is directed to generating one or more presence-event notifications at one or more user devices associated with a user, and transmitting those presence-event notifications to one or more presence server(s). At the presence server(s) a stream of presence-event notifications may be filtered according to any number of predefined criteria, and then the presence-event notifications that have filtered through may be applied to presence plug-ins to generate presence information associated with user(s) for whom presence-event notifications were received. The presence-event notifications may be provided as a stream of presence information to one or more consumers of presence information and/or stored in a presence datastore. A consumer of presence information, such as a service provider, may request presence information associated with one or more users.

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 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.

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: Ones of the windows associated with a software process are identified in a screen layout on a local display of a sharer network node. On the sharer network node, an image of the identified windows as they are arranged in the screen layout and free of obscuration by any other windows in the screen layout is generated. The image is transmitted from the sharer network node to a viewer network node. Also, commands derived from input device events on sharer and viewer network nodes are received. The received commands are processed into a command sequence, which is passed to a shared process executing on the sharer network node. Windows associated with the shared process are presented on the sharer network node in accordance with the received command sequence. An image of the presented windows is generated and transmitted from the sharer network node to the viewer network node.