Skip to content

Stagger weekly Cloudwatch-heavy report jobs to not hit rate limits#11030

Merged
h-m-m merged 1 commit intomainfrom
hmm/stagger-weekly-cloudwatch
Aug 13, 2024
Merged

Stagger weekly Cloudwatch-heavy report jobs to not hit rate limits#11030
h-m-m merged 1 commit intomainfrom
hmm/stagger-weekly-cloudwatch

Conversation

@h-m-m
Copy link
Contributor

@h-m-m h-m-m commented Aug 5, 2024

🛠 Summary of changes

Staggering these jobs should be good enough. The specific times and order in which the reports run were not picked with a specific reason in mind. Feel free to suggest different times if there's a reason to.

@nprimak
Copy link
Contributor

nprimak commented Aug 5, 2024

Slack thread just to provide some more context for these changes: https://gsa-tts.slack.com/archives/CMW9H0RFX/p1722271455385999

The specific times and order in which the reports run were not picked with a specific reason in mind. Feel free to adjust the times as appropriate.

changelog: Internal, Reporting, Stagger Cloudwatch-heavy report jobs so they don't hit rate limits
@h-m-m h-m-m force-pushed the hmm/stagger-weekly-cloudwatch branch from e0c1dc0 to 45180a5 Compare August 6, 2024 16:33
@h-m-m h-m-m marked this pull request as ready for review August 13, 2024 15:56
@h-m-m h-m-m merged commit 2f991d8 into main Aug 13, 2024
@h-m-m h-m-m deleted the hmm/stagger-weekly-cloudwatch branch August 13, 2024 19:33
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