In eco-design thinking, when we deploy microservices in Kubernetes, it will be interesting to be able to split data by pod usage.
During a use case scenario, it will help to identify technical or functional deployment who impact the most environment with multi-criteria view
Solution
I proposed to used a node exporter outside cloud-scanner to scrap data K8s data usage in a prometheus database.
Cloud scanner will be able to call k8s pormetheus data and split by usage cloud instance impact.
Problem
In eco-design thinking, when we deploy microservices in Kubernetes, it will be interesting to be able to split data by pod usage. During a use case scenario, it will help to identify technical or functional deployment who impact the most environment with multi-criteria view
Solution
I proposed to used a node exporter outside cloud-scanner to scrap data K8s data usage in a prometheus database. Cloud scanner will be able to call k8s pormetheus data and split by usage cloud instance impact.
Alternatives
Use "OpenTelemetry Metrics Exporter - Prometheus"
Additional context or elements
Deployment level could be a plus