# US 2016/0254969 A1 · Service metric analysis from structured logging schema of usage data

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2016/0254969 A1
- Document ID: US20160254969A1
- Status: Published application
- Kind: A1
- Application number: 15/153,738
- Filed: 2016-05-13
- Published: 2016-09-01
- Earliest claimed: 2014-02-26
- Assignees: Microsoft Technology Licensing, LLC
- Applicants: Microsoft Technology Licensing, LLC
- Inventors: Aravind Ranganathan; Sanghmitra Gite
- Web page: https://patentgrep.com/patent/US20160254969A1

## CPC

- G06F 11/079: {Root cause analysis, i.e. error or fault diagnosis (in a hardware test environment G06F11/22; in a software test environment G06F11/36)}
- G06F 11/008: {Reliability or availability analysis}
- G06F 11/0709: {in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems}
- G06F 11/0751: {Error or fault detection not based on redundancy (power supply failures G06F1/30; network fault management H04L41/06)}
- G06F 11/0766: {Error or fault reporting or storing}
- G06F 11/0778: {Dumping, i.e. gathering error/state information after a fault for later diagnosis}
- G06F 11/0787: {Storage of error reports, e.g. persistent data storage, storage using memory protection}
- G06F 11/3006: {where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems (multiprogramming arrangements G06F9/46; allocation of resources G06F9/50)}
- G06F 11/3419: {by assessing time}
- G06F 11/3466: {Performance evaluation by tracing or monitoring}
- H04L 43/04: Processing captured monitoring data, e.g. for logfile generation
- H04L 43/0823: Errors, e.g. transmission errors
- G06F 11/0772: {Means for error signaling, e.g. using interrupts, exception flags, dedicated error registers}
- G06F 2201/875: Monitoring of systems including the internet
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Technologies are generally described to provide a passive monitoring system employing a logging schema to track usage data in order to analyze performance and reliability of a service. The logging schema may be configured to track user requests as each request is received and processed at individual subsystems of the collaborative service. A logging entry may be created at a data store of the service, where the logging entry includes a subsystem name, an operation performed by the subsystem to fulfill the request, and start and end times of the operation. The logging schema may also detect errors fulfilling the requests, and may classify detected errors into a bucket, where each bucket denotes a failure scenario. Reliability of the service may be calculated based on analysis of the buckets to compute error rates. Reports may be generated to enable continuous monitoring of a performance and reliability of the system.

## Claims

### Claim 1

A method executed at least in part in a computing device to provide a passive monitoring system employing a logging schema to track requests at a service, the method comprising:
detecting a request received by the service from a user;
creating a logging entry for the request at a data store associated with the service;
in response to a determination that the request is not fulfilled, detecting an error in processing the request at the service;
recording the detected error with the logging entry for the request;
determining an error type of the detected error;
classifying the detected error into an error bucket by:
classifying the detected error into a pre-existing error bucket based on the error type; else
in response to a determination that the error type is unique from prior detected errors, create a new error bucket and classify the detected error into the new error bucket;
providing an alert to the user if a number of detected errors exceeds a predefined threshold value; and
determining a reliability of the service based on a percentage of success buckets and error buckets, wherein synthetic requests are distinguished from real user requests and synthetic request data is removed to provide an accurate determination of the reliability of the service.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
identifying a subsystem of the service receiving the request;
identifying an operation performed by the subsystem to fulfill the request; and
identifying a start time and an end time for the operation performed to fulfill the request.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
including the subsystem, the operation, the start time and the end time for the operation performed to fulfill request with the logging entry at the data store.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
recording an error description for the detected error with the logging entry at the data store.

### Claim 5 (depends on 4)

The method of claim 4, further comprising:
mapping an internal error code to the error description to provide a user friendly error description within an error message provided to the user.

### Claim 6 (depends on 5)

The method of claim 5, further comprising:
localizing the error message such that for a same internal error code, a different error message is generated based on user localization.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
in response to a determination that the request is fulfilled, classifying the request as a success in a success bucket.

### Claim 8 (depends on 1)

The method of claim 1, wherein providing the alert to the user if the number of detected errors exceeds the predefined threshold value further comprises:
recognizing repeatedly detected errors of a same error type such that a same alert is not provided multiple times to the user for the same error type.

### Claim 9 (depends on 1)

The method of claim 1, further comprising:
providing a troubleshooting message to the user to address the detected error.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
providing healing scripts to resolve the detected error at the service.

### Claim 11 (depends on 1)

The method of claim 1, further comprising:
generating a report including the determined reliability of one or more of: the service, one or more features, and one or more subsystems of the service.

### Claim 12

A computing device to provide a passive monitoring system employing a logging schema to track requests at a service, the computing device comprising:
a memory;
a processor coupled to the memory, the processor executing a logging application, wherein the logging application is configured to:
detect a request received by the service from a user;
create a logging entry for the request at a data store associated with the service;
determine whether the request is fulfilled by the service;
in response to a determination that the request is fulfilled, classify the request as a success in a success bucket; and
in response to a determination that the request is not fulfilled, classify the request as a detected error in one of a pre-existing error bucket and a newly created error bucket based on an error type of the detected error;
provide at least one of an alert to the user, a troubleshooting message to the user, and a healing script to the service, wherein the alert, the troubleshooting message, and healing script are associated with the detected error; and
determine a reliability of the service based on a percentage of success buckets and error buckets, wherein synthetic requests are distinguished from real user requests and synthetic request data is removed to provide an accurate determination of the reliability of the service.

### Claim 13 (depends on 12)

The computing device of claim 12, wherein the success bucket denotes a success scenario and the error bucket denotes a failure scenario.

### Claim 14 (depends on 12)

The computing device of claim 12, wherein the request is one or more of: initiating an application, opening a document, initiating a conversation, interacting with a document or application, and retrieving data associated with an application.

### Claim 15 (depends on 12)

The computing device of claim 12, wherein the logging application is further configured to:
record an error description for the detected error with the logging entry at the data store, wherein the error description includes an internal error code, a subsystem of the service where the detected error occurred, and the error type.

### Claim 16 (depends on 15)

The computing device of claim 15, wherein the error type includes a locale agnostic string to categorize the error type of the detected error for the request and an associated operation at the subsystem of the service where the detected error occurred.

### Claim 17 (depends on 12)

The computing device of claim 12, wherein the logging application is configured to:
generate a report based on a determined reliability and performance of the service, wherein the report includes at least one of an analysis of a performance of the service and raw data for one or more detected errors associated with the service.

### Claim 18

A method executed at least in part in a computing device to provide a passive monitoring system employing a logging schema to track requests at a service, the instructions comprising:
detecting a request received by the service from a user;
creating a logging entry for the request at a data store associated with the service;
determining whether the request is fulfilled by the service;
if the request is fulfilled, classifying the request as a success in a success bucket;
if the request is not fulfilled, classifying the request as a detected error in an error bucket by one of:
classifying the detected error into a pre-existing error bucket based on an error type; else
in response to a determination that the error type is unique from prior detected errors, creating a new error bucket and classify the detected error into the new error bucket;
providing at least one of an alert to the user, a troubleshooting message to the user, and a healing script to the service, wherein the alert, the troubleshooting message, and healing script are associated with the detected error; and
determining a reliability of the service based on a percentage of success buckets and error buckets, wherein synthetic requests are distinguished from real user requests and synthetic request data is removed to provide an accurate determination of the reliability of the service.

### Claim 19 (depends on 18)

The computer-readable memory device of claim 18, wherein the instructions further comprise:
employing a bug tracking component to continuously examining one or more of the error buckets to detect a bug;
automatically repairing a detected bug; and
providing another alert to the user indicate a presence of the detected bug.

### Claim 20 (depends on 19)

The computer-readable memory device of claim 19, wherein the instructions include:
enabling an administrator of the service to customize the logging schema to define one or more subsystems to monitor, a monitoring frequency, and a type of data to be monitored.
