OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase Cloud

  • Overview
  • Schema evolution
    • Liquibase
    • Flyway
  • Data ingestion
    • Canal
    • dbt
    • Debezium
    • Flink
    • Glue
    • Informatica Cloud
    • Kafka
    • Maxwell
    • SeaTunnel
    • DataWorks
    • NiFi
  • SQL development
    • DataGrip
    • DBeaver
    • Navicat
    • TablePlus
  • Orchestration
    • DolphinScheduler
    • Linkis
    • Airflow
  • Visualization
    • Grafana
    • Power BI
    • Quick BI
    • Superset
    • Tableau
  • Observability
    • Datadog
    • Prometheus
  • Database management
    • Bytebase
  • AI
    • LlamaIndex
    • Dify
    • LangChain
    • Tongyi Qianwen
    • OpenAI
    • n8n
    • Trae
    • SpringAI
    • Cline
    • Cursor
    • Continue
    • Toolbox
    • CamelAI
    • Firecrawl
    • Hugging Face
    • Ollama
    • Google Gemini
    • Cloudflare Workers AI
    • Qoder
    • OpenCode
    • Claude Code
    • GitHub Copilot
    • Codex
    • Jina AI
    • Augment Code
    • Claude Code
    • Kiro
  • Development tools
    • Cloudflare Workers
    • Vercel

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Cloud

Monitor data of OceanBase Cloud with Datadog

Last Updated:2026-09-04 07:03:30

Background information
Prerequisites
Configure integration with Datadog
Delete Datadog configuration
Available monitoring metrics
Common issues

This topic explains how to monitor OceanBase Cloud instances using Datadog.

Background information

Datadog is a comprehensive cloud monitoring and analytics platform that provides developers and IT operations teams with real-time insights into the status of their entire technology stack, including applications, services, servers, and containers. Since its creation in 2010, Datadog has rapidly grown to become a popular monitoring solution, especially in cloud computing environments and microservice architectures.

OceanBase Cloud supports integration with Datadog, allowing you to push monitoring data from database clusters to the Datadog platform. The integration process uses OAuth to connect with Datadog, eliminating the need to input an API key, which makes the integration more secure and convenient. Datadog authorization is bound to the OceanBase Cloud user, so the user must have the required roles, such as Project Admin, Instance Admin, or Data Read/Write role. If you are monitoring instances from multiple projects, the user must be granted permissions for each project.

Note

Data push is currently only supported for Dedicated instances.

Prerequisites

The account to be bound must have instance permissions, and the project member must have one of the following roles: Project Admin, Instance Admin, or Data Read/Write. For detailed information on project member permissions, please refer to Manage members.

Configure integration with Datadog

  1. Visit the Datadog Console and log in to your Datadog account.

  2. Complete the configuration in the OceanBase Cloud console.

    1. Navigate to the OceanBase Cloud console.

    2. Click Integrations in the left-side navigation pane.

    3. On the Integrations page, search for Datadog, and click Datadog to open the details page.

    4. Click Connect.

    5. On the authorization page, review the authorization details and click Authorize.

      Note

      This authorization page will only appear the first time you authorize. Subsequent authorizations will simply notify you of success or failure.

  3. In the Datadog console, navigate to Integrations and search for OceanBase. Add the OceanBase Cloud Dashboard.

    After completing the configuration, you will be able to see OceanBase Cloud’s instance monitoring data in the dashboard.

    Note

    It may take a few minutes for monitoring data to be pushed to Datadog after the initial configuration.

Delete Datadog configuration

  1. Navigate to the OceanBase Cloud console.

  2. Click Integrations in the left-side navigation pane.

  3. On the Integrations page, search for Datadog, and click Datadog to open the details page.

  4. Click Remove. After deletion, OceanBase Cloud will stop pushing monitoring data to Datadog.

  5. Delete the OceanBase API key in the Datadog console.

    Note

    After clicking Remove, you will also need to delete the Datadog API key. Otherwise, clicking Connect again will result in an error.

    1. Log in to the Datadog console.

    2. Navigate to Organization Settings > API Keys.

    3. Delete the corresponding API key under your profile.

Available monitoring metrics

Metric name
Description
all_session Current session count
clog_trans_log_total_size Size of transaction logs submitted per second
cpu_percent CPU usage rate
load1 System average load over the past 1 minute
memory_used Physical memory usage
net_throughput Network throughput rate
ob_clog_disk_percent OceanBase log disk usage rate
ob_data_disk_percent Disk usage rate
ob_process_exists OceanBase process status
request_queue_time Time SQL requests spent in the wait queue
sql_all_count Number of SQL statements processed per second
sql_all_rt Average SQL statement processing time
transaction_count Number of transactions processed per second
transaction_rt Average transaction processing time on the server
trans_commit_log_count Number of transaction logs submitted per second

Common issues

Q: The following error occurs when clicking Connect: Authentication failed, please contact technical support.

A: This might occur because multiple Datadog accounts belong to the same organization, and only one account can successfully apply for an API key. You need to check the API keys information in Datadog to see if an OceanBase API key is already bound.

Previous topic

Tableau
Last

Next topic

Prometheus
Next
on this page
Background information
Prerequisites
Configure integration with Datadog
Delete Datadog configuration
Available monitoring metrics
Common issues