sentry
sentry copied to clipboard
Developer-first error tracking and performance monitoring
A lot of other errors are being eaten up as timeouts (e.g. rate limiting). Add the class name as a tag so we have better insight into what broke. Note:...
I added scope to the model in the previous PR but not to the serializer. Adding it now. The value is empty for every object atm.
Add logging via EventLifecycle and EventLifecycleMetric to PagerDuty and Opsgenie.
- Adds a new `ApiInvalidRequestError` type, to better differentiate between 400 and unhandled non-400 responses from downstream APIs. - Adds filtering to our ticket creation utils which only propagates `IntegrationFormErrors`...
Closes https://github.com/getsentry/sentry/issues/78591
### Environment SaaS (https://sentry.io/) ### Steps to Reproduce - Go to the issue stream in Sentry. - Add the search term "internal" or any other term in the search bar....
- Improve the throughput of the prototypes by using long lived process pools instead of making a new process for each task. - Improve the pull model by having status...
Have the new tasks contain the logic and point other refs torward the new tasks. issue ref (https://github.com/getsentry/sentry/issues/73857 )
Building off the work done in #61475 I think the plan would be to use this as a dev-ui replacement until we're more confident and can setup the getsentry repo...