Raw data
data_consumption_updated_events
When the Data Consumption is calculated, one record per table and pool is generated and stored in the data_consumption_updated_events table. The update frequency of the APC may differ depending on the environment on which your Celonis instance is running.
Column | Description |
|---|---|
id | Unique identifier for each entry |
schema_version | Schema version shows the version of the table configuration of the data_consumption_updated_events table |
created_at | Timestamp of when this event has been logged by the system |
data_pool_id | Corresponding Data Pool ID of the table |
data_pool_name | Corresponding Data Pool name of the table |
data_connection_id | Corresponding Data Connection ID of the table |
data_connection_type | Corresponding Data Connection name of the table |
table_name | Table name |
size_in_bytes | APC Consumption in bytes |
data_job_state_updated_events
For each Data Job execution step, i.e. for each status change an execution can attain (QUEUED, RUNNING, SUCCESS, CANCEL, FAIL), an event is generated. These entries are added to the data_job_state_updated_events table every five minutes.
Column | Description |
|---|---|
id | Unique identifier for each entry |
schema_version | Schema version shows the version of the table configuration of the table data_job_state_updated_events |
created_at | Timestamp when this event has been logged by the system |
data_pool_id | Corresponding Data Pool ID of the event |
data_pool_name | Corresponding Data Pool Name of the event |
data_pool_version | Corresponding Data Pool Version of the event |
data_connection_id | Corresponding Data Connection ID of the event |
data_connection_name | Corresponding Data Connection Name of the event |
data_connection_type | Corresponding Data Connection Type of the event, such as SAP ECC |
execution_id | Execution ID of the overall execution that triggered this event |
execution_item_id | Execution ID of a single object - either an Extraction, Transformation, Data Job, Data Model Load, or Schedule |
scheduling_id | Schedule ID, filled only if the event relates to a Schedule |
scheduling_name | Schedule Name, filled only if the event relates to a Schedule |
data_job_id | Data Job ID, filled only if the event relates to a Data Job |
task_id | Task ID, filled only if the event relates to a Task |
step_id | Step ID, filled only if the event relates to an Extraction or Data Model Load Step which corresponds to a Table or an Engine Load |
name | Name of the Execution Item |
status | Execution Status: QUEUED, RUNNING, SUCCESS, FAIL, CANCEL |
message | Stores the error message if the execution failed |
execution_type | Type of execution:
|
mode | Extraction Mode:
|
task_type | Type of task:
|
scheduler_cron_pattern | Cron pattern of the Schedule, filled only if the event relates to a Schedule. |
data_model_load_events
For each Data Model Load step, i.e., for each status, an execution can attain (RUNNING, SUCCESS, WARNING, ERROR, CANCELLED), an event is generated. These entries are added to the data_model_load_events table every five minutes.
Column | Description |
|---|---|
id | Unique identifier for each entry |
schema_version | Schema version shows the version of the table configuration of the table data_model_load_events |
created_at | Timestamp of when this event has been logged by the system |
data_model_load_id | Unique identifier of the Data Model Load on compute side, this identifier is set when the Engine Load starts |
data_model_id | Unique identifier of the Data Model |
load_history_id | Unique identifier of the Data Model Load, this identifier is shared across all events in one execution |
status | Data Model Load Status:
|
execution_type | Execution Type:
|
load_type | Load Type of the Data Model:
|
data_model_name | Name of the Data Model |
data_pool_id | Corresponding Data Pool ID of the Data Model Load |
data_pool_name | Corresponding Data Pool Name of the Data Model Load |
table_name | Table Name related to the record, Data Models are loaded table by table |
table_alias | Table Alias related to the record, tables can be assigned aliases to make the Data Model easier to understand or hide implementation details |
data_connection_id | Corresponding Data Connection ID from which the table is loaded |
data_connection_name | Corresponding Data Connection Name from which the table is loaded |
data_connection_type | Corresponding Data Connection Type, e.g., SAP ECC, from which the table is loaded |
row_count | Number of rows in a table in a Data Model (calculated in the Engine Table Step with Execution Type ENGINE_TABLE) |
message | Stores the message if the Data Model Load fails or throws a warning |
execution_id | Execution ID of the execution that triggered this event |
execution_item_id | Execution ID of the Data Model Load if the Data Model Load is part of a Data Job Execution |
job_execution_item_id | Execution Item ID of the Data Job that triggered the Data Model Load |
data_pool_version | Version number of the Data Pool in which the Data Model Load ran |
replication_execution_finished_events
For each finished Replication Cockpit Execution, an event that contains i.e., the status and start/end times of the Extractions and Transformations. These events are added to the replication_execution_finished_events table every five minutes.
Column | Description |
|---|---|
id | Unique identifier for each entry |
created_at | Timestamp when this event has been logged by the system |
schema_version | Schema version shows the version of the table configuration of the replication_execution_finished_events table |
execution_id | Execution ID of the overall execution that triggered this event |
replication_id | Unique identifier of each Replication (table) |
table_name | Name of the table that is being replicated |
data_pool_id | Corresponding Data Pool ID of the Replication |
data_pool_name | Corresponding Data Pool Name of the Replication |
data_source_id | Corresponding Data Source (Data Connection) ID of the Replication |
data_source_name | Corresponding Data Source (Data Connection) Name of the Replication |
start_time | Timestamp when the Replication started |
end_time | Timestamp when the Replication ended |
extraction_start_time | Timestamp when the Extraction started |
push_job_created_time | Timestamp when the Data Push Job was created |
push_job_executed_time | Timestamp when the Data Push Job was executed |
extraction_end_time | Timestamp when the Extraction finished |
transformation_start_time | Timestamp when the Transformation started |
transformation_end_time | Timestamp when the Transformation ended |
status | Overall status of the Replication |
extraction_status | Status of the Extraction |
transformation_status | Status of the Transformation |
cycle | Execution ID of the overall Execution that triggered this Execution |
error_key | Type of the error, filled only if an error occurred |
error_message | Error message, filled only if an error occurred |
extracted_records | Number of records that have been extracted |
extracted_deletion_records | Number of deleted records that have been extracted |