Developer-first error tracking and performance monitoring
By: @scttcper (#58638, #58615)
By: @DominikB2014 (#58939, #58937, #58891, #58785, #58768, #58792, #58770)
File
to EventAttachment
(#59845) by @SwatinemPlus 1016 more
IncidentTrigger
model (#58467) by @isabellaenriquezPlus 209 more
By: @17hogeju (#57522)
By: @scttcper (#56700)
By: @snigdhas (#57053, #56717, #56621)
@sentry
SDKs to v7.74.0 (#58198) by @billyvgPlus 1060 more
Plus 46 more
By: @chloeho7 (#54286)
With the new 2023 grouping config, we started incurring a higher processing cost per saved event. In order to bring it back under controlled a series of code changes will be perform to improve the understandability of the code and its performance.
By: @armenzg (#53643)
By: @scttcper (#56280, #56151, #56141, #55937, #55479, #55366, #54891, #54809)
check_missing
task to each monitor_environment
(#55924) by @rjo100Plus 1078 more
By: @chloeho7 (#54734, #54655, #54589, #54640, #54466, #54348, #54339, #53522, #54234)
By: @scttcper (#54744)
Plus 424 more
By: @chloeho7 (#54001)
With the new 2023 grouping config, we started incurring a higher processing cost per saved event. In order to bring it back under controlled a series of code changes will be perform to improve the understandability of the code and its performance.
By: @armenzg (#53645, #53541)
Plus 400 more
This will allow marking an issue as archived until escalating.
By: @scttcper (#53011)
This is a placeholder milestone for tracking post-v1 work for escalating issues. See the RFC: https://github.com/getsentry/rfcs/blob/main/text/0078-escalating-issues.md There's also discussions about escalation in here: https://github.com/getsentry/sentry/discussions/43039
V2 will focus on moving ongoing issues (upcoming) into the state archived-until-escalating after an issue being in the ongoing
state for 14 days.
By: @snigdhas (#52774)
comment.after_n_builds
value (#53488) by @lobsterkatiePlus 399 more
This is a placeholder milestone for tracking post-v1 work for escalating issues. See the RFC: https://github.com/getsentry/rfcs/blob/main/text/0078-escalating-issues.md There's also discussions about escalation in here: https://github.com/getsentry/sentry/discussions/43039
V2 will focus on moving ongoing issues (upcoming) into the state archived-until-escalating after an issue being in the ongoing
state for 14 days.
By: @snigdhas (#52360)
Make common searches more accessible and discoverable for users. notion page
By: @scttcper (#52414, #52348)
Plus 434 more
This will allow marking an issue as archived until escalating.
By: @scttcper (#51765, #51852, #52048, #51766, #51735, #51671, #51158, #51185, #51187)
Added new language/platform specific stack trace grouping enhancements rules that should make the default grouping experience better. This includes JavaScript, Python, PHP, Go, Java and Kotlin.
By: @armenzg (#51040)
Make common searches more accessible and discoverable for users. notion page
By: @scttcper (#51564, #51565, #51194)
Plus 790 more