Hi yall, Quick question, how does openobserve decide which operation name it displays of all the spans in a trace?

Hi there, so generally speaking operation name , span status etc , most these attributes are handled by instrumentation and not the backend..if you look at O2 Traces UI : their are two views/screens to look at - one is Span view and another for traces. Under Traces screen you'll see the service name and no of spans in a trace - if you click you can get a waterfall diagram which displays all the spans and the operation name. While span view displays all the spans received under the selected timeframe from all the services .. you can filter them further. ( just with few UI clicks no need to write a query.

Well yes, but on the traces screen, in the table, it shows operation name which seems to be quite random which name it actually grabs (of which span in the trace)

traces-hero-1920x1080.mp4

The traces with 27 spans are the same trace (same api call, same spans etc) why does one use "request" and the other "PATCH ..."?

Omkar is from engineering and have worked on the traces part, he should be able to answer your question, tho he is based in GMT + 5:30 , bit late here but we'll come back to you .

In table for a trace its show operation name of the trace root span (the span with no parent). @István Kolkert Can you check and get back if your trace has more than one root spans ?

Hi Omkar, For what I can see all of the spans have a parent (except one root RUM span). I cant find any notable difference in the traces either. Is there a way I can export the traces so you can look at them

@István Kolkert yes, you can. 1. Select "Spans" on traces list page 2. Filter by trace id and click on "Export" right to "Run Query"

Hmm I doubt that export is gonna clear anything up. What I do notice that there is a patern, if its the first trace from the RUM trace it shows "PATCH...." and everything after shows "request". The root RUM span's have the same span_id. The second trace created has a entry refering the previous PATCH request.

@István Kolkert If you check the right one "PATCH", it has 2 root spans

The "wf-home-frontend PATCH http://......" all the way at the bottom?

yes