Jackson Weber

@JasonYeMSFT We've recently upgraded to using OpenTelemetry under the hood of this SDK. Could you test this issue out again, as it should be resolved. Thank you.

@MuhamedSalihSeyedIbrahim Please ensure that you're sending correctly JSON serializable. There are several 3rd party NPM packages that can help clean up JSON for serialization. Thank you.

The callback can be used with flush - solution applies to the latest version.

@jeromewir We recently changed to using OpenTelemetry under the hood for context propagation. As such, this issue may no longer impact you. Please refer to OpenTelemetry JS's docs on context...

@brianpham93 Did you have any luck with your serialization issue?

@brianpham93 Is there anything about your scenario that makes converting the Big Int to a string not work for you in the long term?

@brianpham93 Awesome! Mind if I mark this issue as complete in that case?

@david-luna @ehtb Given the existence of the `undici/native-fetch` instrumentation, this issue can be closed.

@mderriey Thank you for submitting this issue, but I'm having some trouble reproducing your results. I have a simple app currently that looks like this: ``` const express = require('express');...

@mderriey Apologies, I had my test app in shim-testing configuration by accident there, thanks! However, I'm still able to see the message in the `InvariantError` in the CustomProperties of ApplicationInsights...