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.

Sign up for GitHub

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

Jump to bottom

Optimize Crashlytics fetches #730

Merged
merged 4 commits into from
Feb 4, 2025
Merged

Optimize Crashlytics fetches #730

merged 4 commits into from
Feb 4, 2025

Conversation

kitallis
Copy link
Member

@kitallis kitallis commented Feb 3, 2025 •
edited
Loading

This is a simple optimization on two-levels:

  1. Include a start date before querying for crash/analytics data from BigQuery. The start date is the day when the store rollout gets created.
  2. Flag off apps if the monitoring_disabled feature flag is enabled for them. This helps us easily stop/start the apps that use Crashlytics for which the queries are too expensive.

@kitallis kitallis marked this pull request as ready for review February 3, 2025 14:34
@kitallis kitallis merged commit ab7bf87 into main Feb 4, 2025
4 checks passed
@kitallis kitallis deleted the optimize-crashlytics-p1 branch February 4, 2025 07:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@kitallis