-
Notifications
You must be signed in to change notification settings - Fork 14
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 Monitoring #3542
Comments
Paired with @erikamov today to discuss how to control increasing costs over time. Erika will write up a brief summary for review with the group and @evansiroky. |
The brief summary is here. |
As discussed at planning, @erikamov will meet with @evansiroky and analysts to figure out the lowest-hanging fruit. After discussion, we want to discuss GTFS-RT validation outputs. |
Here a list of all buckets and BQ tables with sizes. We can use this list to define our next steps. |
To start we could change For the other DAGs that runs every day, is there a need to run on weekends (except the full refresh on Sunday)? We could also reduce how many times Change I don't want to tag anyone during holidays, so we can discuss when everybody is back, but if you see this comment please feel free to add your input. Complete list and notes to discuss are available here. |
User story / feature request
As a Cal-ITP cloud account owner,
I want to have detailed insights into cloud costs,
So that I can know what is causing our bill to get larger each month.
Acceptance Criteria
Perhaps building on top of #3541, have a way to more easily monitor the cost of various things in the pipeline at a finer-grained analysis than what is currently available in the cloud costs dashboard.
Notes
Based on this, hopefully we can reduce our bill or minimize it's growth.
The text was updated successfully, but these errors were encountered: