Skip to main content
Skip to main content
Edit this page

Notifications

ClickHouse Cloud sends notifications about critical events related to your service or organization. There are a few concepts to keep in mind to understand how notifications are sent and configured:

  1. Notification category: Refers to groups of notifications such as billing notifications, service related notifications etc. Within each category, there are multiple notifications for which the delivery mode can be configured.
  2. Notification severity: Notification severity can be info, warning, or critical depending on how important a notification is. This isn't configurable.
  3. Notification channel: Channel refers to the mode by which the notification is received such as UI, email, Slack etc. This is configurable for most notifications.

Receiving notifications

Notifications can be received via various channels. ClickHouse Cloud supports receiving notifications through email, ClickHouse Cloud UI, and Slack. You can click on the bell icon in the top left menu to view current notifications, which opens a flyout. Clicking the button View All at the bottom of the flyout will take you to a page that shows an activity log of all notifications.

Customizing notifications

For each notification, you can customize how you receive the notification. You can access the settings screen from the notifications flyout or from the second tab on the notifications activity log.

You can customize notifications delivered via the Cloud UI, and these customizations are reflected for each individual user. You can also customize notifications delivered to your own emails, but only users with admin permissions can customize notifications delivered to custom emails and notifications delivered to Slack channels.

To configure delivery for a specific notification, click on the pencil icon to modify the notification delivery channels.

Note

Certain required notifications such as Payment failed aren't configurable.

Service notifications

ClickHouse sends service notifications when a certain alert condition is triggered. See below for more information on service notifications for ClickHouse Cloud:

Notify whenSpecific alert conditionDefault notification channelsResolution steps
Cluster can not be scaled upWhen recommended cluster size exceeds vertical scaling maximum limit. New notification is generated when recommended cluster size changes.Consider raising maximum size per replica autoscaling limit. See scaling.
Too many parts errorWhen 'too many parts' error is detected. Notification will only trigger once per calendar day.Administrator users will receive an email.Consider batching inserts. See Exception: Too many parts.
Failed mutationsWhen a mutation is in a failed state for 15 mins. Notification will only trigger once per calendar day.Administrator users will receive an email.Kill failed mutation. See Avoid mutations.
High query concurrencyWhen query concurrency exceeds 1,000 per replica. Notification will only trigger once per calendar day.Administrator users will receive an email.Consider adding replicas.
Cluster scaling completedWhen a cluster's size changes.N/A
Cluster can not be scaled downWhen recommended cluster size exceeds vertical scaling maximum limit. New notification is generated when recommended cluster size changes.Consider lowering minimum size per replica autoscaling limit. See scaling.
ClickHouse version changedWhen ClickHouse service version update is beginning, and when it has completed.N/A

ClickPipes notifications

ClickHouse sends ClickPipes notifications when a certain alert condition is triggered. See below for more information on ClickPipes notifications for ClickHouse Cloud:

Notify whenSpecific alert conditionDefault notification channelsResolution steps

Billing notifications

ClickHouse sends billing notifications when a certain alert condition is triggered. See below for more information on billing notifications for ClickHouse Cloud:

Notify whenSpecific alert conditionDefault notification channelsResolution steps

Supported notifications

Currently, we send out notifications related to billing (payment failure, usage exceeded a certain threshold, etc.) as well as notifications related to scaling events (scaling completed, scaling blocked etc.).