Idea: Otel native mixins #12281
Description
What is the problem you are trying to solve?
Hello,
I am using OpenTelemetry to gather metrics (both system and application metrics) in our k8s environments. As of now we rely on common prometheus based system/api metrics such as kube_state_metrics , node_exporter and kubelet/cadvisor metrics in a lot of our dashboards and rules/alerts. But, we are gradually moving towards a more Otel native setup since their k8scluster, kubelet and hostmetrics collector receivers somewhat replaces the need of the projects/metrics metioned above. As of today, Mimirs mixins depends on all of the mentioned projects/metrics, and hence is a blocker for fully transition over to a more otel native approach.
Which solution do you envision (roughly)?
Either, add a set of mixins that is based on the otel native metrics from k8scluster, kubelet and hostmetrics receivers.
Have you considered any alternatives?
An alternative is to have a set of mixins that don't rely on kube_state_metrics , node_exporter and kubelet/cadvisor metrics. This would probably make the dashboards/alerts suboptimal as the you don't get the same insights in to how mimir performes, but then again, often times you have othe cluster wide dashboards/alerts unrelated to Mimir that can provide this kind of information about all services running in the cluster.
Any additional context to share?
No response
How long do you think this would take to be developed?
Not sure
What are the documentation dependencies?
https://grafana.com/docs/mimir/latest/manage/monitor-grafana-mimir/deploying-monitoring-mixin/
Proposer?
No response