Skip to main content
Skip to main content
Edit this page

Community and partner integrations

Datadog integration

For Prometheus endpoint setup details, see the Prometheus integration page.

For users interested in monitoring their ClickHouse deployment in Datadog, ClickHouse offers multiple integrations, suited to different deployment modes. Each has its own tradeoffs, and some are owned by ClickHouse while others are owned by Datadog. Integrations are listed in recommended order.

IntegrationDocsDeploymentSignals
ClickHouse Cloud Datadog API integration (recommended)docs.datadoghq.comCloudMetrics
ClickHouse Cloud Prometheus integrationclickhouse.com/docsCloudMetrics
ClickHouse Datadog Agent integrationdocs.datadoghq.comOSS / CloudLogs, Metrics
ClickHouse Datadog DBMdatadoghq.comOSS / CloudLogs, Metrics, Query Insights

ClickHouse Cloud Datadog API integration

Private preview

The recommended way to serve service-level metrics from ClickHouse Cloud in Datadog.

The customer provides a Datadog API key, and Datadog periodically polls the ClickHouse Cloud API to collect metrics using a push-based method authenticated via an OAuth handshake.

  • Cloud only — not suitable for OSS ClickHouse
  • Metrics are not treated as custom metrics by Datadog
  • Does not prevent the service from idling
  • Ships with a pre-configured set of dashboards and monitors For onboarding steps, see ClickHouse Cloud & Datadog - Integration.

ClickHouse Cloud Prometheus integration

The most common and universal way to collect service-level and org-level telemetry from ClickHouse Cloud.

The customer configures the Datadog Agent with the OpenMetrics integration to periodically poll the ClickHouse Cloud API and collect metrics. See the Prometheus integration page for configuration details.

  • Cloud only — not suitable for OSS ClickHouse
  • Metrics are treated as custom metrics by Datadog
  • Does not prevent the service from going idle

ClickHouse Datadog Agent integration

The most common way to get data from on-premises ClickHouse services into Datadog. It also works with ClickHouse Cloud, with some caveats.

The Datadog Agent periodically polls the ClickHouse instance and collects metrics and logs. This integration ships with a pre-configured set of dashboards.

OSS ClickHouse: logs and metrics fully supported.

ClickHouse Cloud (partial support):

  • Metrics only — logs are not supported
  • Requires datadog-cluster-agent instead of datadog-agent
  • Will prevent the service from going idle

ClickHouse Datadog DBM

Database Monitoring (DBM) for ClickHouse is developed and maintained by Datadog. It works by configuring the Datadog Agent to collect system tables data from the ClickHouse instance, providing query-level performance insights similar to what the ClickHouse Cloud Console provides natively. ClickHouse has no involvement in this integration — issues should be directed to Datadog or resolved by the customer.

  • Metrics are free; the customer pays extra for logs and system tables data ingestion
  • OSS ClickHouse: fully supported
  • ClickHouse Cloud (partial support): requires datadog-cluster-agent instead of datadog-agent; will prevent the service from going idle

Community monitoring solutions

The ClickHouse community has developed comprehensive monitoring solutions that integrate with popular observability stacks. ClickHouse Monitoring provides a complete monitoring setup with pre-built dashboards. This open source project offers a quick-start approach for teams looking to implement ClickHouse monitoring with established best practices and proven dashboard configurations.

Note

Like other direct database monitoring approaches, this solution queries ClickHouse system tables directly, which prevents instances from idling and impacts cost optimization.

Billing and Usage API

The Billing & Usage API can be used to programmatically access your Cloud organization's billing and usage records. This is useful for building custom cost monitoring dashboards or integrating billing data into existing financial reporting workflows.

For full API reference, see the Billing API documentation.