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

Provide insights about where to act to reduce impacts #429

Open
demeringo opened this issue Feb 5, 2024 · 0 comments
Open

Provide insights about where to act to reduce impacts #429

demeringo opened this issue Feb 5, 2024 · 0 comments
Labels
draft feature draft feature

Comments

@demeringo
Copy link
Collaborator

demeringo commented Feb 5, 2024

Problem

Once someone uses cloud scanner to assess environmental impacts, the next question is often "Where to act".

Solution

This is mainly an idea list / very draft feature, to be discussed and designed further prior implementation

Cloud scanner (or maybe the visualization dashboard) could help the user by

  • highlighting resources that generate the most of impacts
  • identify underutilised resources like oversized vm's (this may imply to export additional metrics like CPU usage).
  • maybe also identify old data on buckets ?

Alternatives

Suggestions could also appear in CLI output.
But implementation may differ, mainly because when using metrics, we can use native prometheus / grafana functions to filter resources or average impacts of a criteria (metric) over a period of time.

Additional context or elements

@demeringo demeringo added the draft feature draft feature label Feb 5, 2024
@demeringo demeringo changed the title Provide insights about where to reduce Provide insights about where to reduce impacts Jul 11, 2024
@demeringo demeringo changed the title Provide insights about where to reduce impacts Provide insights about where to act to reduce impacts Jul 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
draft feature draft feature
Projects
None yet
Development

No branches or pull requests

1 participant