Update clickpipes error reporting section to mention the system table #3550
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
2 Skipped Deployments
|
| @@ -70,8 +70,8 @@ Steps: | |||
| <Image img={cp_custom_role} alt="Assign a custom role" size="lg" border/> | |||
|
|
|||
| ## Error reporting {#error-reporting} | |||
There was a problem hiding this comment.
I think it could be nice to add a bit of structure and elaborate a bit:
Logging and Errors
And then have two separate sections:
Record Errors Table
ClickPipes will create a table next to your destination table with the postfix <destination_table_name>_clickpipes_error. This table will contain any errors from malformed data or mismatched schema and will include the entirety of the invalid message. These errors are by default retained for ....
ClickPipe Logs
yada yada
This can be accessed via the UI or queried directly with clusterAllReplicas and maybe provide an example query?
| ### System Errors {#system-errors} | ||
| Errors related to the operation of the ClickPipe will be stored in the `system.clickpipes_log` table. This will store all other errors related to the operation of your ClickPipe (network, connectivity, etc.). This table has a [TTL](/engines/table-engines/mergetree-family/mergetree#table_engine-mergetree-ttl) of 7 days. | ||
|
|
||
| If ClickPipes cannot connect to a data source or destination after 15 min., the ClickPipes instance stops and stores an appropriate message in the system error table (providing the ClickHouse instance is available). |
There was a problem hiding this comment.
15min for data source connectivity is correct, but we give 1h for destination connectivity.
Summary
Updated error reporting section on clickpipes to include the system error table for clickpipes.
Notes
Marking as draft until the notification email has been sent out to users.