-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
chore(weekly reports): Add more logs #29819
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thoughts on putting something in prepare_organization_report
to the effect of "started computing reports for x org"? That way, we'll know it ran for the org and will allow us to reduce the surface area of the investigation.
I also assume you've tested this locally with settings like https://github.com/getsentry/getsentry/pull/6568? |
05c0248
to
738680f
Compare
@manuzope I've been trying to test this locally and haven't gotten anywhere, I'm not sure if this is just something you can't test locally or I'm not doing something right. I deployed the getsentry PR and changed my local org slug to one in the list, ran the task manually and it fails to find my organization in the feature list. I've also ran the I read through the feature flag docs and removed the At this point (2 on Friday) I might just deploy this PR soon if I haven't heard back from anyone on how to test this locally and hope for the best on Monday, because I am out of ideas. |
Missing weekly reports still elude me, so I'm adding more logs behind a feature flag to get more data.