-
Notifications
You must be signed in to change notification settings - Fork 110
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
Tag Google Cloud instances with the name of the test or workflow for cost management #5153
Comments
I added this ticket to the sprint, because it helps us work out how to limit Google Cloud costs. |
I'm going to move this to the next sprint. Although this is important it's not high priority for this sprint. |
This is essential for reducing Google Cloud costs, which are currently significantly larger than our budget. So if we run out of DevOps work in this sprint, let's do this next. |
I just looked at costs, and they have decreased significantly over the past week. So let's check costs during sprint planning, and set the priority of this ticket then. |
Tagging it as low for now, in the hope that costs continue to be low. |
We only need to do this if cost is a concern. |
@mpguerra it looks like cost might be a problem, so let's re-check next week, and schedule this in the next sprint if needed? We can get the CI failure rate down first, move jobs to the main branch, and make the send transaction test faster (#5015). |
Costs were reasonable for October, so we don't need to do this unless we need to do detailed cost monitoring again. |
Previous behavior: We couldn't search GCP logs using the instance name if that instance was already deleted. And if we want to know how we're spending our budget its also difficult to know if specific tests or type of instances are the one responsible for a certain % of the costs Fixes #5153 Fixses #5543 Expected behavior: Be able to search logs using the test ID or at least the github reference, and be able to group GCP costs by labels Solution: - Add labels to instances
* feat(gcp): add label to instances for cost and logs grouping Previous behavior: We couldn't search GCP logs using the instance name if that instance was already deleted. And if we want to know how we're spending our budget its also difficult to know if specific tests or type of instances are the one responsible for a certain % of the costs Fixes #5153 Fixses #5543 Expected behavior: Be able to search logs using the test ID or at least the github reference, and be able to group GCP costs by labels Solution: - Add labels to instances * chore: add Network as a label * Revert "chore: add Network as a label" This reverts commit 146f747. * Update .github/workflows/zcashd-manual-deploy.yml Co-authored-by: teor <teor@riseup.net> Co-authored-by: teor <teor@riseup.net>
Motivation
When we look at Google Cloud costs, we want to know which test or continuous deployment is causing them.
This is essential for reducing Google Cloud costs, which we significantly larger than our budget in September.
Priority
The priority of this ticket depends on Google Cloud costs from 24-30 September.
The text was updated successfully, but these errors were encountered: