Abstract: Methods, systems, and computer-readable media are disclosed for monitoring a distributed application. A particular method identifies a plurality of components of a distributed application. The method also identifies a specific technology associated with a particular component and attaches a technology specific interceptor to the particular component based on the identified specific technology. The method includes intercepting messages that are sent by or received by the particular component using the technology specific interceptor. At least one potential work item is generated based on the intercepted messages. The method includes determining whether to schedule the at least one potential work item for execution based on a predicted impact of the at least one work potential item on performance of the distributed application.

Abstract: The described unified service management system provides a unified console to perform functions of individual management specialists. A unified console facilitates an administrator to perform the complex tasks that were performed by the individual management specialists. The unified console provides a “wizard” based approach to the administrator to design all aspects of the complex tasks including placement of components or computing devices, deciding on policies of the components or computing devices, deciding on health policies of components or computing devices, fixing data protection policies of components or computing devices, etc.

Abstract: Technologies are described herein for applying type projection queries to instance space graphs. Through the utilization of the technologies and concepts presented herein, a type projection may be used to describe the hierarchy of instance types connected by relationships within an instance space graph. A type projection query based on the type projection may be dynamically generated to query instances and relationships within the instance store. Filter criteria for the query can be expressed using a path notation. Results from of the type projection query may be provided as graphs of instances and relationships which are subgraphs of the queried instance space graph. Programmatic traversal of the resultant subgraph can navigate to each instance node within the result space.

Abstract: Technologies are described herein for cloud monitoring federations that can include cloud monitoring services (CMS) that collect monitoring information from point of presence (POP) agents. The cloud monitoring POPs may be located in the cloud, on client machines, embedded within cloud applications, or wherever they can obtain visibility into managed entities associated with the cloud. Management systems, acting as cloud monitoring clients (CMC), may interface with the CMS to obtain a complete view of services and application used by their enterprise including those that operate outside of the enterprise premises as part of a cloud or outside network. The publishing by POPs and consumption by CMCs of management information across components within the enterprise and out in the cloud may be supported by managing roles, responsibilities, scopes, security boundaries, authenticity of information, service level agreements, and other aspects of cloud monitoring operations.

Abstract: Computer services and other computer entities may be monitored and evaluated by using a model that defines the services and relationships between the services. The model may be used during discovery for finding entities and creating instances of the entities and instances of the relationships between entities. After discovery, data may be collected and stored in a database by monitoring or instrumenting the entity. Analysis of the data may include tracking performance and monitoring the health of a service or other entity. The relationships may be used to graphically display various entities in many useful manners, including graphical representations of the health of various entities.

Abstract: Technologies are described herein for cloud monitoring federations that can include cloud monitoring services (CMS) that collect monitoring information from point of presence (POP) agents. The cloud monitoring POPs may be located in the cloud, on client machines, embedded within cloud applications, or wherever they can obtain visibility into managed entities associated with the cloud. Management systems, acting as cloud monitoring clients (CMC), may interface with the CMS to obtain a complete view of services and application used by their enterprise including those that operate outside of the enterprise premises as part of a cloud or outside network. The publishing by POPs and consumption by CMCs of management information across components within the enterprise and out in the cloud may be supported by managing roles, responsibilities, scopes, security boundaries, authenticity of information, service level agreements, and other aspects of cloud monitoring operations.

Abstract: Model-based event processing is described. In an embodiment, a model of a system includes managed entities and relationships between the managed entities. Events associated with the managed entities are identified and determined to be correlated if the managed entities with which the events are associated have a relationship according to the model.

Abstract: One exemplary embodiment uses templates that define certain features of a given service type, wherein the features are common to all services of that service type. The template can be configured by a user to obtain a service definition for the given service. The service definition is passed to a programmability layer and provides enough information that the programmability layer can construct the various monitors, rules, classes and tasks required to monitor the given service without further customization by the user. In one embodiment, the user can also customize the service definition, a desired, in order to obtain additional monitoring.

Abstract: Model-based system monitoring includes accessing a model of a system that includes multiple components and executing a monitoring policy to monitor performance of the system. A notification of a problem is received from a first component. A determination is made regarding the cause of the problem. The determination is made, at least in part, based on the model of the system. At least one component associated with the cause of the problem is then identified.

Abstract: Techniques are described herein that are capable of generating a compliance data model for information technology (IT) control. The compliance data model is capable of capturing data from technologies (e.g., software programs, file systems, etc.) and/or developers of those technologies for determining compliance of the technologies with regulations. The compliance data model may be used to automate generation of artifacts. Each artifact is machine-readable code that includes instructions regarding how to implement a control. A control is a software container that is associated with one or more elements, such as a control objective, a control activity, a control activity test, etc. The artifacts are usable by management systems to obtain data regarding installed technologies, settings of the technologies, configurations of the technologies, events that are being utilized by the technologies, etc.

Abstract: Techniques are described herein that are capable of monitoring activity with respect to a distributed application. A server system includes logical tiers, each including processing system(s) configured to process messages in accordance with a respective protocol (e.g., an ASP.net® protocol, WCF protocol, SQL protocol, etc.). When a user initiates an activity with respect to a distributed application, hops are performed between the logical tiers and/or between components of the distributed application to complete the requested activity. A hop is a transfer of a message or a procedure call from one processing system to another processing system. A common identifier may be assigned to each of the hops that are performed with regard to the activity. If a failure occurs with respect to the activity, the common identifier may be used to gather information regarding the hops. For instance, the information may be used to determine a source of the failure.

Abstract: Technologies are described herein for applying type projection queries to instance space graphs. Through the utilization of the technologies and concepts presented herein, a type projection may be used to describe the hierarchy of instance types connected by relationships within an instance space graph. A type projection query based on the type projection may be dynamically generated to query instances and relationships within the instance store. Filter criteria for the query can be expressed using a path notation. Results from of the type projection query may be provided as graphs of instances and relationships which are subgraphs of the queried instance space graph. Programmatic traversal of the resultant subgraph can navigate to each instance node within the result space.

Abstract: A change order to be executed at a scheduled time as part of a change plan is created, wherein the change order to define a change to an Information Technology (IT) environment. The change order is validated against validation rules to simulate execution of the change order at the scheduled time wherein other change orders scheduled to execute before the execution of the change order are included in the simulation. Breaks in change orders scheduled to execute after the change order are detected. Side effects caused by execution of the change order are determined. The results of validating the change order are output.

Abstract: A data synchronization task is received at a console, wherein the data synchronization task is associated with information technology management. A configuration document is configured using the data synchronization task, wherein the configuration document defines data synchronization through declarations. A linking framework is configured based on the configuration document. Data is synchronized from a first and second source to a target as defined by the configuration document.

Abstract: A dashboard can be composed of pre-defined data provider, presentation, and processor components. The data provider component acquires data from a source, and the presentation component visualizes data. The processor component enhances the data for actionable usability by various means (e.g., data aggregation, filtering, projections, wave shaping, anomaly detection, and combination . . . ).

Abstract: A data synchronization task is received at a console, wherein the data synchronization task is associated with information technology management. A configuration document is configured using the data synchronization task, wherein the configuration document defines data synchronization through declarations. A linking framework is configured based on the configuration document. Data is synchronized from a first and second source to a target as defined by the configuration document.

Abstract: Techniques are described herein that are capable of monitoring activity with respect to a distributed application. A server system includes logical tiers, each including processing system(s) configured to process messages in accordance with a respective protocol (e.g., an ASP.net® protocol, WCF protocol, SQL protocol, etc.). When a user initiates an activity with respect to a distributed application, hops are performed between the logical tiers and/or between components of the distributed application to complete the requested activity. A hop is a transfer of a message or a procedure call from one processing system to another processing system. A common identifier may be assigned to each of the hops that are performed with regard to the activity. If a failure occurs with respect to the activity, the common identifier may be used to gather information regarding the hops. For instance, the information may be used to determine a source of the failure.

Abstract: Technologies are described herein for cloud monitoring federations that can include cloud monitoring services (CMS) that collect monitoring information from point of presence (POP) agents. The cloud monitoring POPs may be located in the cloud, on client machines, embedded within cloud applications, or wherever they can obtain visibility into managed entities associated with the cloud. Management systems, acting as cloud monitoring clients (CMC), may interface with the CMS to obtain a complete view of services and application used by their enterprise including those that operate outside of the enterprise premises as part of a cloud or outside network. The publishing by POPs and consumption by CMCs of management information across components within the enterprise and out in the cloud may be supported by managing roles, responsibilities, scopes, security boundaries, authenticity of information, service level agreements, and other aspects of cloud monitoring operations.

Abstract: Described are software stacks for accepting and implementing portable packages containing encodings of processes. The packages are portable and distinct from the technology stacks. The packages may be in the form of declarative code for configuring the technology stacks and can be plugged into the technology stacks to allow the technology stack to play the packages, thereby automating the processes encoded by the packages. The technology stacks have components that are declaratively configurable such that they can provide their functionality autonomously and yet can also, as a unit, in performing their respective functions, cooperatively perform the processes encoded by the packages.

Abstract: Technologies are described herein for applying type projection queries to instance space graphs. Through the utilization of the technologies and concepts presented herein, a type projection may be used to describe the hierarchy of instance types connected by relationships within an instance space graph. A type projection query based on the type projection may be dynamically generated to query instances and relationships within the instance store. Filter criteria for the query can be expressed using a path notation. Results from of the type projection query may be provided as graphs of instances and relationships which are subgraphs of the queried instance space graph. Programmatic traversal of the resultant subgraph can navigate to each instance node within the result space.