Is there a way for the Trace Details view to lazy ...
# supportd
Daniel Hilgarth
10/22/2024, 7:33 AMIs there a way for the Trace Details view to lazy load the spans? I've traces with thousands, sometimes tens of thousands of spans and the UI is either very slow or outright crashes
Daniel Hilgarth
10/22/2024, 7:39 AMI'm not writing the software, I'm just responsible for the infrastructure. From what I gathered so far, the reason for this is a REST call that quickly returns but starts a background process which processes hundreds or thousands of items, each generating a few spans.
Daniel Hilgarth
10/22/2024, 7:40 AM(Just to answer the question why we have something like this)
s
Srikanth Chekuri
10/22/2024, 8:02 AMYes, this is one of the things we are working on solving. Handling large traces better.
d
Daniel Hilgarth
10/22/2024, 8:03 AMGreat! Do you have a rough ETA?
s
Srikanth Chekuri
10/22/2024, 8:06 AMProbably in a month, as there is a lot of experimentation going on. Track progress here: https://github.com/SigNoz/signoz/issues/6132. The title says 10k but the goal is to test the limits of what we can support without putting the system under stress or making the browser go crazy.
d
Daniel Hilgarth
10/22/2024, 8:06 AMI can test with traces of 30k and more 🙈
s
Srikanth Chekuri
10/22/2024, 8:10 AMStill in experimentation, so I can't say anything concrete at the moment. One of the goals is to remove the limitation completely and support as many as several hundred thousand spans to start with feasibility testing of 1 million spans and the cost of supporting such cases in terms of resources needed.
d
Daniel Hilgarth
10/22/2024, 8:11 AMOkay, that does sound awesome
h
Helge Walter
11/20/2024, 3:59 PMWe also face the issue with some traces with over 15k spans and so we cannot get to the information we need for error analysis. I appreciate the efforts to speed up the UI in some future version but is there a possibilty to view the attributes and events of a single span from such a big trace right now?