Track Batch scheduling costs
Problem to solve
Right now we do not have a comfortable way of testing if schedules are actually needed, this impacts product costs as computing power for unneeded jobs is still being used.
Intended users
Developers
Permissions and Security
N/A
Proposal
Let's look for ways to keep a strict tracking of schedules, ideally:
- Force developers to provide metadata explaining why each schedule is required.
- Force developers to review which schedules are still needed on a monthly basis.
Test plan
N/A
Steps
-
Make sure that the code contributions checklist has been followed.
What does success look like, and how can we measure that?
-
Implement metadata for schedules module. -
Update metadata for all schedules -
Implement CI check for requiring metadata for each schedules module. -
Implement CI check for each product pipeline that forces reviewing every related schedule on a monthly basis. -
Remove unneeded schedules. -
Update batch documentation on maintaining schedules meta.
Links / references
Edited by Daniel Salazar