Charts, reports, and dashboards using the DI Operations Mart data
Once you have created and populated your Data Integration Operations Mart with log data, you can use the features of the Pentaho User Console to examine this data and create reports, charts, and dashboards. We provide many pre-built reports, charts, and dashboards that you can modify.
To help understand the contents of the log, see Data Integration Operations Mart.
Logging tables status
The following tables are contained in the PDI Operations Mart:
Transformation log tables
The status values and their descriptions are in the following table:
start
Indicates the transformation was started and retains this status until the transformation ends when no logging interval is set.
end
Transformation ended successfully.
stop
Indicates the user stopped the transformation.
error
Indicates an error occurred when attempting to run the transformation.
running
A transformation is only in this status directly after starting and does not appear without a logging interval.
paused
Indicates the user paused the transformation and does not appear without a logging interval.
Jobs logs tables
The status values and their descriptions are in the following table:
start
Indicates the job was started and retains this status until the job ends, and when no logging interval is set.
end
Job ended successfully.
stop
Indicates the user stopped the job.
error
Indicates an error occurred when attempting to run the job.
running
A job is only in this status directly after starting and does not appear without a logging interval.
paused
Indicates the user paused the job and it does not appear without a logging interval.
Logging dimensions and metrics
These tables identify the various dimensions and metrics that can be used to create new ETL log charts and reports:
Fact table
(fact_execution)
execution_date_tk
A technical key (TK) linking the fact to the date when the transformation/job was executed.
execution_time_tk
A technical key (TK) linking the fact to the time-of-day when the transformation/job was executed.
batch_tk
A technical key (TK) linking the fact to batch information for the transformation/job.
execution_tk
A technical key (TK) linking the fact to execution information about the transformation/job.
executor_tk
A technical key (TK) linking the fact to information about the executor (transformation or job).
parent_executor_tk
A technical key (TK) linking the fact to information about the parent transformation/job).
root_executor_tk
A technical key (TK) linking the fact to information about the root transformation/job.
execution_timestamp
The date and time when the transformation/job was executed.
duration
The length of time (in seconds) between when the transformation was logged (LOGDATE) and the maximum dependency date (DEPDATE).
rows_input
The number of lines read from disk or the network by the specified step. Can be input from files, databases, etc.
rows_output
The number of rows output during the execution of the transformation/job.
rows_read
The number of rows read in from the input stream of the specified step.
rows_written
The number of rows written during the execution of the transformation/job.
rows_rejected
The number of rows rejected during the execution of the transformation/job.
errors
The number of errors that occurred during the execution of the transformation/job.
Batch dimension
(dim_batch)
batch_tk
A technical key (TK) for linking facts to batch information.
batch_id
The ID number for the batch.
logchannel_id
A string representing the identifier for the logging channel used by the batch.
parent_logchannel_id
A string representing the identifier for the parent logging channel used by the batch.
Date dimension
(dim_date)
date_tk
A technical key (TK) for linking facts to date information.
date_field
A Date object representing a particular day (year, month, day).
ymd
A string representing the date value in year-month-day format.
ym
A string representing the date value in year-month format.
year
An integer representing the year value.
quarter
An integer representing the number of the quarter (1-4) to which this date belongs.
quarter_code
A 2-character string representing the quarter (Q1-Q4) to which this date belongs.
month
An integer representing the number of the month (1-12) to which this date belongs.
month_desc
A string representing the month (e.g., January
or December
) to which this date belongs.
month_code
A string representing the shortened month code (e.g., JAN
or DEC
) to which this date belongs.
day
An integer representing the day of the month (1-31) to which this date belongs.
day_of_year
An integer representing the day of the year (1-366) to which this date belongs.
day_of_week
An integer representing the day of the week (1-7) to which this date belongs.
day_of_week_desc
A string representing the day of the week (e.g., Sunday
or Saturday
) to which this date belongs.
day_of_week_code
A string representing the shortened day-of-week code (e.g., SUN
or SAT
) to which this date belongs.
week
An integer representing the week of the year (1-53) to which this date belongs.
Execution dimension
(dim_execution)
execution_tk
A technical key (TK) for linking facts to execution information.
execution_id
A unique string identifier for the execution.
server_name
The name of the server associated with the execution.
server_host
The name of the server associated with the execution.
executing_user
The name of the user who initiated the execution.
execution_status
The status of the execution (start, stop, end, error).
Executor dimension
The following table contains information about an executor that is a job or transformation (dim_executor):
executor_tk
A technical key (TK) for linking facts to executor information.
version
An integer corresponding to the version of the executor.
date_from
A date representing the minimum date for which the executor is valid.
date_to
A date representing the maximum date for which the executor is valid.
executor_id
A string identifier for the executor.
executor_source
The source location (either file- or repository-relative) for the executor.
executor_environment *
File server, repository name, related to the executor_source.
executor_type
The executor type (e.g., job
or transformation
).
executor_name
The name of the executor (e.g., transformation name).
executor_desc
A string description of the executor (e.g., job description).
executor_revision
A string representing the revision of the executor (e.g., 1.3
).
executor_version_label
A string representing a description of the revision (i.e., change comments).
exec_enabled_table_logging
Whether table logging is enabled for this executor. Values are Y
if enabled; N
otherwise.
exec_enabled_detailed_logging
Whether detailed (step or job entry) logging is enabled for this executor. Values are Y
if enabled; N
otherwise.
exec_enabled_perf_logging
Whether performance logging is enabled for this executor. Values are Y
if enabled; N
otherwise.
exec_enabled_history_logging
Whether historical logging is enabled for this executor. Values are Y
if enabled; N
otherwise.
last_updated_date
The date the executor was last updated.
last_updated_user
The name of the user who last updated the executor.
* Reserved for future use.
Log table
The log table (dim_log_table) contains data used by the Pentaho Operations Mart.
CAUTION: Do not modify the Log table. The following table is for reference only:
log_table_tk
A technical key (TK) for linking.
object_type
The type of PDI object being logged (e.g., job
or transformation
or step
).
table_connection_name
The name of the database connection corresponding to the location of the transformation/job logging table.
table_name
The name of the table containing the transformation/job logging information.
schema_name
The name of the database schema corresponding to the location of the transformation/job logging table.
step_entry_table_conn_name
The name of the database connection corresponding to the location of the step/entry logging table.
step_entry_table_name
The name of the table containing the step/entry logging information.
step_entry_schema_name
The name of the database schema corresponding to the location of the step/entry logging table.
perf_table_conn_name
The name of the database connection corresponding to the location of the performance logging table.
perf_table_name
The name of the table containing the performance logging information.
perf_schema_name
The name of the database schema corresponding to the location of the performance logging table.
Time-of-day dimension
This dimension contains entries for every second of a day from midnight to midnight (dim_time).
time_tk
A technical key (TK) for linking facts to time-of-day information.
hms
A string representing the time of day as hours-minutes-seconds (e.g., 00:01:35
).
hm
A string representing the time of day as hours-minutes (e.g., 23:59
).
ampm
A string representing whether the time-of-day is AM or PM. Values are: am
or pm
hour
The integer number corresponding to the hour of the day (0-23).
hour12
The integer number corresponding to the hour of the day with respect to AM/PM (1-12).
minute
The integer number corresponding to the minute of the hour (0-59).
second
The integer number corresponding to the second of the minute (0-59).
Step fact table
This fact table contains facts about individual step executions (fact_step_execution).
execution_date_tk
A technical key (TK) linking the fact to the date when the step was executed.
execution_time_tk
A technical key (TK) linking the fact to the time-of-day when the step was executed.
batch_tk
A technical key (TK) linking the fact to batch information for the step.
executor_tk
A technical key (TK) linking the fact to information about the executor (transformation).
parent_executor_tk
A technical key (TK) linking the fact to information about the parent transformation.
root_executor_tk
A technical key (TK) linking the fact to information about the root transformation/job.
execution_timestamp
The date and time when the step was executed.
step_tk
A technical key (TK) linking the fact to information about the step.
step_copy
The step copy number. This is zero if there is only one copy of the step, or (0
to N-1
) if N
copies of the step are executed.
rows_input
The number of lines read from disk or the network by the step. Can be input from files, databases, etc.
rows_output
The number of lines written to disk or the network by the step. Can be output to files, databases, etc.
rows_read
The number of rows read in from the input stream of the step.
rows_written
The number of rows written to the output stream of the step.
rows_rejected
The number of rows rejected during the execution of the step.
errors
The number of errors that occurred during the execution of the step.
Step dimension
This dimension contains information about individual steps and job entries (dim_step) .
step_tk
A technical key (TK) for linking facts to step/entry information
step_id
The string name of the step/entry
original_step_name *
The name of the step/entry template used to create this step/entry (e.g., Table Input
).
* Reserved for future use.
Job entry fact table
This fact table contains facts about individual job entry executions (fact_jobentry_execution).
execution_date_tk
A technical key (TK) linking the fact to the date when the job entry was executed.
execution_time_tk
A technical key (TK) linking the fact to the time-of-day when the job entry was executed.
batch_tk
A technical key (TK) linking the fact to batch information for the job entry.
executor_tk
A technical key (TK) linking the fact to information about the executor (transformation or job).
parent_executor_tk
A technical key (TK) linking the fact to information about the parent transformation/job.
root_executor_tk
A technical key (TK) linking the fact to information about the root transformation/job.
step_tk
A technical key (TK) linking the fact to information about the job entry.
execution_timestamp
The date and time when the job entry was executed.
rows_input
The number of lines read from disk or the network by the job entry. Can be input from files, databases, etc.
rows_output
The number of lines written to disk or the network by the job entry. Can be output to files, databases, etc.
rows_read
The number of rows read in from the input stream of the job entry.
rows_written
The number of rows written to the output stream of the job entry.
rows_rejected
The number of rows rejected during the execution of the job entry.
errors
The number of errors that occurred during the execution of the job entry.
result
Whether the job entry finished successfully or not. Values are Y
(successful) or N
(otherwise).
nr_result_rows
The number of result rows after execution.
nr_result_files
The number of result files after execution.
Execution performance fact table
This fact table contains facts about the performance of steps in transformation executions (fact_perf_execution).
execution_date_tk
A technical key (TK) linking the fact to the date when the transformation was executed.
execution_time_tk
A technical key (TK) linking the fact to the time-of-day when the transformation was executed.
batch_tk
A technical key (TK) linking the fact to batch information for the transformation.
executor_tk
A technical key (TK) linking the fact to information about the executor (transformation).
parent_executor_tk
A technical key (TK) linking the fact to information about the parent transformation/job.
root_executor_tk
A technical key (TK) linking the fact to information about the root transformation/job.
step_tk
A technical key (TK) linking the fact to information about the transformation/job.
seq_nr
The sequence number. This is an identifier differentiating performance snapshots for a single execution.
step_copy
The step copy number. This is zero if there is only one copy of the step, or (0
to N-1
) if N
copies of the step are executed.
execution_timestamp
The date and time when the transformation was executed.
rows_input
The number of rows read from the input file, database, or network during the interval.
rows_output
The number of rows written to output file, database, or network during the interval.
rows_read
The number of rows read from previous steps during the interval.
rows_written
The number of rows written to following steps during the interval.
rows_rejected
The number of rows rejected by the steps error handling during the interval.
errors
The number of errors that occurred during the execution of the transformation/job.
input_buffer_rows
The size of the step’s input buffer in rows at the time of the snapshot.
output_buffer_rows
The size of the output buffer in rows at the time of the snapshot.
Last updated
Was this helpful?