@krishna-kariya could you please update the description for understanding the scope of the PR

@krishna-kariya
The scope of this PR is not very clear are we only supporting below cases :-

1. When customer is only passing the trace ??
2. We are not supporting the case when trace is not there ??
3. We are not supporting the output binding ??

@krishna-kariya The scope of this PR is not very clear are we only supporting below cases :-

1. When customer is only passing the trace ??
2. We are not supporting the case when trace is not there ??
3. We are not supporting the output binding ??

@shrohilla , The scope is very well defined and only includes tracing support for triggers as mentioned in the description. We have covered for all the cases - when traceparent is present, or not.

@krishna-kariya since the case is only for trigger and as mentioned we are not supporting the output binding. In-that case it doesn't make sense to build a new trace in my opinion.

cc @raorugan & @lpapudippu

@krishna-kariya The scope of this PR is not very clear are we only supporting below cases :-

1. When customer is only passing the trace ??
2. We are not supporting the case when trace is not there ??
3. We are not supporting the output binding ??

@shrohilla , The scope is very well defined and only includes tracing support for triggers as mentioned in the description. We have covered for all the cases - when traceparent is present, or not.

@shrohilla , I think we had decided that distributed tracing support for output binding will be added later.

@krishna-kariya the point is if we are not supporting for output binding in that case creating a new trace doesn't make sense.
Your scope is just to display the trace in app insights for the events which are being triggered and contains the traceid.
Creating a new trace in this case doesn't make sense to me.