Some spans cannot be associated in the entire request trace. Are these spans missing any information? #537

hong-ke · 2025-07-27T13:01:23Z

hong-ke
Jul 27, 2025

I noticed that some spans in my application cannot be properly associated with the entire request trace, resulting in an incomplete trace view. Below is the JSON data of the relevant span and the curl request to view the trace. Could you please tell me what information might be missing that causes this issue?

Span JSON

{
  "id": "e4762ae474",
  "parentId": "e4762ae474",
  "traceId": "9cf0eecbf2a54eaa9b55682f848faade",
  "projectId": 1,
  "groupId": "5107076160605058677",
  "type": "funcs",
  "system": "funcs",
  "kind": "client",
  "name": "MOARedisClient./service/user-location.queryUserLocations",
  "displayName": "MOARedisClient./service/user-location.queryUserLocations",
  "time": "2025-07-24T11:01:00.025Z",
  "duration": 1,
  "statusCode": "ok",
  "statusMessage": "SUCCESS",
  "attrs": {
    "sw8_segment_id": "9cf0eecb3fa54eaaa83f90482fc594de.205.17533548600257074",
    "sw8_trace_id": "9cf0eecb3fa54eaaa83f90482fc594de.205.17533548600257075",
    "url": "redis://10.133.218.135:13032/service/user-location/queryUserLocations",
    "http_url": "http://fep.hellogroup.com/v4/config/ext/batchRecommend",
    "service_name": "momo-prod::mk-web-prod",
    "sw8_span_id": 1,
    "moa_target": "/service/user-location",
    "service_instance_id": "cf4e9d8cb83b430bb3e1e0cd25d28cdf@10.132.199.135",
    "sw8_parent_span_id": 0
  },
  "events": [],
  "links": []
}

Curl request to view the trace

curl 'http://localhost:14318/internal/v1/tracing/1/traces/9cf0eecbf2a54eaa9b55682f848faade/spans?_force=584480156&drop_consumers=false&goto_span_id=e4762ae474' \
  -H 'Accept: application/json, text/plain, */*' \
  -H 'Accept-Language: zh-CN,zh;q=0.9' \
  -H 'Connection: keep-alive' \
  -b 'Goland-65590e03=12afb7f5-ebf0-4411-9041-07e35eeaa2ea; _ga=GA1.1.932772008.1753096240; token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiJKY0dmUCFcdTAwM2MiLCJleHAiOjE3NTM3MDEwODcsImlhdCI6MTc1MzA5NjI4N30.J47EfgHKJtqv5Kv4oVBF_5ZEo1C6Gq2SmFuXAgizMXo; connect.sid=s%3A-hBkO86fxJtAVs_BCg4s1og7BY0nv3D1.NGqg6D48ElBB8gTZiGx19sVJY0C8T0nwOYqMKCaPhhM; _ga_73MMSNPLC5=GS2.1.s1753620571$o4$g1$t1753620782$j60$l0$h0' \
  -H 'Referer: http://localhost:14318/traces/1/9cf0eecbf2a54eaa9b55682f848faade?span=e4762ae474' \
  -H 'Sec-Fetch-Dest: empty' \
  -H 'Sec-Fetch-Mode: cors' \
  -H 'Sec-Fetch-Site: same-origin' \
  -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36' \
  -H 'sec-ch-ua: "Not)A;Brand";v="8", "Chromium";v="138", "Google Chrome";v="138"' \
  -H 'sec-ch-ua-mobile: ?0' \
  -H 'sec-ch-ua-platform: "macOS"'

curl resp

{
    "error": {
        "code": "not_found",
        "message": "trace 9cf0eecbf2a54eaa9b55682f848faade can't be found"
    },
    "statusCode": 404,
    "traceId": "18561ccfa0badff117308778276e3309"
}

From the span data, it has traceId and parentId, but it still seems unable to be correctly associated with the request trace. What could be the reason for this? Is there any key information missing?

vmihailenco · 2025-07-27T14:06:43Z

vmihailenco
Jul 27, 2025
Maintainer

@hong-ke where do you get the Span JSON you posted?

I noticed that some spans in my application cannot be properly associated with the entire request trace, resulting in an incomplete trace view. Below is the JSON data of the relevant span and the curl request to view the trace.

What I see from the data you posted is that

the trace 9cf0eecbf2a54eaa9b55682f848faade does exists in the database
but Uptrace can't find it when you try to view the trace

It should not normally happen. I would try 2 things:

try to reset Redis cache
check Uptrace self_monitoring data by the "traceId": "18561ccfa0badff117308778276e3309" from Uptrace response

4 replies

hong-ke Aug 4, 2025
Author

After using the method you provided, the trace still hasn't been displayed successfully. I created a cloud account and sent one piece of demo data to the account 893312233@qq.com via DSN. The trace ID is 8f0649d5b491422db629331709f1c2b8, and the data was sent at 2025-08-04T02:37:15.803Z. Could you please help check the cause from the server side?

vmihailenco Aug 4, 2025
Maintainer

The problem with the trace you've shared is that it has 2 spans with span.id == span.parent_id which is wrong:

Row 1:
──────
id:            551795783715 -- 551.80 billion
parent_id:     551795783715 -- 551.80 billion

Row 2:
──────
id:            836400873621 -- 836.40 billion
parent_id:     836400873621 -- 836.40 billion

It is also true for the initial span JSON you've shared:

  "id": "e4762ae474",
  "parentId": "e4762ae474",

Uptrace does not know how to handle this situation properly and so it defaults to display 404 error page. I will fix this eventually, but you should also fix the id generation on your side too.

hong-ke Aug 4, 2025
Author

Thank you for your explanation. My agent is the Skywalking-agent, and I am using the community's https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/skywalkingreceiver to convert traces to OTLP format. It is quite difficult to fix the ID generation issue. May I ask about the timeline for fixing this problem? I am currently researching and selecting observation tools, and this issue will affect my decision on whether to use Uptrace. I look forward to your reply.

vmihailenco Aug 4, 2025
Maintainer

You won't get good/meaningful traces without span.parent_id. The best thing Uptrace will be able to do is to display a list of spans without parent/child relations.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Some spans cannot be associated in the entire request trace. Are these spans missing any information? #537

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment 4 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Some spans cannot be associated in the entire request trace. Are these spans missing any information? #537

Uh oh!

Uh oh!

hong-ke Jul 27, 2025

Replies: 1 comment · 4 replies

Uh oh!

Uh oh!

vmihailenco Jul 27, 2025 Maintainer

Uh oh!

hong-ke Aug 4, 2025 Author

Uh oh!

vmihailenco Aug 4, 2025 Maintainer

Uh oh!

hong-ke Aug 4, 2025 Author

Uh oh!

vmihailenco Aug 4, 2025 Maintainer

hong-ke
Jul 27, 2025

Replies: 1 comment 4 replies

vmihailenco
Jul 27, 2025
Maintainer

hong-ke Aug 4, 2025
Author

vmihailenco Aug 4, 2025
Maintainer

hong-ke Aug 4, 2025
Author

vmihailenco Aug 4, 2025
Maintainer