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-issues): Add new use case for metrics dataset #52360

Merged
merged 1 commit into from
Jul 13, 2023

Conversation

snigdhas
Copy link
Member

@snigdhas snigdhas commented Jul 6, 2023

Register a new use case for the metrics dataset to be used with escalating issues.

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jul 6, 2023
@snigdhas snigdhas marked this pull request as ready for review July 6, 2023 17:12
@snigdhas snigdhas requested a review from a team as a code owner July 6, 2023 17:12
@@ -10,13 +10,15 @@ class UseCaseID(Enum):
SPANS = "spans"
TRANSACTIONS = "transactions"
SESSIONS = "sessions"
ESCALATING_ISSUES = "escalating_issues"
Copy link
Contributor

Choose a reason for hiding this comment

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

@ayirr7 hmm do you think this dataset would be reused by others or its just this feature?

Copy link
Member

Choose a reason for hiding this comment

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

so this is the list of all existing use cases - others could hypothetically use the escalating_issues use case and send metrics onto it

@codecov
Copy link

codecov bot commented Jul 6, 2023

Codecov Report

Merging #52360 (79a1d9a) into master (b2f7b26) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files
@@           Coverage Diff            @@
##           master   #52360    +/-   ##
========================================
  Coverage   79.31%   79.31%            
========================================
  Files        4900     4909     +9     
  Lines      205043   205773   +730     
  Branches    35048    35168   +120     
========================================
+ Hits       162625   163219   +594     
- Misses      37457    37564   +107     
- Partials     4961     4990    +29     
Impacted Files Coverage Δ
static/app/components/group/releaseStats.tsx 100.00% <ø> (ø)
src/sentry/sentry_metrics/use_case_id_registry.py 93.33% <100.00%> (+0.47%) ⬆️

... and 154 files with indirect coverage changes

@snigdhas snigdhas requested a review from ayirr7 July 10, 2023 17:07
@ayirr7
Copy link
Member

ayirr7 commented Jul 10, 2023

Overall these changes look good to me, I'd recommend going through the local testing flow I described offline as well. I can approve after that goes through!

@ayirr7
Copy link
Member

ayirr7 commented Jul 11, 2023

Discussed offline that local testing was successful

@snigdhas snigdhas added this to the Escalating Issues V2 (EA) milestone Jul 12, 2023
@snigdhas snigdhas merged commit c3466dc into master Jul 13, 2023
@snigdhas snigdhas deleted the snigdha/metrics-backend branch July 13, 2023 17:42
michellewzhang pushed a commit that referenced this pull request Jul 13, 2023
Register a new use case for the metrics dataset to be used with
escalating issues.
mifu67 pushed a commit that referenced this pull request Jul 13, 2023
Register a new use case for the metrics dataset to be used with
escalating issues.
@github-actions github-actions bot locked and limited conversation to collaborators Jul 29, 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.

3 participants