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.

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(escalating-v2): Emit escalating metrics #54240

Merged
merged 14 commits into from
Aug 14, 2023
Merged

Conversation

snigdhas
Copy link
Member

@snigdhas snigdhas commented Aug 4, 2023

These changes from #52774 were reverting - undoing the revert.

Update the ESCALATING_ISSUES use case during post_process as we see new events come in.

@snigdhas snigdhas requested a review from ayirr7 August 4, 2023 22:30
@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Aug 4, 2023
@snigdhas snigdhas marked this pull request as ready for review August 4, 2023 22:35
@snigdhas snigdhas requested a review from a team as a code owner August 4, 2023 22:35
@codecov
Copy link

codecov bot commented Aug 4, 2023

Codecov Report

Merging #54240 (9aaffb5) into master (05b197d) will increase coverage by 0.01%.
Report is 78 commits behind head on master.
The diff coverage is 86.55%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #54240      +/-   ##
==========================================
+ Coverage   79.74%   79.75%   +0.01%     
==========================================
  Files        4995     5001       +6     
  Lines      212184   212322     +138     
  Branches    36168    36188      +20     
==========================================
+ Hits       169205   169339     +134     
+ Misses      37772    37765       -7     
- Partials     5207     5218      +11     
Files Changed Coverage Δ
.../api/endpoints/organization_missing_org_members.py 97.95% <ø> (ø)
src/sentry/apidocs/build.py 25.00% <ø> (ø)
src/sentry/conf/server.py 91.63% <ø> (+0.01%) ⬆️
src/sentry/monitors/models.py 92.35% <ø> (ø)
src/sentry/monitors/validators.py 91.42% <ø> (ø)
static/app/components/events/eventEntries.tsx 84.61% <ø> (ø)
static/app/components/events/userFeedback.tsx 80.00% <ø> (-3.34%) ⬇️
static/app/components/issues/groupList.tsx 58.82% <ø> (-0.90%) ⬇️
...iews/alerts/rules/metric/details/relatedIssues.tsx 58.82% <ø> (ø)
...tatic/app/views/issueDetails/groupUserFeedback.tsx 0.00% <ø> (ø)
... and 15 more

... and 42 files with indirect coverage changes

@snigdhas
Copy link
Member Author

snigdhas commented Aug 7, 2023

There's some relay tests failing because of the call to the metrics backend - @onewland @ayirr7 any chance you know how to fix these?

@ayirr7
Copy link
Member

ayirr7 commented Aug 7, 2023

@snigdhas let me look into these, though I'm not super familiar with Relay's tests

@ayirr7
Copy link
Member

ayirr7 commented Aug 8, 2023

One note in terms of the rollout of this feature, can we put it behind a feature flag?

@snigdhas
Copy link
Member Author

snigdhas commented Aug 8, 2023

@ayirr7 do you mean the changes in this PR? Or the followup PR with the query? #53177

@snigdhas
Copy link
Member Author

snigdhas commented Aug 8, 2023

@getsentry/ingest could one of y'all help figure out the tests that are failing here? I'm not sure it's specifically related to the changes in this PR - I think the tests may need to be changed a bit to support the generic metrics pipeline.

@ayirr7
Copy link
Member

ayirr7 commented Aug 8, 2023

@ayirr7 do you mean the changes in this PR? Or the followup PR with the query? #53177

I think for this PR, so that we can easily turn on/off metrics emission as needed.

@ayirr7
Copy link
Member

ayirr7 commented Aug 9, 2023

@getsentry/owners-ingest The tests are not failing now because the feature flag is not enabled, but can we have some help with the test failures? specifically https://github.com/getsentry/sentry/actions/runs/5798927319/job/15717780956?

@ayirr7
Copy link
Member

ayirr7 commented Aug 10, 2023

@snigdhas I think I might have managed to fix those tests. I think it might still be good to have someone from the relevant team to take a look and give this their approval

I still need to merge the change in the backend option in getsentry before this can be merged / will do another pass before I approve on my end.

@snigdhas snigdhas requested a review from a team August 10, 2023 23:51
@ayirr7
Copy link
Member

ayirr7 commented Aug 11, 2023

Seems like tests are passing now. I think it's a good idea to have any relevant team(s) -- Issues, Ingest -- take a look at the way the tests have been changed and get approval from them as well before merging.

@ayirr7
Copy link
Member

ayirr7 commented Aug 11, 2023

(Just fyi I will need to merge https://github.com/getsentry/getsentry/pull/11420 before this can be merged)

@@ -457,7 +461,7 @@ def test_sends_issue_notification(self, record_analytics):
assert isinstance(msg.alternatives[0][0], str)
assert "Hello world</pre>" in msg.alternatives[0][0]

attachment, text = get_attachment()
attachment, text = get_attachment(1)
Copy link
Member

@ayirr7 ayirr7 Aug 14, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we know if the response_num needs to be passed in explicitly like this still? This was a different attempt to fix the tests. From my understanding, the passthru should be sufficient for fixing the tests and we no longer need this other change.

i.e. Do all tests still pass if we don't have response_num passed in like this?

@snigdhas snigdhas merged commit 93fc8e7 into master Aug 14, 2023
56 of 57 checks passed
@snigdhas snigdhas deleted the snigdha/emit-metrics branch August 14, 2023 17:15
@github-actions github-actions bot locked and limited conversation to collaborators Aug 30, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Scope: Backend Automatically applied to PRs that change backend components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants