System.Diagnostics.Activity.Current should be available in AgentApplication

[mbatista]

The System.Diagnostics.Activity.Current that is no null in the message handling endpoint is not propagated to the AgentApplication's OnActivity handler.

The framework should propagate the Activity from the message api to the background process that handles message and if possible restore it before calling the handler so that they can all be correlated.

[tracyboehrer]

This ask isn't clear. What relation does System.Diagnostics.Activity.Current have to AgentApplication?

[mbatista]

This ask isn't clear. What relation does System.Diagnostics.Activity.Current have to AgentApplication?

In the controller, when the message request is received by the API set in the bot configuration, there is a System.Diagnostics.Activity.Current created.

This activity should be forwarded to the processor of the message and recovered in the message execution context so that logs emitted in the processing of the message have the same system.diagnostic.activity context. This ensure that analysis of the distributed tracing across multiple services is consistent.

Currently, system.diagnostic.activity.current is null during message processing.

[tracyboehrer]

Gotcha. We can take a look. No solid ETA. The issue is that incoming requests are processed on a background queue and the original Activity.Current is lost.