TELEMETRY SYSTEM FOR A CLOUD SYNCHRONIZATION SYSTEM

• US 20130268491A1
• Filed: 04/05/2012
• Published: 10/10/2013
• Est. Priority Date: 04/05/2012
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Chung, Richard, Lueder, Roger
• Granted Patent: US 10,089,323 B2
• Time in Patent Office: Days
• US Class Current: 707/634
• CPC Class Codes: G06F 11/1662 the resynchronized component or unit being a persistent storage device re-synchronization of failed mirror storage G06F11/2082; rebuild or reconstruction of parity RAID storage G06F11/1008
• CPC Class Codes: G06F 11/2094 Redundant storage or storage space G06F11/2056 takes precedence
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems

Abstract

In one embodiment, a telemetry system may track a cloud synchronization system to improve performance. A service proxy 114 may receive a matching file metadata set 304 for a matching file 134 stored in a cloud user account 132 of a cloud synchronization system. The service proxy 114 may execute a synchronization verification of the matching file metadata set 304 to a local file 112 stored in a client device 110. The service proxy 114 may create a telemetry report 400 describing a synchronization error 412 as determined by the synchronization verification.

Claims

1. A machine-implemented method, comprising:

receiving a matching file metadata set for a matching file stored in a cloud user account of a cloud synchronization system;

executing a synchronization verification of the matching file metadata set to a local file stored in a client device; and

creating a telemetry report describing a synchronization error as determined by the synchronization verification.

2. The method of claim 1, further comprising:

sending the telemetry report to a telemetry server.

3. The method of claim 1, further comprising:

determining from the matching file metadata set an event time for the synchronization error.

4. The method of claim 1, further comprising:

receiving the matching file metadata set from at least one of a cloud server and an associated user device.

5. The method of claim 1, further comprising:

executing the synchronization verification upon completion of a synchronization between the local file and the matching file.

6. The method of claim 1, further comprising:

creating a local file metadata set to compare with the matching file metadata set for the synchronization verification.

7. The method of claim 1, further comprising:

performing a resynchronization of the local file to the matching file.

8. The method of claim 1, further comprising:

receiving an assertion failure during a synchronization of the local file and the matching file for the telemetry report.

9. The method of claim 1, further comprising:

recognizing a synchronization stall during a synchronization of the local file and the matching file for the telemetry report.

10. The method of claim 1, further comprising:

tracking a synchronization of the local file and the matching file to record a synchronization performance metric for the telemetry report.

11. A tangible machine-readable medium having a set of instructions detailing a method stored thereon that when executed by one or more processors cause the one or more processors to perform the method, the method comprising:

receiving from a client device a telemetry report having a telemetry data set compiled at the client device describing a cloud service;

creating a review report based in part on the telemetry data set ; and

sending the review report to the client device.

12. The tangible machine-readable medium of claim 11, wherein the method further comprises:

comparing a synchronization error in the telemetry report to a known error database to find a matching error.

13. The tangible machine-readable medium of claim 12, wherein the method further comprises:

selecting an error patch to the review report based on the matching error.

14. The tangible machine-readable medium of claim 11, wherein the method further comprises:

collecting a service-wide performance record for the review report.

15. The tangible machine-readable medium of claim 11, wherein the method further comprises:

associating the telemetry data set with at least one of a user demographic data set for the cloud user account and a device profile for the client device.

16. The tangible machine-readable medium of claim 11, wherein the method further comprises:

collecting an aggregate user performance record for the review report.

17. The tangible machine-readable medium of claim 11, wherein the method further comprises:

collecting an individual user performance record for the review report.

18. The tangible machine-readable medium of claim 17, wherein the method further comprises:

creating a user customizable timeline based on the individual user performance record.

19. A client device, comprising:

a data storage that stores a local file synchronized with a matching file in a cloud user account of a cloud synchronization system;

a network interface that receives a matching file metadata set for the matching file from a cloud server; and

a processor that executes a synchronization verification of the matching file metadata set to the local file and creates a telemetry report describing a synchronization error as determined by the synchronization verification.

20. The client device of claim 19, wherein the telemetry report has at least one of assertion failure data, synchronization stall data, and a synchronization performance metric.