Telemetry Improvement: Bicep Params
Related to #7301
Order of priority
- [ ] 1. Param file open (top of funnel)
- [ ] 2. Param file save event
- [ ] 3. Add the paramfile type to deploy command (we can finalize the design later)
If we wrap this event into other snippet events, we will still need to add an attribute like fileType "BicepParam" in order differentiate between our regular bicep files.
@sydkar for opinion and comments
I think these sound good. We might want to track the number of deployments or builds done with .bicepparam files as well. As additional features become available, we should probably add items to this list., especially those that are more experimental.
Are there other metrics that demonstrate usage (editing bicepparam files) besides tab completions?
Reopen with specific scenarios to capture