From 03aac5c173ea58e03854443aabf8ad8a218b4e87 Mon Sep 17 00:00:00 2001 From: Joy Gao <17896160+jgao54@users.noreply.github.com> Date: Thu, 25 Jun 2026 12:17:29 -1000 Subject: [PATCH] feat(clickpipes): clarify error logging does not store in clickhouse tables today --- docs/integrations/data-ingestion/clickpipes/index.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/integrations/data-ingestion/clickpipes/index.md b/docs/integrations/data-ingestion/clickpipes/index.md index 86793349c8f..9548363a591 100644 --- a/docs/integrations/data-ingestion/clickpipes/index.md +++ b/docs/integrations/data-ingestion/clickpipes/index.md @@ -159,6 +159,11 @@ ClickPipes provides sensible defaults that cover the requirements of most use ca ## Error reporting {#error-reporting} ClickPipes will store errors in two separate tables depending on the type of error encountered during the ingestion process. + +:::note +This does not currently apply to CDC pipes (Postgres, MySQL, and MongoDB), for which operational and error logging are available directly in the ClickHouse Cloud console. +::: + ### Record errors {#record-errors} ClickPipes will create a table next to your destination table with the postfix `_clickpipes_error`. This table will contain any errors from malformed data or mismatched schema and will include the entirety of the invalid message. This table has a [TTL](/engines/table-engines/mergetree-family/mergetree#table_engine-mergetree-ttl) of 7 days. ### System errors {#system-errors}