Microsoft Technology Licensing, LLC

Prasanna Kumar Padmanabhan

Jon Barry Avner

Mihai R Jalobeanu

Charlie Ricafort Chung

David Wang

Wilson Li

Sean Usher

Srinath Gomathinathan Ramasubramanian

Shantanu Uddhav Deshmukh

Gregory C J Chang

Nirav Jasapara

Oleksandr Bublichenko

A resilient incident management system is provided that continues operation when certain outages occur. An RSS feed is utilized to indicate incident-related information despite the certain outages. In an embodiment, the incident management system includes a redundant architecture that comprises a traffic manager and a backup traffic manager. The incident management system receives a client request for incident-related information and determines a priority level or a performance level of end points associated with the request. Based on a status of the traffic manager and the backup traffic manager, as well as based on the priority level or the performance level, the incident management system causes a computer operation to be executed via the redundant architecture to retrieve a response from a producer and generate the RSS feed. In this manner, incident-related information is provided to the client even when the components responsible for providing the incident-related information themselves experience outages.

Incident management engine for an incident management system

A method for backfilling records dropped by a distributed node system during a transfer to an external database includes initially determining whether an attempt to transfer a data record failed or succeeded. In response to determining that the transfer succeeded, the data record is appended at its original location include a first transfer status identifier. In response to determining that the transfer failed, the data record is appended to include a second transfer status identifier and queued copy of the data record is created by copying the data record to a delayed re-try queue. The method further includes verifying that the transfer status identifier of the queued copy is identical to the transfer status identifier of a newest version of the data record within the distributed node system and, responsive to the verification, attempting a subsequent transfer of the queued copy of the data record to the external database.

Mechanism for backfilling records dropped during transfer from distributed node system

A multi-level monitoring system is provided for monitoring multiple performance aspects of a cloud service concurrently in order to generate a full and reliable performance analysis of the cloud service. The multi-level monitoring system may include a set of components for carrying out the performance analysis of the cloud service which may be deployed together to operate externally, internally, or concurrently with the cloud service. The component framework of the multi-level monitoring system may include a main component, a plug-in associated with the main component, a definition database, a log database, and an output database. The main components of an example multi-level monitoring framework may include a probe runner component for probing the cloud service, a monitor component for generating alerts based on probe results, and a responder component for processing the alerts and taking appropriate actions to improve the cloud service performance.

System comprising probe runner, monitor, and responder with associated databases for multi-level monitoring of a cloud service

Growing community of inventors

Bellevue, WA, United States of America

Prasanna Kumar Padmanabhan