xieziyu
如何使用后台获取的数据
Something to double-check for whoever works on this: do we need to add all of these metrics as individual time series? Let's make sure we focus on adding low-level, flexible time series that can be composed to produce useful higher level metrics.
For anyone working with crossplane https://github.com/crossplane-contrib/x-metrics might provide useful metrics to aggregate the requested metrics.
@ezgidemirel, from your experience and knowledge, how much hope is there to see this or something similar implemented in Crossplane? 🙏🏻
Thank you. ❤️
From an observability point of view Crossplane so far is lacking a good strategy to monitor the MRs and claims in "kubernetes native way".
It is hard to track the overall health of an environment without understanding if just one single claim or MR is not synched or suddenly hundreds of them are not synched.
It is currently also hard to understand adoption of Crossplane in a bigger environment: if you can't pinpoint which compositions are used the most.
Hi @pierluigilenoci, as we discussed in the slack thread, I'm closing this issue as completed.
We have introduced MR metrics with #683 but decided not to add MR names, claim names or composite names to the exposed metrics as labels. The reason is, we don't want to create a metric for each managed resource created on the cluster. This will increase the cardinality dramatically. You can see more details in the comment here.
Further discussions about having more detailed metrics can be carried on within this issue.
