Skip to content

Commit 86362ae

Browse files
authored
Merge pull request #5522 from ClickHouse/update-core-dump-collection-kb
Update kb article with note and screenshot
2 parents a481edb + 7283948 commit 86362ae

File tree

2 files changed

+15
-7
lines changed

2 files changed

+15
-7
lines changed

knowledgebase/opt-out-core-dump-collection.mdx

Lines changed: 15 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,28 +1,30 @@
11
---
22
date: 2026-02-04
3-
title: 'How to opt out of core dump collection'
4-
description: 'This article shows you how you can opt out of core dump collection on ClickHouse Cloud'
3+
title: 'How to opt out of crash report collection'
4+
description: 'This article shows you how you can opt out of crash report collection on ClickHouse Cloud'
55
tags: ['Managing Cloud']
66
---
77

88
import optOut from '@site/static/images/crash-reports.png';
9+
import crash_reports_collection from '@site/static/images/cloud/crash-reports-collection.png';
10+
911
import Image from '@theme/IdealImage';
1012

1113
{frontMatter.description}
1214
{/* truncate */}
1315

1416
## Overview
1517

16-
Starting **February 27, 2026**, ClickHouse Cloud will begin collecting core dumps when server crashes occur. This is part of our commitment to improving service reliability for all our users.
18+
Starting **February 27, 2026**, ClickHouse Cloud will begin collecting crash reports when server crashes occur. This is part of our commitment to improving service reliability for all our users.
1719

18-
Core dump collection helps us:
20+
Crash report collection helps us:
1921
- Identify and understand what caused a crash
2022
- Fix issues more quickly
2123
- Continuously improve your service experience
2224

2325
## What's collected
2426

25-
When a crash occurs, core dumps capture a snapshot of the server's state at that moment. We want to be transparent that this may include sensitive information that was in memory, such as:
27+
When a crash occurs, crash reports capture a snapshot of the server's state at that moment. We want to be transparent that this may include sensitive information that was in memory, such as:
2628

2729
- Connection credentials
2830
- Encryption keys
@@ -39,15 +41,15 @@ We take the security of this data seriously:
3941

4042
## Services automatically excluded
4143

42-
Some services are automatically excluded from core dump collection:
44+
Some services are automatically excluded from crash report collection:
4345

4446
- Services with **HIPAA** compliance requirements
4547
- Services with **PCI** compliance requirements
4648
- **BYOC** (Bring Your Own Cloud) services
4749

4850
## How to opt out
4951

50-
If you'd prefer not to participate in core dump collection, you can easily opt out:
52+
If you'd prefer not to participate in crash report collection, you can easily opt out:
5153

5254
1. Go to the [ClickHouse Cloud Console](https://clickhouse.cloud)
5355
2. Select your service
@@ -56,3 +58,9 @@ If you'd prefer not to participate in core dump collection, you can easily opt o
5658
5. Toggle the option off to opt out
5759

5860
<Image img={optOut} size="md" alt="Where to find the opt out option in Cloud UI"/>
61+
62+
:::note
63+
In addition to the service setting, we also support configuring preferences for the organization. If the setting is disabled, i.e., opt out of the crash report collection, all existing and new services will be opted out automatically. If you set the preference to enabled i.e. opt in, you can selectively disable at the service level to override and opt out.
64+
:::
65+
66+
<Image img={crash_reports_collection} size="md" alt="Crash reports collection"/>
98.5 KB
Loading

0 commit comments

Comments
 (0)