Performance data model and content

Performance data is stored in a single, denormalized, repository table named TRON_PERFORMANCE, which you can query to collect performance data.

Each execution of project or job is identified by a global unique ID. You will find the execution starting time in three variations: a full timestamp, a date, and a time. Additional information is provided about the account that initiated the execution and the repository in which the project or job is located.

For each executed project ID, version (modification date), name, and a global, unique execution ID is reported. A single project execution event stores the duration of a project in ms.

Project components are represented by ID, name, class, type, and version. The process event provides the number of steps and the amount of processed records.

For port events, the ID, name, class, type and the amount of input or output blocks and records are reported.

For each job, the ID, the version (modification date), and the name is reported. A single job execution event stores the duration of a job in ms. The components (projects) of a job are represented by their ID, class, and version.

The performance log is based on events. For each event, the starting time (in three variations: a full timestamp, a date, and a time) and the duration (in ms) is stored. The description of an event is made up by a class, a name, and a text. Some events include a result (such as succeeded or failed). Also included is information about the engine that reported an event.

Reported events include: