Glen Mailer

This would be really useful to be able to do on a per-request basis. At the moment the only way I can see to add a username field on the...

Aha, telemetry processor looks like just the ticket. Are there any pointers to docs on this other than in these issues?

Oh right, I did see it in the README. Perhaps adding an example of logging auth would be good to add. I’ll have a poke around and maybe send in...

This is what I ended up going with ```js appInsights.defaultClient.addTelemetryProcessor(attachUserId); function attachUserId(envelope, context) { const res = context['http.ServerResponse']; if (res && res.locals && res.locals.user) { envelope.tags['ai.user.authUserId'] = res.locals.user.username; } }...

I had a look to see how `webpack-hot-middleware` handles this scenario, as @garbles suggested in https://github.com/webpack-contrib/webpack-hot-client/issues/93#issuecomment-406459576 the global sentinel value is used to share the socket instance across all entries,...

I've just had a look, it looks like `webpack-dev-server` will produce one socket connection per entry, which will also mostly work, although I recall it also uses `postMessage` on the...

Ok, I've now gone and read up on all the issues related to #47 and it turns out this is pretty complicated because there's a bunch of different ways that...

@hedgepigdaniel oh cool, that looks neat - but I’m getting a 404 on the link with an explanation of the differnces

Oh right! I hadn’t realised it was a fork of hot client. I think contrib might be open to offers if someone maintaining it. I haven’t caught up with the...

Is there anything blocking such an implementation, or does this just require someone to send in a PR for the functionality?