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

Track financial details, including the total spend incurred by usage of the DCP in production conditions #316

Open
sampierson opened this issue Mar 5, 2019 · 2 comments

Comments

@sampierson
Copy link
Member

We need to monitor our spending and find ways to improve where possible.

Coverage is required In both AWS and GCP. Need to be able to break spend down by DCP component, and by service type (bucket storage, compute, batch, etc).

In AWS I believe this requires we tag each of our resources and then use their finance tools to mine those tags and aggregate costs. Not sure how this works in GCP.

Step 1 = research the different mechanisms in AWS / GCP.
Step 2 = design tagging strategy, detail it in the dcp repo ticket #78 (https://app.zenhub.com/workspaces/dcp-backlogs-5ac7bcf9465cb172b77760d9/issues/humancellatlas/dcp/78)
Step 3 = ping component teams to implement their part
Step 4 = ensure platform-wide tools work as advertised

@parthshahva parthshahva added the Blocked Development is blocked label Mar 6, 2019
@parthshahva parthshahva added H1 Proposed H1 task and removed Blocked Development is blocked labels Apr 16, 2019
@parthshahva
Copy link
Contributor

Discuss with Andrey how to monitor batch spot instance cost

@parthshahva parthshahva removed the H1 Proposed H1 task label May 14, 2019
@sampierson
Copy link
Member Author

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

No branches or pull requests

2 participants