Mark Wolff

Which code snippet are you using where this is not working? Does [this](https://github.com/microsoft/ApplicationInsights-JS#telemetry-initializers) sample not work for you? Are you seeing it documented differently elsewhere? I've put out a change...

Only id is actually required for the item to be accepted, but as many fields should be set as possible so that the telemetry is actually useful. I will update...

@JRGranell actually I believe this is because the docs incorrectly reference `resultCode`. Use `responseCode` instead. I've updated the docs to account for this as well! Also the docs at `/vNext/AISKU/API.md`...

Yep, ideally this SDK should share, as much as possible, an API/feature surface with the node.js SDK. I'll add this to our backlog

@dotansimha It would be inside the "analytics plugin". Here is the entry point (you will also need to update the same function located in `AISKU/Initialization.ts` to match the interface change)....

Seems to be related to #516 but for a much smaller size (500 MB vs 1 KB). The try/catch added to fix that is not applied for this header. A...

Your setup looks fine (although you could try calling `setup`, then setting the config, then calling `.start()`. Is your url well-formatted? We use `url.parse()` to grab the hostname from it...

This is correct. I'm curious why your urls are not falling into the `regex.text(...)` conditional though

In #534 I added a try/catch around the setHeader causing this. I am not quite sure what is causing it to try to set the header after 1024 bytes, but...

Just giving some context here from the JS SDK. App Insights limits the length of strings for telemetry. The warning only reflects the app insights world and the actual string...