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

Cost Explorer API (9/n): adopt strategy for total costs #4787

Closed
Tracked by #4453
consideRatio opened this issue Sep 11, 2024 · 0 comments · Fixed by #4846
Closed
Tracked by #4453

Cost Explorer API (9/n): adopt strategy for total costs #4787

consideRatio opened this issue Sep 11, 2024 · 0 comments · Fixed by #4846
Assignees

Comments

@consideRatio
Copy link
Contributor

consideRatio commented Sep 11, 2024

Definition of done

  • Let aws-ce-grafana-backend acquire data for the daily total costs by filtering based on tags below, combined with logical OR.

    Based on a given cluster name, such as openscapeshub, the known 2i2c infra total can be calculated using the tag filter:

    • alpha.eksctl.io/cluster-name=<cluster-name>
    • kubernetes.io/cluster/<cluster-name>=owned
    • 2i2c.org/cluster-name (for openscapes this needs to be 2i2c:node-purpose=<any value> until k8s upgrades re-creates all nodes)
    • 2i2c:hub-name=<any value>
  • The labels should be made configurable
  • A manually defined grafana dashboard should be examplified to function against the backend. This should be panel 4 in [EPIC] Support attributing costs to individual hubs automatically on Openscapes #4453 (comment).
    image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant