Multiple Create: Determine and add telemetry to get insights for the feature usage

[severussundar]

To get some insights into the usage of multiple create feature by the users, it is important to have some telemetry emitted.

1. Determine exactly what telemetry to be emitted. Example: One way to quantify the adoption of multiple create feature could be to track the number of times a multiple create operation is used - Adding a log statement such as Multiple Create operation: {operation name} might be sufficient for this.

Likewise, determine the insights we would want and the relevant telemetry to emit that would enable us to have those insights.

2. Implement and test the changes necessary to emit the identified telemetry.

[seantleonard]

Dependent on telemetry strategy being fully defined. @JerryNixon

[severussundar]

Collecting telemetry to gain insights seem to be a bigger conversation in terms of the exact implementation approach.

This is not a blocker for releasing the feature or GA. Hence, moving it to a milestone post GA

[severussundar]

Closing this issue as there exists no solution, at the moment, for collecting detailed telemetry at the granularity of each request.