https://signoz.io
Join Slack
Issue: Trace field `Name` display N/A and can not filter using field Name. Version: 0.92.1 Reason: ...
# support
d
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/
s
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?
d
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.
s
Please go to browser local storage / application and share the 
TRACE_LIST_OPTIONS
value
d
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"
    }
  ]
}
s
Change the 
"type":"tag"
for 
name
to 
"type":"span"
And then update the local storage value with entire new object
d
Thanks @Srikanth Chekuri workaround works. I think the correct solution should available soon ?
s
Yes
🙌 1
d
Hi @Srikanth Chekuri, I can expect the fix in which release ?
s
next release.
Open in Slack
PreviousNext
Powered by

SigNoz Community

SigNoz is an open-source APM. It helps developers monitor their applications & troubleshoot problems, an open-source alternative to DataDog, NewRelic, etc.

Powered by