You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are implementing OpenTelemetry for observability in our solution, but we have identified a blind spot. Currently, we are unable to obtain information about delays and propagate trace information. This is due to the fact that the InitiateView method of the ViewManager does not support context propagation. As a result, we are unable to create a complete and accurate picture of the system's behavior, starting from the controller or other microservices within the solution.
We would greatly benefit from the fabric-smart-client library supporting the propagation of context instead of creating a new one. This would enable the propagation of trace information from the microservice. To achieve this, we suggest either adding a new method or modifying the existing viewManager.InitiateView() method to accept a context.
The text was updated successfully, but these errors were encountered:
Opening this up again; another way to use FSC is to InitiateContext with a view first, and then pass around the resulting view.Context. That way should also support to derive a view.Context from an existing context.Context.
We are implementing OpenTelemetry for observability in our solution, but we have identified a blind spot. Currently, we are unable to obtain information about delays and propagate trace information. This is due to the fact that the InitiateView method of the ViewManager does not support context propagation. As a result, we are unable to create a complete and accurate picture of the system's behavior, starting from the controller or other microservices within the solution.
We would greatly benefit from the fabric-smart-client library supporting the propagation of context instead of creating a new one. This would enable the propagation of trace information from the microservice. To achieve this, we suggest either adding a new method or modifying the existing viewManager.InitiateView() method to accept a context.
The text was updated successfully, but these errors were encountered: