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

Inventory monitoring jobs #3861

Merged
merged 1 commit into from
Aug 25, 2023
Merged

Conversation

cielf
Copy link
Collaborator

@cielf cielf commented Aug 25, 2023

Description

These jobs are used to monitor the "inventory drift" problem.

Whenever we've thought we have solved it, I've been running these jobs on a regular (daily? weekly?) basis to confirm. Until we see there is another problem, or some reasonable time (a couple of months) has passed.

Core team use only, as they are meaningless without production data.

There are additional steps, of course, which are in the comments on the jobs.

Type of change

  • New feature (non-breaking change which adds functionality)

How Has This Been Tested?

I've been using them for awhile -- They have been useful in finding incidents?

@dorner
Copy link
Collaborator

dorner commented Aug 25, 2023

These are only being called when run manually on development, correct? Seems pretty safe to me

@cielf
Copy link
Collaborator Author

cielf commented Aug 25, 2023

That's correct. I've been running them on dev against a prod copy (though I admit, I didn't run them after I copied them over to this branch).

@dorner dorner merged commit cc38093 into rubyforgood:main Aug 25, 2023
11 checks passed
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

Successfully merging this pull request may close these issues.

2 participants