-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Make error.main_thread searchable on Discover and Issues page #46183
Conversation
Do I need to add |
Do I need to add |
I'm not adding a |
My PR is basically looking at |
@evanh or @untitaker would any of you be able to help me out with all those open questions? thanks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not familiar with the event_attribute code, but for discover all you should need to do is update src/sentry/snuba/events.py
if there's no post-processing required
Do I need to change |
Yes
No, filter.py is deprecated by
No, from your other answer where this is just a boolean field, all you should need to do is update snuba.py -- see the previous answer for when you need to update those two files |
Alright, thanks, this has to be searchable on the Alert and Issues page as well, is there anyone that knows how this work? my tests are still broken, so I'm unsure what is wrong or what I have to do. |
@barkbarkimashark @wmak tests are green and this is ready for approval/merging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes to discover code look good to me, a reminder you'll need to update the frontend too to see error.main_thread in autocompletes etc.
Depends on getsentry/snuba#3863