getsentry / getsentry/sentry

Sentry didn't show me any endpoint nor function regression issues

Open
#75,407 4 comments 1 reaction 0 assignees View on GitHub
Improvement Product Area: Issues
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

When looking at data in my Sentry `gibpotato-backend` project, I always filter globally on my `production` environment.
This is mainly due to me also emitting errors and traces locally, but under the `local` environment, so I don't want to mess up my views with data from both environments.

I was wondering for quite a while now why I never saw a single endpoint regression nor a function regression issue.

It turns out that these issues are only visible if I do not select any environment (All Envs).

Because of that, I completely missed this [function regression]() and also missed this [endpoint regression]().

What makes matters even worse is that my alerts aren't firing either, as I also scoped them on the `production` environment only.

### Issues filtered on the production environment

![Image](https://uploads.linear.app/3ed206af-f87a-40aa-82a0-150bf83e43e6/72194d3c-8227-4d1f-b303-68747ff750a5/6e9d5639-f761-4e94-bb60-525fa7a7d912?signature=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJwYXRoIjoiLzNlZDIwNmFmLWY4N2EtNDBhYS04MmEwLTE1MGJmODNlNDNlNi83MjE5NGQzYy04MjI3LTRkMWYtYjMwMy02ODc0N2ZmNzUwYTUvNmU5ZDU2MzktZjc2MS00ZTk0LWJiNjAtNTI1ZmE3YTdkOTEyIiwiaWF0IjoxNzc1NzY1MjQzLCJleHAiOjE4MDczMzU4MDN9.JhmnV68DF0Ut1aj_wr8Tbm-KUNhAKooPAuL3HfHKzd0)

### Issues not filtered on any environments

![Image](https://uploads.linear.app/3ed206af-f87a-40aa-82a0-150bf83e43e6/71826934-ca1b-45b0-9741-6f69a903a635/b0fd30ec-f3c0-4d0b-964f-ec44ed6971ec?signature=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJwYXRoIjoiLzNlZDIwNmFmLWY4N2EtNDBhYS04MmEwLTE1MGJmODNlNDNlNi83MTgyNjkzNC1jYTFiLTQ1YjAtOTc0MS02ZjY5YTkwM2E2MzUvYjBmZDMwZWMtZjNjMC00ZDBiLTk2NGYtZWM0NGVkNjk3MWVjIiwiaWF0IjoxNzc1NzY1MjQzLCJleHAiOjE4MDczMzU4MDN9.bZY64sv8KmZVQXLAL_FKkE_eixXghpY4RIDHVuvvaC4)

In case of the endpoint regression, the detected change in duration is quite severe going from `12ms to 131ms (+959,18%)`. And I was completely unaware that this is happening.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.