Logging & Monitoring

Monitoring

Once Prequel is up and running, you may wish to monitor activity on the platform. Prequel automatically logs the following events which can be reviewed using the logs API endpoint.

event_type	resource_id	Logged when...
`DESTINATION_ADD`	`{destination_id}`
`DESTINATION_DELETE`	`{destination_id}`
`DESTINATION_UPDATE`	`{destination_id}`
`ENABLE_ALL`
`FULL_REFRESH_START`	`{destination_id}`	a `full_refresh: true` transfer kicks off
`FULL_REFRESH_END`	`{destination_id}`	a `full_refresh: true` transfer finishes
`MAGIC_LINK_CREATE`	`{magic_link_id}`
`MAGIC_LINK_DELETE`	`{magic_link_id}`
`MODEL_ERROR`	`{destination_id}`	an individual model fails to transfer. This is usually due to either an invalid model config file, or a data integrity issue in the source table.
`MODEL_SUCCESS`	`{destination_id}`	an individual model succeeds.
`MODEL_SKIPPED`	`{destination_id}`	an individual model is skipped, due to no new data being present in the source table.
`TRANSFER_CANCELED`	`{destination_id}`	a transfer is canceled. This happens if there is a transfer of the same type already in progress for the given source <> destination pair.
`TRANSFER_CLEANUP`	`{destination_id}`	a transfer is cleaned up. This usually happens after a transfer failed, and means we clean up possible dangling artifacts like temp tables.
`TRANSFER_END`	`{destination_id}`
`TRANSFER_ERROR`	`{destination_id}`	a transfer fails to run. This is usually due to an error when attempting to connect to the source or the destination.
`TRANSFER_RESCHEDULED`	`{destination_id}`	a transfer is rescheduled. This happens when a `full_refresh` transfer is requested, but there is an incremental transfer already in progress for the given source <> destination pair.
`TRANSFER_START`	`{destination_id}`	a transfer to a destination begins. Transfers are comprised of multiple models.
`PAUSE_ALL`
`SOURCE_ADD`	`{source_id}`
`SOURCE_DELETE`	`{source_id}`
`SOURCE_UPDATE`	`{source_id}`