Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split environmental impact by K8s pod usage #476

Open
damienfernandes opened this issue Mar 20, 2024 · 0 comments · May be fixed by #477
Open

Split environmental impact by K8s pod usage #476

damienfernandes opened this issue Mar 20, 2024 · 0 comments · May be fixed by #477

Comments

@damienfernandes
Copy link
Contributor

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

@damienfernandes damienfernandes linked a pull request Mar 20, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant