chore(ACI): Update metric issue dual processing metrics #92076
Merged
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
github-actions
bot
added
the
Scope: Backend
saponifi3d
approved these changes
May 21, 2025
Codecov ReportAll modified and coverable lines are covered by tests ✅
|
ceorourke
force-pushed
the
ceorourke/update-dual-proc-metrics
branch
from
6f31139 to
7b04255
Compare
andrewshie-sentry
pushed a commit
that referenced
this pull request
Jun 2, 2025
Follow up to #91979 to only track when there is at least one action in `process_workflows` and differentiate between fires and resolves in the subscription processor. Previously I wanted them added together but now that we've realized we're not reaching `process_workflows` for resolutions I want to be able to determine if the number of fires is accurate.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Follow up to #91979 to only track when there is at least one action in
process_workflowsand differentiate between fires and resolves in the subscription processor. Previously I wanted them added together but now that we've realized we're not reachingprocess_workflowsfor resolutions I want to be able to determine if the number of fires is accurate.