Articles in this section

Analyze your sync progress with event logs

Michelle Welch
Updated

Event logs capture phases of a Celigo sync's run to help you analyze its data ingestion progress. To view them, go to the sync's integration, select the sync name, then select Event logs from the top of the page.

di-event-log.png

Select a date range from the top of the dashboard to filter the events displayed.

Understand the event log

An event log includes the following information to help you analyze your sync's progress:

  • Timestamp — The date and time the event completed. Sortable by newest or oldest.
  • Stage — The point in data ingestion (for example extract or transform) when the event occurred.
  • Type — The category of event detected. Filterable by the following options:
    • All types
    • Data catalog —During the sync, Celigo sync detected a new column in the source data and, per your schema drift policy, automatically added it to the destination table.
    • Schema drift — Celigo detected a schema change in the source data. Destination updates will occur according to your configured schema drift policy.
  • Resource — The name of the table or object at the corresponding stage. Filterable by table.
  • Action — The event the sync performed, such as removing a table or expanding a column.
  • View — Select to open a trace of the event, showing what the sync did in response. The trace includes:
    • Event id — The unique identifier for this drift event, useful when referencing the event with Celigo support.
    • Field — The source field that changed (for example, a Salesforce custom field such as SANDBOXPROVISION__C).
    • New value — The Celigo data type assigned to the field (see Understand how data types are inferred).
    • The executed statement — The SQL statement Celigo sync ran against your destination to apply the change, for example: ALTER TABLE TRAVIS_DB.DRIFTTEST.ACCOUNT ADD COLUMN IF NOT EXISTS SANDBOXPROVISION__C BOOLEAN. The statement references the destination as <database>.<schema>.<table>, so you can see exactly which table was altered. Select Copy copy.png to quickly reuse the statement in other environments or share it with your database administrator.

Learn more