-
Notifications
You must be signed in to change notification settings - Fork 6
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
feat: add metrics for sync engine slow and incremental - RC (WPB-11199) #3090
Conversation
…3086) * feat: add base for metrics, implement in slow sync * feat: add base for metrics, implement in slow sync * feat: add metrics for slow sync and improve json log * feat: incremental sync logs * feat: incremental sync logs * feat: incremental sync logs, improv for foreground * feat: refactor some naming to clarify * feat: refactor some naming to clarify * feat: docs
Quality Gate passedIssues Measures |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release/candidate #3090 +/- ##
=====================================================
+ Coverage 52.57% 52.60% +0.03%
=====================================================
Files 1319 1320 +1
Lines 51475 51515 +40
Branches 4778 4779 +1
=====================================================
+ Hits 27065 27102 +37
- Misses 22449 22451 +2
- Partials 1961 1962 +1
... and 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
Datadog ReportBranch report: ✅ 0 Failed, 3145 Passed, 107 Skipped, 30.89s Total Time |
internal enum class SyncStatus { | ||
STARTED, | ||
COMPLETED | ||
} |
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.
No failed status ?
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.
Yup, we don't need for the metrics we want to get, and as well the job cancellation (coroutine failure) can happen in another layer different from this.
What we want to achieve with this, is to measure and answer the questions:
- How much it takes to perform a sync? By type
- How many syncs started and never ended ? (this is the path we are trying to investigate and includes implicitly failures as well)
Cherry-pick of:
PR Submission Checklist for internal contributors
The PR Title
SQPIT-764
The PR Description
What's new in this PR?
Issues
We are somehow blind in some places regarding sync
Causes (Optional)
Difficulty to troubleshoot sync problems, and no metrics regarding this, like we have in other places for example for events.
Solutions
.runningFold
Testing
Test Coverage (Optional)
How to Test
Interact with the app and see logs formatted in Datadog (not available if you don't have local setup of credentials)
Notes (Optional)
Dashboards in DD will follow.
https://app.datadoghq.eu/dashboard/crc-suh-fq6/android-sync-manager-performance?fromUser=false&refresh_mode=sliding&from_ts=1730463823807&to_ts=1730478223807&live=true
PR Post Submission Checklist for internal contributors (Optional)
PR Post Merge Checklist for internal contributors
References
feat(conversation-list): Sort conversations by most emojis in the title #SQPIT-764
.