You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -37,7 +37,7 @@ chDB has the following language bindings:
37
37
## How do I get started? {#how-do-i-get-started}
38
38
39
39
* If you're using [Go](install/go.md), [Rust](install/rust.md), [NodeJS](install/nodejs.md), [Bun](install/bun.md) or [C and C++](install/c.md), take a look at the corresponding language pages.
40
-
* If you're using Python, see the [getting started developer guide](getting-started.md). There are also guides showing how to do common tasks like:
40
+
* If you're using Python, see the [getting started developer guide](getting-started.md) or the [chDB on-demand course](https://learn.clickhouse.com/user_catalog_class/show/1901178). There are also guides showing how to do common tasks like:
@@ -378,8 +379,20 @@ You can customize a dashboard using metrics from system tables like `system.metr
378
379
379
380
<br />
380
381
382
+
#### Access the BYOC Prometheus stack {#prometheus-access}
383
+
ClickHouse BYOC deploys a Prometheus stack on your Kubernetes cluster. You may access and scrape the metrics from there and integrate them with your own monitoring stack.
384
+
385
+
Contact ClickHouse support to enable the Private Load balancer and ask for the URL. Please note that this URL is only accessible via private network and does not support authentication
**DEPRECATED: ** Please use the Prometheus stack integration in the above section instead. Besides the ClickHouse Server metrics, it provides more metrics including the K8S metrics and metrics from other services.
395
+
383
396
ClickHouse Cloud provides a Prometheus endpoint that you can use to scrape metrics for monitoring. This allows for integration with tools like Grafana and Datadog for visualization.
384
397
385
398
**Sample request via https endpoint /metrics_all**
A ClickHouse username and password pair can be used for authentication. We recommend creating a dedicated user with minimal permissions for scraping metrics. At minimum, a `READ` permission is required on the `system.custom_metrics` table across replicas. For example:
420
433
421
434
```sql
422
-
GRANT REMOTE ON*.* TO scraping_user
423
-
GRANTSELECTONsystem.custom_metrics TO scraping_user
435
+
GRANT REMOTE ON*.* TO scrapping_user;
436
+
GRANTSELECTONsystem._custom_metrics_dictionary_custom_metrics_tables TO scrapping_user;
437
+
GRANTSELECTONsystem._custom_metrics_dictionary_database_replicated_recovery_time TO scrapping_user;
438
+
GRANTSELECTONsystem._custom_metrics_dictionary_failed_mutations TO scrapping_user;
439
+
GRANTSELECTONsystem._custom_metrics_dictionary_group TO scrapping_user;
440
+
GRANTSELECTONsystem._custom_metrics_dictionary_shared_catalog_recovery_time TO scrapping_user;
441
+
GRANTSELECTONsystem._custom_metrics_dictionary_table_read_only_duration_seconds TO scrapping_user;
442
+
GRANTSELECTONsystem._custom_metrics_view_error_metrics TO scrapping_user;
443
+
GRANTSELECTONsystem._custom_metrics_view_histograms TO scrapping_user;
444
+
GRANTSELECTONsystem._custom_metrics_view_metrics_and_events TO scrapping_user;
445
+
GRANTSELECT(description, metric, value) ONsystem.asynchronous_metrics TO scrapping_user;
446
+
GRANTSELECTONsystem.custom_metrics TO scrapping_user;
447
+
GRANTSELECT(name, value) ONsystem.errors TO scrapping_user;
448
+
GRANTSELECT(description, event, value) ONsystem.events TO scrapping_user;
449
+
GRANTSELECT(description, labels, metric, value) ONsystem.histogram_metrics TO scrapping_user;
450
+
GRANTSELECT(description, metric, value) ONsystem.metrics TO scrapping_user;
Copy file name to clipboardExpand all lines: docs/cloud/features/05_admin_features/upgrades.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ When you create a service, the [`compatibility`](/operations/settings/settings#c
30
30
31
31
The `compatibility` setting allows you to use default values of settings from previous versions. When your service is upgraded to a new version, the version specified for the `compatibility` setting does not change. This means that default values for settings that existed when you first created your service will not change (unless you have already overridden those default values, in which case they will persist after the upgrade).
32
32
33
-
You cannot manage the `compatibility` setting for your service. You must [contact support](https://clickhouse.com/support/program) if you would like to change the version set for your `compatibility` setting.
33
+
You cannot manage the service-level default `compatibility` setting for your service. You must [contact support](https://clickhouse.com/support/program) if you would like to change the version set for your service's default `compatibility` setting. However, you can override the `compatibility` setting at the user, role, profile, query, or session level using standard ClickHouse setting mechanisms such as `SET compatibility = '22.3'` in a session or `SETTINGS compatibility = '22.3'` in a query.
<Imageimg={samlAzureClaims}size="md"alt="Attributes and Claims" />
301
+
<Imageimg={samlAzureClaims}size="md"alt="Attributes and Claims"force/>
302
302
303
303
12. Gather these two items and go to Submit a Support Case above to complete the process:
304
304
- Login URL
@@ -366,4 +366,3 @@ Security is our top priority when it comes to authentication. For this reason, w
366
366
-**All users assigned to your app via your IdP must have the same email domain.** If you have vendors, contractors or consultants you would like to have access to your ClickHouse account, they must have an email address with the same domain (e.g. user@domain.com) as your employees.
367
367
368
368
-**We do not automatically link SSO and non-SSO accounts.** You may see multiple accounts for your users in your ClickHouse user list even if they are using the same email address.
Copy file name to clipboardExpand all lines: docs/cloud/reference/03_billing/01_billing_overview.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -184,6 +184,10 @@ A ClickHouse Credit is a unit of credit toward Customer's usage of ClickHouse Cl
184
184
185
185
Legacy pricing information can be found [here](https://clickhouse.com/pricing?legacy=true).
186
186
187
+
:::note
188
+
If you are being billed through Stripe then you will see that 1 CHC is equal to \$0.01 USD on your Stripe invoice. This is to allow accurate billing on Stripe due to their limitation on not being able to bill fractional quantities of our standard SKU of 1 CHC = \$1 USD.
189
+
:::
190
+
187
191
### How is compute metered? {#how-is-compute-metered}
188
192
189
193
ClickHouse Cloud meters compute on a per-minute basis, in 8G RAM increments.
ClickPipes provides sensible defaults that cover the requirements of most use cases. If your use case requires additional fine-tuning, you can adjust the following settings:
88
88
89
-
-**Streaming max insert wait time**: Configures the maximum wait period before inserting data into the ClickHouse cluster. Applies to streaming ClickPipes (e.g., Kafka, Kinesis).
90
-
-**Object storage polling interval**: Configures how frequently ClickPipes checks object storage for new data. Applies to object storage ClickPipes (e.g., S3, GCS).
|`Max insert bytes`| 10GB | Number of bytes to process in a single insert batch. |
94
+
|`Max file count`| 100 | Maximum number of files to process in a single insert batch. |
95
+
|`Max threads`| auto(3) |[Maximum number of concurrent threads](/operations/settings/settings#max_threads) for file processing. |
96
+
|`Max insert threads`| 1 |[Maximum number of concurrent insert threads](/operations/settings/settings#max_insert_threads) for file processing. |
97
+
|`Min insert block size bytes`| 1GB |[Minimum size of bytes in the block](/operations/settings/settings#min_insert_block_size_bytes) which can be inserted into a table. |
98
+
|`Max download threads`| 4 |[Maximum number of concurrent download threads](/operations/settings/settings#max_download_threads). |
99
+
|`Object storage polling interval`| 30s | Configures the maximum wait period before inserting data into the ClickHouse cluster. |
Copy file name to clipboardExpand all lines: docs/integrations/data-ingestion/dbms/postgresql/connecting-to-postgresql.md
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,11 +14,14 @@ import ExperimentalBadge from '@theme/badges/ExperimentalBadge';
14
14
15
15
This page covers following options for integrating PostgreSQL with ClickHouse:
16
16
17
-
- using [ClickPipes](/integrations/clickpipes/postgres), the managed integration service for ClickHouse Cloud powered by PeerDB.
18
-
- using [PeerDB](https://github.com/PeerDB-io/peerdb), an open-source CDC tool specifically designed for PostgreSQL database replication to both self-hosted ClickHouse and ClickHouse Cloud.
19
17
- using the `PostgreSQL` table engine, for reading from a PostgreSQL table
20
18
- using the experimental `MaterializedPostgreSQL` database engine, for syncing a database in PostgreSQL with a database in ClickHouse
21
19
20
+
:::tip
21
+
We recommend using [ClickPipes](/integrations/clickpipes/postgres), a managed integration service for ClickHouse Cloud powered by PeerDB.
22
+
Alternatively, [PeerDB](https://github.com/PeerDB-io/peerdb) is available as an an open-source CDC tool specifically designed for PostgreSQL database replication to both self-hosted ClickHouse and ClickHouse Cloud.
23
+
:::
24
+
22
25
## Using the PostgreSQL table engine {#using-the-postgresql-table-engine}
23
26
24
27
The `PostgreSQL` table engine allows **SELECT** and **INSERT** operations on data stored on the remote PostgreSQL server from ClickHouse.
0 commit comments