Service metric analysis from structured logging schema of usage data
First Claim
1. A method to monitor request errors at a service, the method comprising:
- detecting a request received by the service;
creating a logging entry for the request, wherein creating the logging entry for the request comprises for each subsystem to process the request, recording one or more of;
a subsystem name,a sub-operation name,an entry and an exit time from the subsystem,a start time and an end time for the sub-operation performed by the subsystem to fulfill the request,user locale information for the request, orerror information associated with processing of the request at the subsystem;
if the request is fulfilled by the service, logging an entry in a success bucket;
if an error is detected 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 a new error bucket if the detected error is unique from prior detected errors;
classifying the detected error into a pre-existing error bucket if the error is known;
andgenerating a report on a reliability of the service based on the success bucket and one or more error buckets.
1 Assignment
0 Petitions
Accused Products
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 nay 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.
-
Citations
20 Claims
-
1. A method to monitor request errors at a service, the method comprising:
-
detecting a request received by the service; creating a logging entry for the request, wherein creating the logging entry for the request comprises for each subsystem to process the request, recording one or more of; a subsystem name, a sub-operation name, an entry and an exit time from the subsystem, a start time and an end time for the sub-operation performed by the subsystem to fulfill the request, user locale information for the request, or error information associated with processing of the request at the subsystem; if the request is fulfilled by the service, logging an entry in a success bucket; if an error is detected 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 a new error bucket if the detected error is unique from prior detected errors; classifying the detected error into a pre-existing error bucket if the error is known; and generating a report on a reliability of the service based on the success bucket and one or more error buckets. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A server to monitor request errors at a service, the server comprising:
-
a memory; a processor coupled to the memory, the processor executing an application, wherein the application is configured to; detect a request received by the service; create a logging entry for the request; if the request is fulfilled by the service, log an entry in a success bucket; if an error is detected in processing the request at the service; record the detected error with the logging entry for the request; determine an error type of the detected error; classify the detected error into a new error bucket if the detected error is unique from prior detected errors; classify the detected error into a pre-existing error bucket if the error is known; and generate a report on a reliability of the service based on the success bucket and one or more error buckets, wherein the report includes one or more of;
a list of subsystems experiencing least usage, a list of subsystems experiencing most usage, an observation about a nature of user interaction with the service, or a pattern of operations performed by users under different scenarios. - View Dependent Claims (11, 12, 13, 14, 15, 16, 17)
-
-
18. A method to provide monitoring of errors to one or more cloud-based services, the method comprising:
-
detecting a request received by the one or more cloud-based services; creating a logging entry for the request; if the request is fulfilled by the one or more cloud-based services, logging an entry in a success bucket; if an error is detected in processing the request at the one or more cloud-based services; recording the detected error with the logging entry for the request; determining an error type of the detected error; classifying the detected error into a new error bucket if the detected error is unique from prior detected errors; classifying the detected error into a pre-existing error bucket if the error is known; classifying the detected error independent of usage data localization; and anonymizing user information for protection of user privacy; and generating a report on a performance and a reliability of the one or more cloud-based services based on an analysis of the processing of the request. - View Dependent Claims (19, 20)
-
Specification