Hector Hernandez

You could use Application Insights APIs to manually call trackTrace with the correct custom property you are adding, https://github.com/microsoft/ApplicationInsights-node.js#track-custom-telemetry

@Eden1999 you can pass tagOverrides as well when calling trackEvent API, something like this: `let tagOverrides = {}; tagOverrides["ai.user.id"] = "TestUser"; appInsights.defaultClient.trackEvent({ name: "TestEvent", tagOverrides: tagOverrides });`

@mattmccleary can you take a look at this issue?, it would be good to allocate work for this to maintain feature parity with C# SDK

@kh-yash the SDK will make a call to Azure Metadata service to enhance telemetry with extra properties when running in Azure environments like App Services or Azure Functions, this doesn't...

@kh-yash that is correct this timeout will not break any functionality and your data must be sent, I believe this timeout will be logged only when debug logs are turned...

@ArtemisMucaj can you include the full error message here?, which file is generating the error?

@kevit-amish-faldu can you check following file and check the stored JSON events in there /tmp/appInsights-node/{YOUR_INSTUMENTATION_KEY} for Linux or USERDIR/AppData/Local/Temp/appInsights-node/{YOUR_INSTUMENTATION_KEY}, AI SDK will store telemetry in disk when it fails to...

@kevit-amish-faldu I can see now that AI SDK delete the file before trying to parse the JSON events, so when you hit this error it will not keep failing as...

@NiravMultani157 we don't add the full envelope in the Trace logs, mainly because of potential huge increase of telemetry size, something you can try is adding a [telemetryProcessor](https://github.com/microsoft/ApplicationInsights-node.js#preprocess-data-with-telemetry-processors) and try...

@DevRCRun is possible, JSON serialization could happen with any field in the envelope, you can try what I suggested before to find which envelope is causing the issue.