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

Webhook herding #9

Open
cmelone opened this issue Feb 5, 2024 · 0 comments
Open

Webhook herding #9

cmelone opened this issue Feb 5, 2024 · 0 comments
Assignees
Labels
feature New feature or request

Comments

@cmelone
Copy link
Collaborator

cmelone commented Feb 5, 2024

Problem/Opportunity Statement

Gitlab webhooks may encounter issues finding our server from time to time, and we might not be able to collect the resource usage we want.

What would success / a fix look like?

Write up a cron job that grabs all the Gitlab jobs executed in the past N hours (thinking 24) and run them through our collection function.

I'm trying to think of a good way to preprocess the jobs we actually want to collect. If we took all the jobs, that's a lot of wasted DB queries on verifying that the job is already saved. We could just grab a list of all the job ids in the database, and eliminate those from consideration on being re-processed.

@cmelone cmelone added the feature New feature or request label Feb 5, 2024
@cmelone cmelone self-assigned this Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant