microsoft / microsoft/AzureTRE
Use telemetry via the customer-attribution method to track deployments
Open
Nobody has claimed this yet.
deployment
feature
- Dominant language
- Python
- Stars
- 235
- Forks
- 192
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 13
Description
Describe the solution you'd like
Similar to Azure Verified Modules and most Landing Zone Accelerators, we should collect telemetry from deployments of TRE core and each shared and workspace service to gauge usage and demand.
Customers can opt-out of telemetry.
Describe alternatives you've considered
N/A
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the customer-attribution method and the deployment entry points for TRE core, shared services, and workspace services. Clarify the telemetry data, opt-out behavior, and coverage expected before implementing; done means deployments collect the agreed telemetry while customers can opt out.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, python
- Domain
- cloud, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100