You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm opening the issue more to see the appetite for this in the community. OpenTelemetry-Collector has several components that gather statistics about host, kubernetes itself and can be potential replacements for node-exporter, cAdvisor, kube-state-metrics, etc. Potentially we could reduce the amount of components in the stack if we just use the collector, sending all metrics to Prometheus of course.
I'm not yet sure how this change could affect the stack, but some things to keep an eye on:
Potential metric name differences.
Extra attention to which OTel resource attributes can be safely promoted to labels.
What would we need to propose to upstream mixins to make this doable?
The text was updated successfully, but these errors were encountered:
I'm opening the issue more to see the appetite for this in the community. OpenTelemetry-Collector has several components that gather statistics about host, kubernetes itself and can be potential replacements for node-exporter, cAdvisor, kube-state-metrics, etc. Potentially we could reduce the amount of components in the stack if we just use the collector, sending all metrics to Prometheus of course.
I'm not yet sure how this change could affect the stack, but some things to keep an eye on:
The text was updated successfully, but these errors were encountered: