Bobsled generates and logs several types of data related to your usage of Bobsled Sledhouse and Bobsled transfers in the form of structured log events from system and manual actions from Sledhouse Tables, Data Products, Data Fulfillment, and Bobsled Transfers.
You can use this data for the following purposes:
Monitoring and troubleshooting the movement of your data in and out of Bobsled.
Conducting audits and tracing changes made in the system.
You can monitor and process this data by locating the desired object, navigating to the detail page, and selecting the ‘Log’ tab. Bobsled also offers Webhook integrations.
BOBSLED SLEDHOUSE LOGS ARE IN PUBLIC PREVIEW
Feature is in public preview. It is suitable for certain production workloads but may not be appropriate for all use cases. For guidance, contact your account representative. More events are added
Bosbled Sledhouse log event format (public preview)
Bobsled Sledhouse events are standardized in JSON format.
{
"timestamp": // Date of the event, following ISO 8601
"logId": // Unique identifier for log
"trigger": // System or Manual
"message": // Human-friendly description of the event
"code": // Programatic, unique identifier for the event
"eventName": // Human-friendly identifier for the event
"level": // Severity of the event.
"author": // Author email or service account. NULL when triggered by the system.
"resource": [
{
// Varies by event. One or more resources of interest for the generation of a log.
}
],
"jobId": // Optional. Unique identifier for a job, applicable across multiple logs.
"details": {
// Contents of the log. Varies by event.
}
}For payload examples, please refer to the Sledhouse API documentation ↗
Sledhouse Table events
Bobsled will generate the following events for Sledhouse Tables:
Event | Trigger | Description |
|---|---|---|
Sledhouse Table created |
| A user has manually created a new Sledhouse Table. |
Sledhouse Table edited |
| A user has manually edited a new Sledhouse Table. This may result in a new spec version. |
Sledhouse Table deleted |
| A user has deleted a Sledhouse Table. |
Sync queued |
| A user has manually requested a sync, or the system has queued a sync following the Sledhouse Table scheduling options. |
Sync started |
| The system has triggered a sync. |
Sync completed |
| The system has completed the data sync |
Sync failed |
| The sync has failed. |
Fresh data check |
| The system detected if the Sledhouse Table source has new data added since the previous sync. |
Load started |
| Bobsled has started the operation of moving data from your source. |
Load completed |
| Bobsled has completed the load operation. |
Load failed |
| The data has failed to load. |
Schedule paused |
| A user has paused the schedule—the frequency at which the system performs sync operations. |
Schedule resumed |
| A user has resumed the schedule. |
Backfill sync queued |
| A user has manually requested a backfill sync, and the system has queued it. |
Backfill sync started |
| The system has begun a backfill sync. |
Backfill sync completed |
| The system has completed a backfill sync. |
Data Fulfillment events
Bobsled will generate the following events for Data Fulfillment:
Event | Trigger | Description |
|---|---|---|
Data consumer created |
| A user has created a new Data Consumer |
Data consumer edited |
| A user has edited the Data Consumer details. |
Data consumer deleted |
| A user has deleted a Data Consumer and its metadata. |
Data fulfillment created |
| A user has manually configured—added, customized—data products to share with a Data Consumer. |
Data fulfillment edited |
| A user has manually edited—added, customized or removed—data products shared with a Data consumer. |
Destination edited |
| A user has manually edited the details of the destination for a Data Consumer. |
Data Fulfillment for Cloud Data Warehouse destinations
Event | Trigger | Description |
|---|---|---|
Data Product view created/replaced |
| A data product view has been created or replaced in the destination. |
Data Product view dropped |
| A view generated from a data product has been dropped from the destination. |
Data Product view failed |
| A view has failed to generate or to be replaced in the destination. |
Data Fulfillment for File Storage destinations
Event | Trigger | Description |
|---|---|---|
File conversion check |
| The system is checking if a given data product exists in a file format available to be fulfilled for a given data consumer. |
File conversion started |
| A new conversion in a file format has been triggered for a given data product. |
File conversion completed |
| The file conversion for a given data product has been completed. |
File conversion failed |
| An error has occurred, and the file conversion has failed. |
File conversion backfill started | | A file conversion backfill has been triggered. |
File conversion backfill completed |
| A file conversion backfill has been completed. |
File conversion backfill failed |
| An error has occurred, and the file conversion backfill has failed. |
Sharing started |
| Sharing the data product converted into a file format with the destination has started. |
Sharing completed |
| Sharing the converted data product has been completed. |
Sharing failed |
| An error has occurred, and sharing the data has failed. |
Bosbled Transfer Logs
This section will describe how you can observe information about a Share and the data transferred.
Logs can be found at the bottom of each Share, next to the Transfers tab.
Log events
When system and user actions are executed concerning a Share, they're stored in the Share Log. The Share Log will display the following events and information:
Event | Description |
|---|---|
| Share Transfer Configuration Created |
| Share Transfer Configuration Edited |
| Share Transfer Configuration Delete |
| Data transfer started |
| Data transfer completed |
| Data transfer paused |
| Data transfer failed |
| Data transfer from a Table Started |
| Data transfer from a Table Completed |
| Data transfer from a Table Failed |
| Data transfer from a Cloud Storage FilePath started |
| Data transfer from a Cloud Storage FilePath Completed |
| Data transfer from a Cloud Storage FilePath Failed |
| The Source for this Share has been deleted |
| The table has started unloading from a data warehouse source |
| The table has completed unloading from a data warehouse source |
Log event payload examples
Refer to our webhooks docs on the API docs site ↗ for webhook and log event payloads.