Issue Trace field `Name` display N A and can not filter usin SigNoz Community #support

Issue: Trace field `Name` display N/A and can not ...

Dang Huy Nguyen

08/16/2025, 9:32 AM

Issue: Trace field

Name

display N/A and can not filter using field Name. Version: 0.92.1 Reason: Both field

name

and

attributes_string['name']

exists.

Copy code

"message": "Key `name` is ambiguous, found 2 different combinations of field context / data type: [name=name,context=attribute,datatype=string name=name,context=span,datatype=string]."

Do you think this is a bug? I believe field

Name

should fallback to span context. Ref: https://signoz.io/docs/userguide/field-context-data-types/

Srikanth Chekuri

08/16/2025, 2:52 PM

Can you create an issue here https://github.com/SigNoz/signoz? I will see how to go about fixing this. Otherwise, what is you experience with 0.92.1 so far?

Dang Huy Nguyen

08/18/2025, 3:26 AM

Thanks @Srikanth Chekuri, created: https://github.com/SigNoz/signoz/issues/8820 Meanwhile it would be nice if we have a quick workaround. I just upgraded last weekend, have not seen much difference so far.

Srikanth Chekuri

08/18/2025, 3:56 AM

Please go to browser local storage / application and share the

TRACE_LIST_OPTIONS

value

Dang Huy Nguyen

08/18/2025, 4:01 AM

Copy code

{
  "selectColumns": [
    {
      "key": "name",
      "dataType": "string",
      "type": "tag",
      "isColumn": true,
      "isJSON": false,
      "id": "name--string--tag--true",
      "isIndexed": false,
      "name": "name"
    },
    {
      "key": "durationNano",
      "dataType": "float64",
      "type": "tag",
      "isColumn": true,
      "isJSON": false,
      "id": "durationNano--float64--tag--true",
      "isIndexed": false,
      "name": "durationNano"
    },
    {
      "key": "httpMethod",
      "dataType": "string",
      "type": "tag",
      "isColumn": true,
      "isJSON": false,
      "id": "httpMethod--string--tag--true",
      "isIndexed": false,
      "name": "httpMethod"
    },
    {
      "key": "responseStatusCode",
      "dataType": "string",
      "type": "tag",
      "isColumn": true,
      "isJSON": false,
      "id": "responseStatusCode--string--tag--true",
      "isIndexed": false,
      "name": "responseStatusCode"
    },
    {
      "key": "has_error",
      "dataType": "bool",
      "type": "",
      "isColumn": true,
      "isJSON": false,
      "id": "has_error--bool----true",
      "name": "has_error"
    },
    {
      "name": "trace_id",
      "signal": "traces",
      "fieldContext": "span",
      "fieldDataType": "string"
    }
  ]
}

Srikanth Chekuri

08/18/2025, 4:02 AM

Change the

"type":"tag"

for

name

"type":"span"

Srikanth Chekuri

08/18/2025, 4:03 AM

And then update the local storage value with entire new object

Dang Huy Nguyen

08/18/2025, 4:13 AM

Thanks @Srikanth Chekuri workaround works. I think the correct solution should available soon ?

Srikanth Chekuri

08/18/2025, 4:21 AM

Yes

🙌 1

Dang Huy Nguyen

08/25/2025, 10:26 AM

Hi @Srikanth Chekuri, I can expect the fix in which release ?

Srikanth Chekuri

08/25/2025, 10:41 AM

next release.

Open in Slack

Previous Next