Cannot see trace details (still)

[maciejpankanin]

Environment

self-hosted (https://develop.sentry.dev/self-hosted/)

Steps to Reproduce

I have already reported it in getsentry/sentry#51512, but the fix did not help.

1. Go to details of any trace

Expected Result

I see details of the trace

Actual Result

sentry-self-hosted-web-1  | 08:09:25 [INFO] sentry.access.api: api.access (method='GET' view='sentry.api.endpoints.organization_events_trace.OrganizationEventsTraceEndpoint' response=500 user_id='1' is_app='None' token_type='None' is_frontend_request='True' organization_id='1' auth_id='None' path='/api/0/organizations/sentry/events-trace/d81ce96c8b5e4c95931fbfdbd96cc951/' caller_ip='172.18.0.1' user_agent='Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36' rate_limited='False' rate_limit_category='None' request_duration_seconds=0.32290196418762207 rate_limit_type='DNE' concurrent_limit='None' concurrent_requests='None' reset_time='None' group='None' limit='None' remaining='None')
sentry-self-hosted-web-1  | 08:09:25 [ERROR] django.request: Internal Server Error: /api/0/organizations/sentry/events-trace/d81ce96c8b5e4c95931fbfdbd96cc951/ (status_code=500 request=<WSGIRequest: GET '/api/0/organizations/sentry/events-trace/d81ce96c8b5e4c95931fbfdbd96cc951/?detailed=1&end=2023-07-11T23%3A04%3A21.933&project=-1&query=&start=2023-07-10T23%3A04%3A21.916'>)
sentry-self-hosted-web-1  | 08:09:25 [INFO] sentry.access.api: api.access (method='GET' view='sentry.api.endpoints.organization_events_trace.OrganizationEventsTraceMetaEndpoint' response=500 user_id='1' is_app='None' token_type='None' is_frontend_request='True' organization_id='1' auth_id='None' path='/api/0/organizations/sentry/events-trace-meta/d81ce96c8b5e4c95931fbfdbd96cc951/' caller_ip='172.18.0.1' user_agent='Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36' rate_limited='False' rate_limit_category='None' request_duration_seconds=0.3541371822357178 rate_limit_type='DNE' concurrent_limit='None' concurrent_requests='None' reset_time='None' group='None' limit='None' remaining='None')
sentry-self-hosted-web-1  | 08:09:25 [ERROR] django.request: Internal Server Error: /api/0/organizations/sentry/events-trace-meta/d81ce96c8b5e4c95931fbfdbd96cc951/ (status_code=500 request=<WSGIRequest: GET '/api/0/organizations/sentry/events-trace-meta/d81ce96c8b5e4c95931fbfdbd96cc951/?end=2023-07-11T23%3A04%3A21.933&project=-1&query=&start=2023-07-10T23%3A04%3A21.916'>)

Product Area

Performance

Link

No response

DSN

No response

Version

23.6.2

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[stayallive]

Same problem, it seems related to getsentry/sentry#52712 since snuba throws a bunch of errors when accessing that page.

[stayallive]

Update, I found #2183 and running the following did indeed fix the issue:

docker-compose run --rm snuba-api migrations migrate -g search_issues --force

I am still not sure why this would be needed in the first place and seems like a bug?

[hubertdeng123]

It seems like it's because there is an exception for self-hosted, where the search_issues is not migrated
https://github.com/getsentry/snuba/blob/master/snuba/settings/settings_self_hosted.py#L22

[hubertdeng123]

Issue platform is not yet enabled for self-hosted, we may need to enable this migration for self-hosted users. I have created an issue here to track the effort:
#2269

[stayallive]

Oh, good catch!

For people not in the know (like I was) this is the "issue platfom": https://develop.sentry.dev/issue-platform/ (super dope feature)

This also looks like it might power things like performance issues?

[hubertdeng123]

I've created a PR here to run the migration for self-hosted.
getsentry/snuba#4518

[hubertdeng123]

PR has been merged.

[maciejpankanin]

Update, I found #2183 and running the following did indeed fix the issue:

docker-compose run --rm snuba-api migrations migrate -g search_issues --force

I am still not sure why this would be needed in the first place and seems like a bug?

Thanks, it worked for me.

Also @hubertdeng123 thanks for fixing, I think we can close this issue.