Telemetry not logging ActivityID and ConversationID.

[tracyboehrer]

It is a problem which happened only on directline extension, neither in directline nor webchat it will happen.

As we known,
1), in directline/webchat, client connect to directline via https and directline connect to bot via https

2), in directline extension, client connect to directline extension via websocket and directline connect to bot via named pipe

In BotFramework OpenSource SDK, we can found that SDK use HttpContext to store activity and log it to telemetry.

where to store it: botbuilder-dotnet/libraries at main · microsoft/botbuilder-dotnet · GitHub

where to log it to telemetry: botbuilder-dotnet/libraries at main · microsoft/botbuilder-dotnet · GitHub

In above, we had metioned that in directline/webchat, directline connect to bot via https, so it has a non-null HttpContext, but in directline extension, extension connect to bot via named pipe, and the value of HttpContext is null, and I think it is an SDK bug.

Then it will lead to both conversationid and activityid not log into telemetry.