Method and system for generating a common trace data format

• US 7,979,850 B2
• Filed: 09/29/2006
• Issued: 07/12/2011
• Est. Priority Date: 09/29/2006
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP AG (SAP SE)
• Inventors: Dobtchev, Hristo I., Ivanov, Ventsislav I.
• Primary Examiner(s): Puente; Emerson C
• Assistant Examiner(s): PATEL, HIREN P
• Application Number:
  US11/529,980
• Publication Number:
  US 20080127110A1
• Time in Patent Office: 1,747 Days
• Field of Search: 717/128, 714/45
• US Class Current: 717/128
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/3495 for systems

Abstract

A method for generating a common trace data format is disclosed. In one embodiment, the method includes generating trace data at a provider, identifying a format of the trace data, comparing the format of the trace data with a common format to determine if the format is in compliance with the common format, and modifying the format to comply with the common format, if the format is not in compliance with the common format.

Claims

1. A method comprising:

identifying a first trace format of a first trace data received from a first trace data provider and associated with a first programming engine that is associated with first trace activities at a first computer system, wherein the first trace format is compatible with a common trace data format, wherein identifying the first trace format includes detecting first correlation objects assigned by the first programming engine to first trace entities associated with the first trace activities to determine whether one or more of the first trace entities are compatible or incompatible with the common trace data format;

identifying a second trace format of a second trace data received from a second trace data provider and associated with a second programming engine that is associated with second trace activities at a second computer system, wherein the second trace format is incompatible with the common trace data format, wherein identifying the second trace format includes detecting second correlation objects assigned by the second programming engine to second trace entities associated with the second trace activities to determine whether one or more of the second trace entities are compatible or incompatible with the common trace data format, wherein the second trace data and the second programming engine are incompatible with and independent of the first trace data and the first programming engine, respectively, wherein the common trace data format comprises a trace format that is designated as the common trace data format, the trace format including a common performance trace (CPT) format, wherein the (CPT) format includes a common interface model (CIM)-compliant format and provides the common trace data format defining a type of data that is needed to analyze performance; and

modifying the second trace data by converting the second trace format to the common trace data format, wherein modifying includes converting one or more incompatible second trace entities of the second trace format into one or more compatible common trace entities, removing one or more incompatible second trace entities, or adding one or more compatible common trace entities to the second trace entities.

2. The method of claim 1, further comprising importing, via an import module, the second trace data having the incompatible second trace format from the second trace data provider into a file system for temporary storage prior to the modification.

3. The method of claim 1, further comprising transporting the modified second trace data having the converted second trace format to a database having the first trace data.

4. The method of claim 1, wherein the common trace data format comprises a trace data format that is designated as the common trace data format, the trace data format including a common performance trace (CPT) format.

5. The method of claim 1, wherein modifying further comprises preserving one or more compatible second trace entities of the second trace format.

6. The method of claim 1, wherein the first and second trace entities comprise one or more of an origin file, a metric file, a correlator file, a metadata file, a record correlator file, and a record file.

7. The method of claim 1, wherein the first programming engine comprises a Java 2 Enterprise Edition (J2EE) engine, and the second programming engine comprises an Advanced Business Application Programming (ABAP) engine.

8. A system comprising:

a computer system having a processor coupled with a storage medium and a database, the computer system having an application server employing a trace manager to;

identify a first trace format of a first trace data received from a first trace data provider and associated with a first programming engine that is associated with first trace activities at a first computer system, wherein the first trace format is compatible with a common trace data format, wherein identifying the first trace format includes detecting first correlation objects assigned by the first programming engine to first trace entities associated with the first trace activities to determine whether one or more of the first trace entities are compatible or incompatible with the common trace data format;

identify a second trace format of a second trace data received from a second trace data provider and associated with a second programming engine that is associated with second trace activities at a second computer system, wherein the second trace format is incompatible with the common trace data format, wherein identifying the second trace format includes detecting second correlation objects assigned by the second programming engine to second trace entities associated with the second trace activities to determine whether one or more of the second trace entities are compatible or incompatible with the common trace data format, wherein the second trace data and the second programming engine are incompatible with and independent of the first trace data and the first programming engine, respectively, wherein the common trace data format comprises a trace format that is designated as the common trace data format, the trace format including a common performance trace (CPT) format, wherein the (CPT) format includes a common interface model (CIM)-compliant format and provides the common trace data format defining a type of data that is needed to analyze performance; and

modify the second trace data by converting the second trace format to the common trace data format, wherein modifying includes converting one or more incompatible second trace entities of the second trace format into one or more compatible common trace entities, removing one or more incompatible second trace entities, or adding one or more compatible common trace entities to the second trace entities.

9. The system of claim 8, wherein the trace manager further comprises an import module to import, from the second trace provider, the second trace data having the incompatible second trace format into a file system for temporary storage prior to the modification.

10. The system of claim 9, wherein the trace module is further to transport the modified trace data having the converted second trace format to a database having the first trace data.

11. The system of claim 8, wherein the common trace data format comprise comprises a trace data format that is designated as the common trace data format, the trace data format including a common performance trace (CPT).

12. The system of claim 8, wherein the first programming engine comprises a Java 2 Enterprise Edition (J2EE) engine, and wherein the second programming engine comprises an Advanced Business Application Programming (ABAP) engine.

13. The system of claim 8, wherein modifying further comprises preserving one or more compatible second trace entities of the second format.

14. The system of claim 8, wherein the first and second trace entities comprise one or more of an origin file, a metric file, a correlator file, a metadata file, a record correlator file, and a record file.

15. An article of manufacture comprising a machine-accessible medium having instructions which, when executed, cause a machine to:

identify a first trace format of a first trace data received from a first trace data provider and associated with a first programming engine that is associated with first trace activities at a first computer system, wherein the first trace format is compatible with a common trace data format, wherein identifying the first trace format includes detecting first correlation objects assigned by the first programming engine to first trace entities associated with the first trace activities to determine whether one or more of the first trace entities are compatible or incompatible with the common trace data format;

identify a second trace format of a second trace data received from a second trace data provider and associated with a second programming engine that is associated with second trace activities at a second computer system, wherein the second trace format is incompatible with the common trace data format, wherein identifying the second trace format includes detecting second correlation objects assigned by the second programming engine to second trace entities associated with the second trace activities to determine whether one or more of the second trace entities are compatible or incompatible with the common trace data format, wherein the second trace data and the second programming engine are incompatible with and independent of the first trace data and the first programming engine, respectively, wherein the common trace data format comprises a trace format that is designated as the common trace data format, the trace format including a common performance trace (CPT) format, wherein the (CPT) format includes a common interface model (CIM)-compliant format and provides the common trace data format defining a type of data that is needed to analyze performance; and

modify the second trace data by converting the second trace format to the common trace data format, wherein modifying includes converting one or more incompatible second trace entities of the second trace format into one or more compatible common trace entities, removing one or more incompatible second trace entities, or adding one or more compatible common trace entities to the second trace entities.

16. The article of manufacture of claim 15, wherein the instructions which, when executed, further cause the machine to import, via an import module, the second trace data having the incompatible second trace format from the second trace data provider into a file system for temporary storage prior to the modification.

17. The article of manufacture of claim 15, wherein the instructions which, when executed, further cause the machine to transport the modified second trace data having the converted second trace format to a database having the first trace data.

18. The article of manufacture of claim 15, wherein modifying further comprises preserving one or more compatible second trace entities of the second trace format.

19. The article of manufacture of claim 15, wherein the first and second trace entities comprise one or more of an origin file, a metric file, a correlator file, a metadata file, a record correlator file, and a record file.

20. The article of manufacture of claim 15, wherein the first programming engine comprises a Java 2 Enterprise Edition (J2EE) engine, and the second programming engine comprises an Advanced Business Application Programming (ABAP) engine.