Add tracking for cron jobs

[shubham599]

Signed-off-by: Shubham Saxena s.shubham.work@gmail.com

Contributes to #127

What did you do?

Added tracking of the cron jobs (start time, end time and number of objects processed).

Why did you do it?

There were no insights on whether the cron jobs were running or not.

How have you tested it?

Yet to test...

Were docs updated if needed?

• [ ] No
• [ ] Yes
• [X] N/A

Type of change

• [ ] Bug fix (non-breaking change which fixes an issue)
• [X] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• [ ] My code follows the style guidelines of this project
• [ ] I have performed a self-review of my own code
• [ ] I have commented my code, particularly in hard-to-understand areas
• [ ] My changes generate no new console logs
• [ ] Fixes entire issue
• [ ] Partial fix for issue

[tonypearson]

20 May 2022 - Discussion between Demi, Shubham, and Tony: Great idea, but we need to avoid ever-increasing database that could grow out of control/out-of-space crash condition. Suggest we create a method on the new JobDetail class such as "cleanup" which removes any records that are in excess of six months or 100,000 records, for example. This can be invoked prior to each call in each of the three batch jobs.

[github-actions[bot]]

:wave: Hi! This pull request has been marked stale due to inactivity. If no further activity occurs, it will automatically be closed.