Stracktrace in_app directives sent properly but ignored in Sentry
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 10m
- Merged PRs (30d)
- 635
Description
### Environment
self-hosted (https://develop.sentry.dev/self-hosted/)
### Steps to Reproduce
1. Sentry 25.9.0 / Laravel-Sentry 4.22.0
2. Configure in_app_include, e.g:
```php
'in_app_include' => [base_path('vendor/custom_one'),],
```
4. Trigger any exception
5. Check sentry json before send:
```json
# exception > values > stacktrace > frames > [{
"filename": "\/vendor\/custom_one\/File.php",
"lineno": 35,
"in_app": true,
"abs_path": "\/var\/www\/vendor\/custom_one/File.php",
```
Doesn't seem to be an SDK issue since "in_app" are sent
### Expected Result
All frames starting with "/vendor/custom_one" are shown by default and have an extra "In App" label
### Actual Result
Frames starting with "/vendor/custom_one" are hid by default, no "In App" label next to it
### Product Area
Issues
### Link
_No response_
### DSN
_No response_
### Version
25.9.0
Contributor guide
Research direction
Reproduce the behavior with Sentry 25.9.0 and Laravel-Sentry 4.22.0 using the shown in_app_include configuration. Compare the submitted stacktrace frames with how the Issues product displays frames, focusing on the in_app field, hidden frames, and the missing In App label. Done means matching frames are shown by default with the label.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, php, python
- Domain
- frontend, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100