Requirement - what kind of business use case are you trying to solve?
There are long living processes in our ecosystem involving many services. Sometimes it leads to anomaly huge traces (100k+ spans). Fetching all spans from such a traces slow down trace search.
Problem - what in Jaeger blocks you from solving the requirement?
There is no option (similar to es.max-num-spans for Elasticsearch storage) to limit amount of spans being fetched for each trace.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Introduce new setting in config file to imit amount of spans being fetched for each trace.
Requirement - what kind of business use case are you trying to solve?
There are long living processes in our ecosystem involving many services. Sometimes it leads to anomaly huge traces (100k+ spans). Fetching all spans from such a traces slow down trace search.
Problem - what in Jaeger blocks you from solving the requirement?
There is no option (similar to es.max-num-spans for Elasticsearch storage) to limit amount of spans being fetched for each trace.
Proposal - what do you suggest to solve the problem or improve the existing situation?
Introduce new setting in config file to imit amount of spans being fetched for each trace.