Karlie-777

[BUG] enableUnhandledPromiseRejectionTracking shows no error trace

4

when parsing `onunhandledrejection` error event, `error.reason.toString()` is passed to `Exception.CreateAutoException()` function and the `error.reason.toString()` will expose no detailed trace stack . Instead `error.reason.stack.toString()` should be used to enable full trace...

for current snippet version, add parent trace id in the snippet.

[draft] Specs Overview: [shared/AppInsightsCommon/src/Interfaces/IThrottleMgr.ts](https://github.com/microsoft/ApplicationInsights-JS/pull/1882/files/0b19df2686333318d78d2210db61c3a3e195cd0c#diff-47e400f1c578b07a6eb851a986322fd8bd248c674d9efbfcfd67feb625f88bd7)

1. change config name `snippet` to `webInstrumentation` 2. old config/methods should still work 3. add client config for JS SDK 4. add client config for snippet src 5. add more...

Current way of adding offline support plugin: [here](https://github.com/microsoft/ApplicationInsights-JS/tree/main/channels/offline-channel-js#basic-usage ) Offline support depends on Sender Channel to get request details, so sender channel has to be initialized before offline support plugin.

The SDK performs some “back-off” logic to stop the SDK from flooding the endpoint This will be causing the “buffer” to continue to accumulate the “retriable” events in the send...

https://github.com/microsoft/ApplicationInsights-JS/issues/2322