Skip to main content

Celonis Product Documentation

Processed Data
Data Consumption Monitoring

The Data Consumption Monitoring Data Model consists of four tables representing the organizational structure of Data Integration, allowing you to take different perspectives on your data consumption.

Table

Description

data_pools

Your Data Pools

data_connections

Your Data Connections, associated to your Data Pools

data_tables

Your tables, associated to your Data Connections

data_consumption_updated_events

The log of the data consumption calculations. In this table, you can find historic data consumption information for each table.

Data Pipeline Monitoring

The Data Pipeline Monitoring Data Model contains case tables for each entity of a data pipeline execution, namely:

  • Schedules

  • Data Jobs

  • Tasks

    • Extractions

    • Transformations

    • Data Model loads

  • Steps

    • Individual tables in an Extraction

    • Individual table exports in Data Model loads and the Engine load

Table

Description

schedule_executions

Your schedule executions

schedule_execution_events

The different stages of your schedule executions

data_job_executions

Your Data Job executions

data_job_execution_events

The different stages of your Data Job executions

task_executions

Your Task executions, this includes Extractions, Transformations, and Data Model loads

task_execution_events

The different stages of your Task executions

step_executions

Your Step executions, this includes the individual tables in an Extraction and the export of individual tables in Data Model loads and the Engine load

step_execution_events

The different stages of your Step executions

extraction_table_executions

Individual tables in your Extractions

extraction_table_execution_events

The different stages of individual tables in your Extractions

data_model_executions

Your Data Model loads

data_model_execution_events

The different stages of your Data Model loads

Replication Cockpit Monitoring

The Replication Cockpit Monitoring builds on a simple Data Model with just two tables which hold information about your Replications on a table level. Each entry in the replication_executions table is the replication of a table from your source system, consisting of the extraction of the table and, optionally, its subsequent transformation. The different stages from Extraction start to Extraction end (or possibly Transformation end) are logged in the replication_execution_events table.

Table

Description

replication_executions

Your Replications

replication_execution_events

The different stages of your Replications