This message was deleted.
# general
s
This message was deleted.
a
It probably is due to the size of data in 1 trace. The API call might return MBs of data which crashes a browser tab. We would have to include some sort of pagination to display say 1K spans in one view.
👍 1
It could be handled by backend of we can send the spanID around which we want to visualize more spans.
👍 1
I think anyhow 100K spans in 1 go won't be that useful