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

chore(similarity): Add metric for no stacktrace frame #73514

Closed
wants to merge 2 commits into from

Conversation

jangjodi
Copy link
Member

@jangjodi jangjodi commented Jun 28, 2024

Add metric for when an event has a non-empty stacktrace string that we'd send to seer, but has no stacktrace frames
Limit metric to backend calls

@github-actions github-actions bot added the Scope: Backend Automatically applied to PRs that change backend components label Jun 28, 2024
@jangjodi jangjodi marked this pull request as ready for review June 28, 2024 16:35
@jangjodi jangjodi requested a review from a team June 28, 2024 16:35
"grouping.similarity.no_contributing_stacktrace_frame",
# TODO: Consider lowering this (in all the spots this metric is
# collected) once we roll Seer grouping out more widely
sample_rate=1.0,
Copy link
Member

Choose a reason for hiding this comment

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

Not necessary as a part of this change - we have a handful of these high sample rates, thoughts on having a single ML grouping sample rate setting somewhere that we can lower/change over time?

Copy link
Member

Choose a reason for hiding this comment

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

Yeah, I did that here. It's only used for the one metric, but we could make it more general.

@jangjodi, if you want to go ahead and get this merged, I can handle doing that.

Copy link
Member Author

Choose a reason for hiding this comment

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

Sounds good, thanks @lobsterkatie

Copy link

codecov bot commented Jun 28, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.01%. Comparing base (4bb6ded) to head (d5324ea).
Report is 760 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #73514      +/-   ##
==========================================
- Coverage   78.02%   78.01%   -0.01%     
==========================================
  Files        6638     6638              
  Lines      296818   296821       +3     
  Branches    51115    51116       +1     
==========================================
- Hits       231582   231572      -10     
- Misses      58965    58976      +11     
- Partials     6271     6273       +2     
Files Coverage Δ
...y/api/endpoints/group_similar_issues_embeddings.py 100.00% <100.00%> (ø)
src/sentry/seer/similarity/utils.py 100.00% <100.00%> (ø)

... and 9 files with indirect coverage changes

@getsantry
Copy link
Contributor

getsantry bot commented Jul 20, 2024

This pull request has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you add the label WIP, I will leave it alone unless WIP is removed ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

@getsantry getsantry bot added the Stale label Jul 20, 2024
@getsantry getsantry bot closed this Jul 28, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Aug 12, 2024
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 Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants