Techniques for generating diagnostic identifiers to trace events and identifying related diagnostic information

• US 9,529,657 B2
• Filed: 09/18/2014
• Issued: 12/27/2016
• Est. Priority Date: 02/07/2014
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Jan, Wai, Cook, Gregory, Irvin, R. Bruce, Loo, Kaj van de
• Primary Examiner(s): Iqbal, Nadeem
• Application Number:
  US14/490,619
• Publication Number:
  US 20150227405A1
• Time in Patent Office: 831 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0778 Dumping, i.e. gathering error/state information after a fault for later diagnosis
• CPC Class Codes: 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

Abstract

Techniques are described for determining diagnostic information (e.g., a diagnostic identifier) for one or more events related to operations performed in a cloud computer system. A diagnostic identifier may be generated based on diagnostic data corresponding to one or more attributes about an event. A computing operation may be performed to generate a code (e.g., a hash code) for each attribute in the diagnostic data. The generated code(s) may be combined to form a diagnostic identifier to identify the diagnostic data. A comparison may be performed by comparing each code in one diagnostic identifier to a code in another diagnostic identifier corresponding to an attribute for which the codes were generated. A measure of a match between the two identifiers may be determined using a result of the comparison. The measure of the match may enable tracing and analysis of one or more events occurring in the cloud computer system.

Claims

1. A method comprising:

receiving, by a computer system, diagnostic data related to processing a request for a service provided by an enterprise computer system, wherein the request is processed by the computer system;

locating, by the computer system, first diagnostic data in the diagnostic data, wherein the first diagnostic data corresponds to a first event that occurs during processing of the request;

identifying, by the computer system, attribute data for each attribute of a plurality of attributes corresponding to an operation identified in the first diagnostic data, wherein the attribute data identifies an executed function and operation information about the operation;

generating, by the computer system, a plurality of codes, wherein each code of the plurality of codes is generated using the attribute data corresponding to a different attribute of the plurality of attributes;

determining, by the computer system, a first diagnostic identifier for the first event by combining the plurality of generated codes;

determining, by the computer system, a second diagnostic identifier for a second event that occurs during processing of the request, wherein the second diagnostic identifier is determined based on second diagnostic data in the diagnostic data corresponding to the second event; and

computing, by the computer system, a value that indicates a measure of a match between the first diagnostic identifier and the second diagnostic identifier, wherein the value is computed by comparing the first diagnostic identifier to the second diagnostic identifier.

2. The method of claim 1, wherein the computer system is a cloud computer system that is located at a first geographical location, and wherein the enterprise computer system is located at a second geographical location that is different from the first geographical location of the computer system.

3. The method of claim 1, wherein the diagnostic data includes stack trace data about one or more events, and wherein the first diagnostic data corresponds to a first call frame for the first event in the stack trace data, and wherein the second diagnostic data corresponds to a second call frame for the second event in the stack trace data.

4. The method of claim 1, further comprising:

receiving, from a mobile computing device, a request to allocate a computing resource for processing of a request for one or more services provided by the enterprise computer system;

allocating the computing resource in the computer system, wherein processing for the request for the service is performed using the allocated computing resource; and

detecting the first event during the processing of the request for the service.

5. The method of claim 1, wherein the first event corresponds to an error event that occurs during the operation identified in the first diagnostic data.

6. The method of claim 1, wherein the attribute data further identifies class information for a class used by the executed function, package information for a package including the class, and component information for a component including the package.

7. The method of claim 1, wherein the operation information about the operation identifies an operation code identifying the operation and a line number in the executed function.

8. The method of claim 1, wherein each code of the plurality of codes is generated using a hash operation.

9. The method of claim 1, wherein the attribute data includes first attribute data, the first attribute data corresponding to a first attribute of the plurality of attributes, and wherein the first attribute data includes a value for the first attribute corresponding to the operation identified in first diagnostic data.

10. The method of claim 9, wherein generating the code using the first attribute data includes performing a hash operation using the value in the first attribute data.

11. The method of claim 1, further comprising:

determining that the first diagnostic data is related to the second diagnostic data when the computed value satisfies a comparison threshold.

12. The method of claim 1, wherein comparing the first diagnostic identifier to the second diagnostic identifier includes comparing each generated code of the plurality of codes combined for determining the first diagnostic identifier to a corresponding generated code in the second diagnostic identifier.

13. The method of claim 12, wherein the value indicating the measure of the match is computed using a ratio of generated codes that match based on comparing the first diagnostic identifier to the second diagnostic identifier.

14. The method of claim 12, wherein the value indicating the measure of the match is computed based on an amount of the plurality of generated codes that match based on comparing the first diagnostic identifier to the second diagnostic identifier.

15. A computer system comprising:

one or more processors; and

one or more memory devices coupled to the one or more processors, the one or more memory devices containing instructions that, when executed on the one or more processors, cause the one or more processors to;

receive, from a mobile computing device using a first communication protocol, a request for a service, wherein the service is provided by an enterprise computer system;

convert the request for the service, wherein the request is converted to be sent to the enterprise computer system, and wherein the request is converted from a first format of the first communication protocol to a second format of a second communication protocol;

receive diagnostic data from a diagnostics data store, wherein the diagnostic data is related to processing the request to be sent to the enterprise computer system;

locate first diagnostic data in the diagnostic data, wherein the first diagnostic data corresponds to a first event that occurs during processing of the request;

identify attribute data for each attribute of a plurality of attributes corresponding to an operation identified in the first diagnostic data, wherein the attribute data identifies an executed function and operation information about the operation;

generate a plurality of codes, wherein each code of the plurality of codes is generated using the attribute data corresponding to a different attribute of the plurality of attributes;

determine a first diagnostic identifier for the first event by combining the plurality of generated codes;

determine a second diagnostic identifier for a second event that occurs during processing of the request, wherein the second diagnostic identifier is determined based on second diagnostic data in the diagnostic data corresponding to the second event; and

compute a value that indicates a measure of a match between the first diagnostic identifier and the second diagnostic identifier, wherein the value is computed by comparing the first diagnostic identifier to the second diagnostic identifier.

16. The computer system of claim 15, wherein the diagnostic data includes a stack trace data about one or more events, wherein the first diagnostic data corresponds to a first call frame for the first event in the stack trace data, and wherein the second diagnostic data corresponds to a second call frame for the second event in the stack trace data.

17. The computer system of claim 15, wherein the first event corresponds to an error event that occurs during the operation identified in the first diagnostic data.

18. The computer system of claim 17, wherein the instructions, when executed on the one or more processors, further cause the one or more processors to:

receive, from the enterprise computer system via the second communication protocol, a response to the request for the service;

convert the response received from the enterprise computer system using the second communication protocol, wherein the response is converted from the second format of the second communication protocol to the first format of the first communication protocol; and

send the converted response to the mobile computing device.

19. A non-transitory computer-readable memory storing a set of instructions that, when executed by one or more processors, causes the one or more processors to:

receive diagnostic data related to processing a request for a service provided by an enterprise computer system, wherein the request is processed by a computer system;

locate first diagnostic data in the diagnostic data, wherein the first diagnostic data corresponds to a first event that occurs during processing of the request;

identify attribute data for each attribute of a plurality of attributes corresponding to an operation identified in the first diagnostic data, wherein the attribute data identifies an executed function and operation information about the operation;

generate a plurality of codes, wherein each code of the plurality of codes is generated using the attribute data corresponding to a different attribute of the plurality of attributes;

determine a first diagnostic identifier for the first event by combining the plurality of generated codes;

determine a second diagnostic identifier for a second event that occurs during processing of the request, wherein the second diagnostic identifier is determined based on second diagnostic data in the diagnostic data corresponding to the second event; and

compute a value that indicates a measure of a match between the first diagnostic identifier and the second diagnostic identifier, wherein the value is computed by comparing the first diagnostic identifier to the second diagnostic identifier.

20. The non-transitory computer-readable memory of claim 19, wherein comparing the first diagnostic identifier to the second diagnostic identifier includes comparing each generated code of the plurality of codes combined for determining the first diagnostic identifier to a corresponding generated code in the second diagnostic identifier, wherein each generated code of the plurality of codes combined for determining the first diagnostic identifier corresponds to a distinct attribute of the plurality of attributes, and wherein the measure of the match is computed using a ratio of generated codes that match based on comparing the first diagnostic identifier to the second diagnostic identifier.