You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The attributes mapping in the ADX exporter documentation listed out table columns like TraceId / SpanId / ParentId, but the sample code of creating tables in ADX in the same document uses TraceID / SpanID / ParentID. The source code of the exporter also uses ID instead of Id.
Please keep in mind that, ADX is a case-sensitive database and the data of TraceID cannot be mapped into TraceId correctly.
I'm glad to open a PR to fixup the doc
The text was updated successfully, but these errors were encountered:
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Component(s)
exporter/azuredataexplorer
Describe the issue you're reporting
Hi,
The attributes mapping in the ADX exporter documentation listed out table columns like
TraceId
/SpanId
/ParentId
, but the sample code of creating tables in ADX in the same document usesTraceID
/SpanID
/ParentID
. The source code of the exporter also usesID
instead ofId
.Please keep in mind that, ADX is a case-sensitive database and the data of
TraceID
cannot be mapped intoTraceId
correctly.I'm glad to open a PR to fixup the doc
The text was updated successfully, but these errors were encountered: