en: Doc update for monitoring multiple TiDB clusters with one TidbMon…

…itor (#782)
pingcap · Oct 21, 2020 · 43ab7da · 43ab7da
1 parent 1f9c822
commit 43ab7da
Showing 1 changed file with 38 additions and 0 deletions.
diff --git a/en/monitor-using-tidbmonitor.md b/en/monitor-using-tidbmonitor.md
@@ -290,6 +290,44 @@ data:
 type: kubernetes.io/tls
  ```
 
+## Monitor multiple TiDB clusters
+
+TidbMonitor supports monitoring multiple non-TLS clusters. As for TLS-enabled clusters, it is recommended that you monitor each cluster with a separate TidbMonitor. You can use [`Thanos`](https://thanos.io/tip/thanos/getting-started.md/) to query all the monitoring data.
+
+To monitor multiple non-TLS clusters, configure the TidbMonitor CR as follows:
+
+```yaml
+apiVersion: pingcap.com/v1alpha1
+kind: TidbMonitor
+metadata:
+  name: basic
+spec:
+  clusters:
+    - name: ns1
+      namespace: ns1
+    - name: ns2
+      namespace: ns2
+  kubePrometheusURL: "your-kube-prometheus-url"
+  alertmanagerURL: "your-alert-manager-url"
+  prometheus:
+    baseImage: prom/prometheus
+    version: v2.11.1
+    service:
+      type: NodePort
+  grafana:
+    baseImage: grafana/grafana
+    version: 6.0.1
+    service:
+      type: NodePort
+  initializer:
+    baseImage: pingcap/tidb-monitor-initializer
+    version: v4.0.6
+  reloader:
+    baseImage: pingcap/tidb-monitor-reloader
+    version: v1.0.1
+  imagePullPolicy: IfNotPresent
+```
+
 ## References
 
 For more detailed API information of TidbMonitor, see [TiDB Operator API documentation](https://github.com/pingcap/tidb-operator/blob/master/docs/api-references/docs.md).