Skip to content

Commit e3fecc8

Browse files
authored
cloud: Update monitor-prometheus-and-grafana-integration.md (#21907)
1 parent ff859f7 commit e3fecc8

File tree

4 files changed

+57
-20
lines changed

4 files changed

+57
-20
lines changed

tidb-cloud/monitor-datadog-integration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ TiDB Cloud has supported the project-level Datadog integration (Beta) since Marc
2020

2121
If you do not have a Datadog account, sign up at [https://app.datadoghq.com/signup](https://app.datadoghq.com/signup).
2222

23-
- To set up third-party metrics integration for TiDB Cloud, you must have the `Organization Owner` or `Project Owner` access in TiDB Cloud. To view the integration page or access configured dashboards via the provided links, you need at least the `Project Viewer` role to access the target clusters under the project in TiDB Cloud.
23+
- To set up third-party metrics integration for TiDB Cloud, you must have the `Organization Owner` or `Project Owner` access in TiDB Cloud. To view the integration page or access configured dashboards via the provided links, you need at least the `Project Viewer` role to access the target clusters under your project in TiDB Cloud.
2424

2525
## Limitation
2626

tidb-cloud/monitor-prometheus-and-grafana-integration.md

Lines changed: 53 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,44 +1,69 @@
11
---
2-
title: Integrate TiDB Cloud with Prometheus and Grafana (Beta)
2+
title: Integrate TiDB Cloud with Prometheus and Grafana
33
summary: Learn how to monitor your TiDB cluster with the Prometheus and Grafana integration.
44
---
55

6-
# Integrate TiDB Cloud with Prometheus and Grafana (Beta)
6+
# Integrate TiDB Cloud with Prometheus and Grafana
77

8-
TiDB Cloud provides a [Prometheus](https://prometheus.io/) API endpoint (beta). If you have a Prometheus service, you can monitor key metrics of TiDB Cloud from the endpoint easily.
8+
TiDB Cloud provides a [Prometheus](https://prometheus.io/) API endpoint. If you have a Prometheus service, you can monitor key metrics of TiDB Cloud from the endpoint easily.
99

1010
This document describes how to configure your Prometheus service to read key metrics from the TiDB Cloud endpoint and how to view the metrics using [Grafana](https://grafana.com/).
1111

12+
## Prometheus integration version
13+
14+
TiDB Cloud has supported the project-level Prometheus integration (Beta) since March 15, 2022. Starting from October 21, 2025, TiDB Cloud introduces the cluster-level Prometheus integration (Preview).
15+
16+
- **Cluster-level Prometheus integration (Preview)**: if no legacy project-level Prometheus integration remains undeleted within your organization by October 21, 2025, TiDB Cloud provides the cluster-level Prometheus integration (Preview) for your organization to experience the latest enhancements.
17+
18+
> **Note**
19+
>
20+
> Currently, cluster-level Prometheus integrations (Preview) are available only for TiDB Cloud Dedicated clusters hosted on AWS and Google Cloud.
21+
22+
- **Legacy project-level Prometheus integration (Beta)**: if at least one legacy project-level Prometheus integration remains undeleted within your organization by October 21, 2025, TiDB Cloud retains both existing and new integrations at the project level for your organization to avoid affecting current dashboards.
23+
1224
## Prerequisites
1325

1426
- To integrate TiDB Cloud with Prometheus, you must have a self-hosted or managed Prometheus service.
1527

16-
- To edit third-party integration settings of TiDB Cloud, you must have the `Organization Owner` access to your organization or `Project Member` access to the target project in TiDB Cloud.
28+
- To set up third-party metrics integration for TiDB Cloud, you must have the `Organization Owner` or `Project Owner` access in TiDB Cloud. To view the integration page, you need at least the `Project Viewer` role to access the target clusters under your project in TiDB Cloud.
1729

1830
## Limitation
1931

20-
- You cannot use the Prometheus and Grafana integration in [{{{ .starter }}}](/tidb-cloud/select-cluster-tier.md#starter) or [{{{ .essential }}}](/tidb-cloud/select-cluster-tier.md#essential) clusters.
21-
32+
- Prometheus and Grafana integrations now are only available for [TiDB Cloud Dedicated](/tidb-cloud/select-cluster-tier.md#tidb-cloud-dedicated) clusters.
2233
- Prometheus and Grafana integrations are not available when the cluster status is **CREATING**, **RESTORING**, **PAUSED**, or **RESUMING**.
2334

2435
## Steps
2536

2637
### Step 1. Get a scrape_config file for Prometheus
2738

28-
Before configuring your Prometheus service to read metrics of TiDB Cloud, you need to generate a `scrape_config` YAML file in TiDB Cloud first. The `scrape_config` file contains a unique bearer token that allows the Prometheus service to monitor any database clusters in the current project.
39+
Before configuring your Prometheus service to read metrics of TiDB Cloud, you need to generate a `scrape_config` YAML file in TiDB Cloud first. The `scrape_config` file contains a unique bearer token that allows the Prometheus service to monitor your target clusters.
40+
41+
Depending on your [Prometheus integration version](#prometheus-integration-version), the steps to get the `scrape_config` file for Prometheus and access the integration page are different.
42+
43+
<SimpleTab>
44+
<div label="Cluster-level Prometheus integration (Preview)">
45+
46+
1. In the [TiDB Cloud console](https://tidbcloud.com/), navigate to the [**Clusters**](https://tidbcloud.com/project/clusters) page of your project, and then click the name of your target cluster to go to its overview page.
47+
2. In the left navigation pane, click **Settings** > **Integrations**.
48+
3. On the **Integrations** page, click **Integration to Prometheus (Preview)**.
49+
4. Click **Add File** to generate and show the `scrape_config` file for the current cluster.
50+
5. Make a copy of the `scrape_config` file content for later use.
2951

30-
To get the `scrape_config` file for Prometheus, do the following:
52+
</div>
53+
<div label="Legacy project-level Prometheus integration (Beta)">
3154

3255
1. In the [TiDB Cloud console](https://tidbcloud.com), switch to your target project using the combo box in the upper-left corner.
3356
2. In the left navigation pane, click **Project Settings** > **Integrations**.
3457
3. On the **Integrations** page, click **Integration to Prometheus (BETA)**.
3558
4. Click **Add File** to generate and show the scrape_config file for the current project.
36-
3759
5. Make a copy of the `scrape_config` file content for later use.
3860

39-
> **Note:**
40-
>
41-
> For security reasons, TiDB Cloud only shows a newly generated `scrape_config` file once. Ensure that you copy the content before closing the file window. If you forget to do so, you need to delete the `scrape_config` file in TiDB Cloud and generate a new one. To delete a `scrape_config` file, select the file, click **...**, and then click **Delete**.
61+
</div>
62+
</SimpleTab>
63+
64+
> **Note:**
65+
>
66+
> For security reasons, TiDB Cloud only shows a newly generated `scrape_config` file once. Ensure that you copy the content before closing the file window. If you forget to do so, you need to delete the `scrape_config` file in TiDB Cloud and generate a new one. To delete a `scrape_config` file, select the file, click **...**, and then click **Delete**.
4267
4368
### Step 2. Integrate with Prometheus
4469

@@ -54,10 +79,13 @@ To get the `scrape_config` file for Prometheus, do the following:
5479

5580
After your Prometheus service is reading metrics from TiDB Cloud, you can use Grafana GUI dashboards to visualize the metrics as follows:
5681

57-
1. Download the Grafana dashboard JSON of TiDB Cloud [here](https://github.com/pingcap/docs/blob/master/tidb-cloud/monitor-prometheus-and-grafana-integration-grafana-dashboard-UI.json).
82+
1. Depending on your [Prometheus integration version](#prometheus-integration-version), the link to download the Grafana dashboard JSON of TiDB Cloud for Prometheus is different.
83+
84+
- For cluster-level Prometheus integration (Preview), download the Grafana dashboard JSON file [here](https://github.com/pingcap/docs/blob/master/tidb-cloud/monitor-prometheus-and-grafana-integration-tidb-cloud-dynamic-tracker.json).
85+
- For legacy project-level Prometheus integration (Beta), download the Grafana dashboard JSON file [here](https://github.com/pingcap/docs/blob/master/tidb-cloud/monitor-prometheus-and-grafana-integration-grafana-dashboard-UI.json).
86+
87+
2. [Import this JSON to your own Grafana GUI](https://grafana.com/docs/grafana/v8.5/dashboards/export-import/#import-dashboard) to visualize the metrics.
5888

59-
2. [Import this JSON to your own Grafana GUI](https://grafana.com/docs/grafana/v8.5/dashboards/export-import/#import-dashboard) to visualize the metrics.
60-
6189
> **Note:**
6290
>
6391
> If you are already using Prometheus and Grafana to monitor TiDB Cloud and want to incorporate the newly available metrics, it is recommended that you create a new dashboard instead of directly updating the JSON of the existing one.
@@ -73,7 +101,7 @@ To improve data security, it is a general best practice to periodically rotate `
73101
1. Follow [Step 1](#step-1-get-a-scrape_config-file-for-prometheus) to create a new `scrape_config` file for Prometheus.
74102
2. Add the content of the new file to your Prometheus configuration file.
75103
3. Once you have confirmed that your Prometheus service is still able to read from TiDB Cloud, remove the content of the old `scrape_config` file from your Prometheus configuration file.
76-
4. On the **Integrations** page of your project, delete the corresponding old `scrape_config` file to block anyone else from using it to read from the TiDB Cloud Prometheus endpoint.
104+
4. On the **Integrations** page of your project or cluster, delete the corresponding old `scrape_config` file to block anyone else from using it to read from the TiDB Cloud Prometheus endpoint.
77105

78106
## Metrics available to Prometheus
79107

@@ -104,6 +132,15 @@ Prometheus tracks the following metric data for your TiDB clusters.
104132
| tidbcloud_resource_manager_resource_unit_read_request_unit | gauge | cluster_name: `<cluster name>`<br/>resource_group: `<group-name>` | The read request units consumed by Resource Manager |
105133
| tidbcloud_resource_manager_resource_unit_write_request_unit | gauge | cluster_name: `<cluster name>`<br/>resource_group: `<group-name>` | The write request units consumed by Resource Manager |
106134

135+
For cluster-level Prometheus integration, the following additional metrics are also available:
136+
137+
| Metric name | Metric type | Labels | Description |
138+
|:--- |:--- |:--- |:--- |
139+
| tidbcloud_dm_task_status | gauge | instance: `instance`<br/>task: `task`<br/>cluster_name: `<cluster name>` | Task state of Data Migration:<br/>0: Invalid<br/>1: New<br/>2: Running<br/>3: Paused<br/>4: Stopped<br/>5: Finished<br/>15: Error |
140+
| tidbcloud_dm_syncer_replication_lag_bucket | gauge | instance: `instance`<br/>cluster_name: `<cluster name>` | Replicate lag (bucket) of Data Migration. |
141+
| tidbcloud_dm_syncer_replication_lag_gauge | gauge | instance: `instance`<br/>task: `task`<br/>cluster_name: `<cluster name>` | Replicate lag (gauge) of Data Migration. |
142+
| tidbcloud_dm_relay_read_error_count | count | instance: `instance`<br/>cluster_name: `<cluster name>` | The number of failed attempts to read binlog from the master. |
143+
107144
## FAQ
108145

109146
- Why does the same metric have different values on Grafana and the TiDB Cloud console at the same time?

tidb-cloud/monitoring-concepts.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,6 @@ TiDB Cloud lets you integrate any of the following third-party metrics services
3939

4040
- [Datadog integration](/tidb-cloud/monitor-datadog-integration.md)
4141

42-
- [Prometheus and Grafana integration (Beta)](/tidb-cloud/monitor-prometheus-and-grafana-integration.md)
42+
- [Prometheus and Grafana integration](/tidb-cloud/monitor-prometheus-and-grafana-integration.md)
4343

4444
- [New Relic integration](/tidb-cloud/monitor-new-relic-integration.md)

tidb-cloud/third-party-monitoring-integrations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ summary: Learn how to use third-party metrics integrations.
88
You can integrate TiDB Cloud with the following third-party metrics services to receive TiDB Cloud alerts and view the performance metrics of your TiDB cluster in these services:
99

1010
- [Datadog integration](#datadog-integration)
11-
- [Prometheus and Grafana integration (Beta)](#prometheus-and-grafana-integration-beta)
11+
- [Prometheus and Grafana integration](#prometheus-and-grafana-integration)
1212
- [New Relic integration](#new-relic-integration)
1313

1414
## Datadog integration
@@ -17,7 +17,7 @@ With the Datadog integration, you can configure TiDB Cloud to send metric data a
1717

1818
For the detailed integration steps and a list of metrics that Datadog tracks, refer to [Integrate TiDB Cloud with Datadog](/tidb-cloud/monitor-datadog-integration.md).
1919

20-
## Prometheus and Grafana integration (Beta)
20+
## Prometheus and Grafana integration
2121

2222
With the Prometheus and Grafana integration, you can get a `scrape_config` file for Prometheus from TiDB Cloud and use the content from the file to configure Prometheus. You can view these metrics in your Grafana dashboards.
2323

0 commit comments

Comments
 (0)