feat(processing) Collect latency metrics from processing store #92447
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I'd like to understand the latency from processing store clusters, and we don't have any existing metrics for that.
github-actions
bot
added
the
Scope: Backend
Codecov ReportAll modified and coverable lines are covered by tests ✅ ✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #92447 +/- ##
=======================================
Coverage 87.89% 87.90%
=======================================
Files 10226 10226
Lines 585974 585977 +3
Branches 22760 22760
=======================================
+ Hits 515068 515078 +10
+ Misses 70477 70470 -7
Partials 429 429 |
evanh
approved these changes
May 29, 2025
markstory
added a commit
that referenced
this pull request
May 30, 2025
The base `Service` class requires `__all__` to be defined for metrics to be collected on methods. I missed that in #92447
markstory
added a commit
that referenced
this pull request
May 30, 2025
The base `Service` class requires `__all__` to be defined for metrics to be collected on methods. I missed that in #92447
andrewshie-sentry
pushed a commit
that referenced
this pull request
Jun 2, 2025
I'd like to understand the latency from processing store clusters, and we don't have any existing metrics for that.
andrewshie-sentry
pushed a commit
that referenced
this pull request
Jun 2, 2025
The base `Service` class requires `__all__` to be defined for metrics to be collected on methods. I missed that in #92447
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'd like to understand the latency from processing store clusters, and we don't have any existing metrics for that.