Mike
Mike
We have supported one prometheus monitor multiple tidbclusters in #3155, and they have been merged into the master branch. You can use thanos example to integrate into your prometheus operator....
Now, we provide prometheus operator example https://github.com/pingcap/tidb-operator/tree/master/examples/prometheus-operator and thanos example https://github.com/pingcap/tidb-operator/tree/master/examples/monitor-with-thanos. But it is not elegant. I think we can do 1. optimize the configuration of thanos in tidbmonitor,add thanos...
> @mikechengwei Could you please help improve this example to support TiFlash, TiCDC, and Pump? Thanks! ok, one component one tidbmonitor, then thanos aggreate all tidbmonitor, right?
I do not recommend user-defined servicemonitor.
I think this requires tikv to support ip communication natively,tidb-operator can't finish this feature. I think you can try to get through the domain names of two k8s clusters.
> > I think this requires tikv to support ip communication natively,tidb-operator can't finish this feature. > > I don't think the communication part is controlled by operator, it just...
I think we can support #4472 issue.
Now this feature can use `podpatch` implement, ref: https://github.com/pingcap/tidb-operator/tree/master/examples/podpatch
Hi,do you still have questions? @VoxT
For example: pd member screenshot: pod update screenshot:( The order is pd-1 pd-0 pd-2) transfer leader log: