Skip to content

Conversation

@ksy36
Copy link
Collaborator

@ksy36 ksy36 commented Feb 4, 2026

Changes in this PR:
import_reports_from_bigquery is only saving reports to db without cluster_id or bucket_id
triage_new_reports command gets reports that don't have bucket_id and attempts to cluster and bucket them (runs every hour at the moment)

I think once we import live reports the frequency of triaging can be increased.

@ksy36 ksy36 force-pushed the incoming_clustering branch 2 times, most recently from 1ce7f27 to c515179 Compare February 10, 2026 20:43
@ksy36 ksy36 marked this pull request as ready for review February 10, 2026 20:47
@ksy36 ksy36 requested a review from jgraham February 10, 2026 20:47
@ksy36
Copy link
Collaborator Author

ksy36 commented Feb 10, 2026

I need to find a way to run cluster_reports command once to cluster existing reports on production before these changes are deployed :)

@ksy36 ksy36 force-pushed the incoming_clustering branch from c515179 to ddfcd1a Compare February 11, 2026 15:30
# triage = True
#
# if getattr(settings, "USE_CELERY", None) and triage:
# triage_new_report.apply_async((instance.pk,), countdown=0.1)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

triage_new_report was triggered once report is created or edited, I commented this out for now as triaging happens asynchronously every hour and not on creation. And we're not editing buckets/reports at the moment, but will at some point, so keeping the code just in case

@ksy36 ksy36 requested a review from denschub February 11, 2026 16:28
@ksy36 ksy36 marked this pull request as draft February 12, 2026 15:33
@ksy36 ksy36 marked this pull request as ready for review February 12, 2026 20:24
@ksy36
Copy link
Collaborator Author

ksy36 commented Feb 12, 2026

Ok I've added a page at /reportmanager/clustering/ where we can trigger full clustering and it also displays all runs, full and incremental ones (triaging new reports). We can probably display more info in the table later, if needed.

Screenshot 2026-02-12 at 3 23 56 PM

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.

1 participant