Environment
SaaS (https://sentry.io/)
Steps to Reproduce
I am creating issues via dotnet sdk. Trace data is provided via otel collector integration. Works good. However the link provided to the trace id on the issue page adds some qs filters that prevent all the child spans from being displayed. I have to edit the qs in order to view the child spans alongside the parent. For instance https://.sentry.io/explore/traces/trace//?node=error-&pageEnd=2026-05-23T20%3A59%3A58.657&pageStart=2026-05-22T20%3A59%3A58.657&project=&query=is%3Aunresolved%20issue.category%3A%5Berror%2Coutage%5D&referrer=issue-stream×tamp= does not work but https://.sentry.io/explore/traces/trace/ when pasted into the browser shows me correctly the nested spans.
Expected Result
Have the spans displayed. Its an inconvenience rather than a functional defect that cannot be worked around, but detracts from the usability and function of the service which is the reason i use it rather than rolling my own with otel + grafana.
Actual Result
child spans are not displayed. I imagine because they have been created via otel integration rather than sdk and therefore lack the meta data to match the filters in the generated link.
Product Area
Issues
Link
No response
DSN
No response
Version
No response
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
I am creating issues via dotnet sdk. Trace data is provided via otel collector integration. Works good. However the link provided to the trace id on the issue page adds some qs filters that prevent all the child spans from being displayed. I have to edit the qs in order to view the child spans alongside the parent. For instance https://.sentry.io/explore/traces/trace//?node=error-&pageEnd=2026-05-23T20%3A59%3A58.657&pageStart=2026-05-22T20%3A59%3A58.657&project=&query=is%3Aunresolved%20issue.category%3A%5Berror%2Coutage%5D&referrer=issue-stream×tamp= does not work but https://.sentry.io/explore/traces/trace/ when pasted into the browser shows me correctly the nested spans.
Expected Result
Have the spans displayed. Its an inconvenience rather than a functional defect that cannot be worked around, but detracts from the usability and function of the service which is the reason i use it rather than rolling my own with otel + grafana.
Actual Result
child spans are not displayed. I imagine because they have been created via otel integration rather than sdk and therefore lack the meta data to match the filters in the generated link.
Product Area
Issues
Link
No response
DSN
No response
Version
No response