data collector does not understand data type.

%3CLINGO-SUB%20id%3D%22lingo-sub-1773464%22%20slang%3D%22en-US%22%3Edata%20collector%20does%20not%20understand%20data%20type.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1773464%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20write%20own%20logger%20into%20asp.net%20to%20log%20into%20log%20analytics.%3CBR%20%2F%3EThere%20try%20to%20implement%20distributed%20tracing%20with%20help%20of%20activity%20class%20which%20is%20provided%20by%20asp.net%20core%20framework%2C%3C%2FP%3E%3CP%3EIssue%20is%20that%20when%20we%20are%20log%20TraceId%20into%20log%20as%20string%20%2C%20it's%20automatic%20consider%20as%20GUID%20and%20append%20dashes(-).%20so%20that%20we%20are%20not%20able%20to%20compare%20actual%20TraceId%20and%20logged%20TraceId.%3C%2FP%3E%3CP%3Ehere%20problem%20is%20Data%20Collector%20API%20does%20not%20understand%20proper%20data%20type.%3C%2FP%3E%3CP%3Efea47d6e-5871-c742-a07c-5073e8a7886c%20(logged%20TraceId)%3CBR%20%2F%3Efea47d6e5871c742a07c5073e8a7886c%20(original%20TraceId)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1846172%22%20slang%3D%22en-US%22%3ERe%3A%20data%20collector%20does%20not%20understand%20data%20type.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1846172%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F829906%22%20target%3D%22_blank%22%3E%40DhruvBarot%3C%2FA%3E%26nbsp%3BCan%20you%20please%20clarify%20which%20specific%20API%20you%20are%20using%3F%20Sample%20code%20demonstrating%20the%20issue%20would%20be%20even%20better.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBest%2C%26nbsp%3B%20Michael%3C%2FP%3E%0A%3CP%3E-AzMon%20Product%20Management%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I have write own logger into asp.net to log into log analytics.
There try to implement distributed tracing with help of activity class which is provided by asp.net core framework,

Issue is that when we are log TraceId into log as string , it's automatic consider as GUID and append dashes(-). so that we are not able to compare actual TraceId and logged TraceId.

here problem is Data Collector API does not understand proper data type.

fea47d6e-5871-c742-a07c-5073e8a7886c (logged TraceId)
fea47d6e5871c742a07c5073e8a7886c (original TraceId)

2 Replies

@DhruvBarot Can you please clarify which specific API you are using? Sample code demonstrating the issue would be even better. 

Best,  Michael

-AzMon Product Management

@Michael_Milirud we are using azure data collector API (https://docs.microsoft.com/en-us/azure/azure-monitor/platform/data-collector-api) 

please find attached sample application to reproduce the issue.

let me know if you want to more details.