-
Notifications
You must be signed in to change notification settings - Fork 10.6k
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: improve omni queue metrics query #33159
Conversation
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: 0ed4cde The changes in this PR will be included in the next version bump. This PR includes changesets to release 32 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #33159 +/- ##
========================================
Coverage 59.33% 59.33%
========================================
Files 2546 2546
Lines 63242 63235 -7
Branches 14217 14214 -3
========================================
- Hits 37525 37521 -4
+ Misses 23015 23014 -1
+ Partials 2702 2700 -2
Flags with carried forward coverage won't be shown. Click here to find out more. |
e627bd5
to
ba18fc5
Compare
ba18fc5
to
0ed4cde
Compare
Proposed changes (including videos or screenshots)
The results should be the same but the pipeline structure is better for consuming less memory between stages.
Although the commits don't show it, I have added a few test cases for the endpoints that uses the query. I have then ran the tests against the old query and the new query.
Issue(s)
OPI-40
Steps to test or reproduce
Further comments